I tested kvm-81 and kvm-83 as well (can't test kvm-80 or older because of
the
qcow2 performance regression caused by the default writethrough caching
policy)
but it randomly triggers an even worse bug: the moment I shut down a guest
by
typing quit in the monitor, it sometimes
On Sun, Feb 15, 2009 at 2:57 AM, Gleb Natapov g...@redhat.com wrote:
I am not able to reproduce this. After more then hundred boot linux; generate
disk io; quit loops all I've got is an image with 7 leaked blocks and
couple of filesystem corruptions that were fixed by fsck.
The type of
On Sun, Feb 15, 2009 at 3:46 AM, Marc Bevand m.bev...@gmail.com wrote:
Other factors you might consider when trying to reproduce: [...]
And the probability of that bug occuring seems less than 1% (I only
witnessed 6 or 7 occurences out of about a thousand shutdown events).
Also, contrary to
Hi All,
This is our Weekly KVM Testing Report against lastest kvm.git
48aa74b80e1dbef32f756104a9f5a18f58429c25 and kvm-userspace.git
a1efe3d681ccd3ae75870b9bd639ae8ee2625e7e.
There is no new issue found in this two weeks.
Five Old Issues:
1.
Bugs item #2088475, was opened at 2008-09-02 11:37
Message generated for change (Comment added) made by technologov
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2088475group_id=180599
Please note that this message will contain a full copy of the comment
The callback you suggest for devices requesting an inbound filter will
infinite-loop when there's two such devices on the same vlan bus,
because each time the callback is called, that device will re-issue
its filter request which triggers the callback on the other similar
device. Back and
Jorge Lucángeli Obes wrote:
On Thu, Feb 12, 2009 at 11:56 PM, Ross McKay ro...@zeta.org.au wrote:
dnjap wrote:
I'm looking for a laptop on which I can run KVM.
1. Does anyone have a list of AMD-V or VT-x capable laptop CPU's?
Bugs item #2525768, was opened at 2009-01-21 16:03
Message generated for change (Comment added) made by danv
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599
Please note that this message will contain a full copy of the comment
Introduce KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY two ioctls.
This two ioctls are used by userspace to specific guest device MSI-X entry
number and correlate MSI-X entry with GSI during the initialization stage.
MSI-X should be well initialzed before enabling.
Don't support change MSI-X entry
(oops... fix a typo)
Introduce KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY two ioctls.
This two ioctls are used by userspace to specific guest device MSI-X entry
number and correlate MSI-X entry with GSI during the initialization stage.
MSI-X should be well initialzed before enabling.
Don't support
From fb2e7473e44b6b0bcc8448d4f74a4f8d43e7fa4c Mon Sep 17 00:00:00 2001
From: Xiantao Zhang xiantao.zh...@intel.com
Date: Mon, 16 Feb 2009 15:24:05 +0800
Subject: [PATCH] kvm: ia64: Fix the build errors due to lack of macros related
to MSI.
Include the newly introduced msidef.h to solve the build
Hi, Tony
For supporting kvm's MSI, we have to move some macros from ia64_msi.c out to
avoide duplicate them. In addition, to keep them consistent with x86's , I also
changed some macros' name. How do you think of the patch ? If you agree to
the changes, could you add your Sign-off-by to
12 matches
Mail list logo
