Hi, Dustin. On Saturday, 07 November 2009 21:15:09 -0600, Dustin Kirkland wrote: > On Sat, Nov 7, 2009 at 7:01 PM, Daniel Bareiro <daniel-listas@xxxxxxx> wrote: > > According to I see in Launchpad, there is a fix released for Qemu > > and qemu-kvm (Ubuntu). > It's "fix committed" in QEMU, and "Fix Released" in Ubuntu's qemu-kvm. > > We in Ubuntu have released version of qemu-kvm-0.11.0 that includes an > extra patch from Anthony, which he posted on the mailing list, and > committed to QEMU's git tree. He hasn't officially released an > upstream QEMU with the fix yet, though. > > I'm using KVM-88 compiled from the source code obtained of the KVM > > official site. How I could apply these fix? There is some KVM > > version that includes these corrections in the official site? > > Not that I know of, yet. > > You can pull the patch [1] we're carrying in Ubuntu, and apply it to > qemu-kvm-0.11.0 [2] from the kvm website, if you like. > [1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/qemu-kvm/karmic/annotate/head%3A/debian/patches/11_fix_virtio-blk_hot_add_after_remove.patch > [2] http://sourceforge.net/projects/kvm/files/ I've tested again with Linux 2.6.32 and qemu-kvm-0.12.0-rc2 and this time I could verify that no longer happens the problem with Virtio. That is to say, the virtual disk can be added and be removed every time without problems. It drew attention to me that whenever I add the virtio device, this appears with a different name (vdc, vdd, vde, etc). This it is the awaited behavior? Testing the same with if=scsi, I get a tainted again when removing the virtual disk since the first time that I try to remove it. Nevertheless, no longer it seems to have problem to add it again. Thanks for your reply. Merry Christmas. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Lenny - Linux user #188.598
Attachment:
signature.asc
Description: Digital signature
