On Saturday 05 January 2008 09:24:40 Anthony Liguori wrote:
> @@ -215,17 +231,40 @@
> struct virtnet_info *vi = rvq->vdev->priv;
> /* Suppress further interrupts. */
> rvq->vq_ops->disable_cb(rvq);
> +#ifdef COMPAT_napi
> + vi->rvq->vq_ops->enable_cb(vi->rvq);
> +
Hey Rusty et al,
I've got automatic backports of the virtio modules[1] working back to
2.6.18. Everything seems okay except that for any kernel with the older
NAPI api, performance is extremely bad. I get about 1gbit on TX with
2.6.24 but I get somewhere around 20mbit on 2.6.22.
I had to r
Hi Avi,
On Thu, Jan 03, 2008 at 11:17:50PM +0200, Avi Kivity wrote:
> While pci interrupts are documented as active high, the documentation for
> the piix4 pic elcr registers suggests piix4 level-triggered interrupts are
> active high. So there is some inconsistency somewhere involving qemu
> i
>> One update for those issues about failures of booting SMP Windows,
refer
>> to 6th and 7th issues.
>> We found that Windows SMP guests will fail to boot if using qcow
images.
>>
>> In our testing we are using qcow images to boot most guests. We tried
to
>> switch to common disk images and then
On Fri, Jan 04, 2008 at 01:42:04AM -0600, Carlo Marcelo Arenas Belon wrote:
> On Fri, Jan 04, 2008 at 12:57:49AM -0600, Carlo Marcelo Arenas Belon wrote:
> > change the function parameter to use vaddr instead of addr to avoid a
> > variable name redefinition from 9a5ee611ca79bec98e9d97e93f11df8083b
Zhao, Yunfeng wrote:
> Hi, all,
>
> This is today's KVM test result against kvm.git
> e7706133a12f0172b1a5ce4467277abd598155b6 and kvm-userspace.git
> 7c75d86ba5c761bb44ea80e6e22973fee66adb00.
>
> One update for those issues about failures of booting SMP Windows, refer
> to 6th and 7th issues.
>
Hi, all,
This is today's KVM test result against kvm.git
e7706133a12f0172b1a5ce4467277abd598155b6 and kvm-userspace.git
7c75d86ba5c761bb44ea80e6e22973fee66adb00.
One update for those issues about failures of booting SMP Windows, refer
to 6th and 7th issues.
We found that Windows SMP guests will
