On 04/03/2010 11:07 AM, Blue Swirl wrote:
On 4/3/10, Paolo Bonzini wrote:
On 04/02/2010 09:04 PM, Blue Swirl wrote:
-int kvm_init(int smp_cpus);
I had missed this; I don't see a particular reason to move this out of
kvm.h. Anyway I don't feel strongly about this.
The reason is to avoi
On 4/4/10, Paolo Bonzini wrote:
> On 04/03/2010 11:07 AM, Blue Swirl wrote:
>
> > On 4/3/10, Paolo Bonzini wrote:
> >
> > > On 04/02/2010 09:04 PM, Blue Swirl wrote:
> > >
> > >
> > > > -int kvm_init(int smp_cpus);
> > > >
> > > >
> > >
> > > I had missed this; I don't see a particular reason to
On Thu, Apr 01, 2010 at 11:56:25PM +0200, Stefan Weil wrote:
> u_int64_t raises compiler error messages:
>
> CClibhw32/virtio.o
> /qemu/ar7/hw/virtio.c: In function ‘virtio_queue_get_avail_size’:
> /qemu/ar7/hw/virtio.c:776: error: ‘u_int64_t’ undeclared (first use in this
> function)
> /qe
On Fri, Apr 02, 2010 at 10:41:03AM -0500, Anthony Liguori wrote:
> On 04/02/2010 10:27 AM, Anthony Liguori wrote:
>>
>> This tap files are a bit odd. We don't compile tap.o for mingw32 but
>> we do compile tap-win32.o so what we need to do is define
>> tap_get_vhost_net in tap-win32.c. Testin
2010/4/2 Anthony Liguori :
> On 04/02/2010 10:27 AM, Anthony Liguori wrote:
>>
>> This tap files are a bit odd. We don't compile tap.o for mingw32 but we
>> do compile tap-win32.o so what we need to do is define tap_get_vhost_net in
>> tap-win32.c. Testing a patch right now.
>
> I pushed a fix th
Hi,
Thanks for reply. -monitor option gives me acces to qemu console. I need
access to guest shell.
It occours I didn't have serial port enabled in grub, now it's works with
-nographic option. If someone is interested this tutorial make the deal:
http://www.cyberciti.biz/faq/linux-serial-console-
On Wed, Mar 31, 2010 at 09:20:31PM +0300, Michael S. Tsirkin wrote:
> From: David L Stevens
>
> vhost driver in qemu didn't ack features, and this happens
> to work because we don't really require any features. However,
> it's better not to rely on this. This patch passes features to
> vhost as g
Avi Kivity writes:
> On 03/02/2010 11:34 AM, Jernej Simončič wrote:
> >On Tuesday, March 2, 2010, 9:21:18, Chris Webb wrote:
> >
> >>I remember about a year ago, someone asserting on the list that -usbdevice
> >>tablet was very CPU intensive even when not in use, and should be avoided if
> >>mous
> > Looks like the tablet is set to 100 Hz polling rate. We may be able
> > to get away with 30 Hz or even less (ep_bInterval, in ms, in
> > hw/usb-wacom.c).
>
> Changing the USB tablet polling interval from 10ms to 100ms in both
> hw/usb-wacom.c and hw/usb-hid.c made no difference except the an i
vhost in current kernels doesn't support mergeable buffers.
Disable this feature if vhost is enabled, until such
support is implemented.
Signed-off-by: Michael S. Tsirkin
---
hw/vhost_net.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/vhost_net.c b/hw/vhost_net.c
i
Howdy,
while trying to run a self-compiled ppc32 2.6.34-rc3 kernel in qemu I stumbled
over this host TCG breakage. We're looking at this code: (printks added by me)
lib/lmb.c:lmb_add_region()
153 if (adjacent > 0) {
154 printk("XXX %d - 0x%08llx\n", __LINE__, rgn->region
On Sun, 4 Apr 2010, Alexander Graf wrote:
> Howdy,
>
> while trying to run a self-compiled ppc32 2.6.34-rc3 kernel in qemu I
> stumbled over this host TCG breakage. We're looking at this code:
> (printks added by me)
Thanks for the report should be fixed by
36368cf0d513efff45b0dbb4350cdc04a2b
On 04/04/2010 05:25 PM, Paul Brook wrote:
Looks like the tablet is set to 100 Hz polling rate. We may be able
to get away with 30 Hz or even less (ep_bInterval, in ms, in
hw/usb-wacom.c).
Changing the USB tablet polling interval from 10ms to 100ms in both
hw/usb-wacom.c and hw/usb-hid.c
The reason is to avoid including kvm.h by vl.c.
But that's not a problem, kvm.h can be included by compiled-once files;
that was the reason to introduce the stubs in the first place. kvm_* should
be declared in kvm.h.
That can't be safe because CONFIG_KVM will not be defined for files
com
On 04.04.2010, at 18:38, malc wrote:
> On Sun, 4 Apr 2010, Alexander Graf wrote:
>
>> Howdy,
>>
>> while trying to run a self-compiled ppc32 2.6.34-rc3 kernel in qemu I
>> stumbled over this host TCG breakage. We're looking at this code:
>> (printks added by me)
>
> Thanks for the report sho
Commit f1698408 "Compile usb-ohci only once" introduces a "be" property to the
pci-ohci device. The PCI bus is always little-endian, so this is completely
bogus. A hypothetical big-endian device would actually introduce another
byteswap.
As discussed previously, if you really want to avoid comp
On 4/4/10, Paul Brook wrote:
> Commit f1698408 "Compile usb-ohci only once" introduces a "be" property to the
> pci-ohci device. The PCI bus is always little-endian, so this is completely
> bogus. A hypothetical big-endian device would actually introduce another
> byteswap.
Then why there are
> > The USB HID devices implement the SET_IDLE command, so the polling
> > interval will have no real effect on performance.
>
> On a Linux guest (F12), I see 125 USB interrupts per second with no
> mouse movement, so something is broken (on the guest or host).
Turns out to be a a bug in the UHCI
> On 4/4/10, Paul Brook wrote:
> > Commit f1698408 "Compile usb-ohci only once" introduces a "be" property
> > to the pci-ohci device. The PCI bus is always little-endian, so this is
> > completely bogus. A hypothetical big-endian device would actually
> > introduce another byteswap.
>
> Then why
> > My guess is that the overhead you're seeing is entirely from the USB host
> > adapter having to wake up and check the transport descriptor lists. This
> > will only result in the guest being woken if a device actually responds
> > (as mentioned above it should not).
>
> A quick profile on the
I think I got all the tcg backend bits right, but can't test most of them.
Please test and report any problems.
Historically the qemu tlb "addend" field was used for both RAM and IO accesses,
so needed to be able to hold both host addresses (unsigned long) and guest
physical addresses (target_phy
On (Thu) Apr 01 2010 [18:42:38], Alexander Graf wrote:
> Virtio-Console can only process one character at a time.
The host can process as many as you give it, depending on the buffer
size exposed by the guest.
On older guests (guest kernels w/o multiport support), the guest reads
input from host,
On (Thu) Apr 01 2010 [18:42:39], Alexander Graf wrote:
> When using virtio-console on s390, the input doesn't work.
>
> The root of the problem is rather simple. What happens is the following:
>
> 1) create character device for stdio
> 2) char device is done creating, sends OPENED event
> 3) v
23 matches
Mail list logo
