Red Hat Bugzilla – Bug 905713
F18 virtio doesn't support VMs that use virtio from F17
Last modified: 2013-06-26 06:10:13 EDT
Description of problem:
I have a Windows 7 KVM VM working nicely with virtio in F17 x86_64. I installed the virtio windows storage drivers... works nicely.
I copy that exact same xml file in /etc/libvirt/qemu/ from my F17 partition to my F18 partition, and it Windows fails to boot. Windows complains of not seeing its drive. Here is the drive section in the XML definition:
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
Is there some virtio trick in F18 that I've missed to get it to work generally?
Version-Release number of selected component (if applicable):
$ uname -a
Linux hostname 3.7.2-204.fc18.x86_64 #1 SMP Wed Jan 16 16:22:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -qa | egrep "virt|kvm|qemu" | sort
Very similar issue here. Windows 7 32bit installed on Fedora 17 kvm. Now Fedora 18 kvm boots the Windows 7 guest, but it is extremely slow. It seems the virtio storage device is no longer available to the guest, and it falls back to a fake Intel IDE controller.
virtio-win-0.1-52.iso seems to not contain compatible virtio storage drivers for whatever Fedora 18 kvm is making available within the guest.
Sorry! False alarm. The virtio-blk device actually does work. I was seriously confused by a different bug where a new virtio win driver upgrade sometime in the last year began using 100% CPU on all cores.
Joshua, can you still reproduce with latest F18 bits?
Can you provide the full XML file, and /var/log/libvirt/qemu/$vmname.log?
Yes, I can still reproduce. Please find files you requested attached.
Created attachment 733940 [details]
Created attachment 733941 [details]
What kernel version was this?
Not sure of the F17 kernel version, sorry. I no longer have access to this machine.
Too bad. :(