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: <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/VolGrpSlow0/vm_WinBloze7'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> 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 ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarch libvirt-0.10.2.2-3.fc18.x86_64 libvirt-client-0.10.2.2-3.fc18.x86_64 libvirt-daemon-0.10.2.2-3.fc18.x86_64 libvirt-daemon-config-network-0.10.2.2-3.fc18.x86_64 libvirt-daemon-config-nwfilter-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-interface-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-lxc-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-network-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-nodedev-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-nwfilter-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-qemu-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-secret-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-storage-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-uml-0.10.2.2-3.fc18.x86_64 libvirt-daemon-driver-xen-0.10.2.2-3.fc18.x86_64 libvirt-daemon-kvm-0.10.2.2-3.fc18.x86_64 libvirt-gconfig-0.1.5-1.fc18.x86_64 libvirt-glib-0.1.5-1.fc18.x86_64 libvirt-gobject-0.1.5-1.fc18.x86_64 libvirt-python-0.10.2.2-3.fc18.x86_64 python-virtinst-0.600.3-2.fc18.noarch qemu-common-1.2.2-2.fc18.x86_64 qemu-img-1.2.2-2.fc18.x86_64 qemu-kvm-1.2.2-2.fc18.x86_64 qemu-kvm-tools-1.2.2-2.fc18.x86_64 qemu-system-x86-1.2.2-2.fc18.x86_64 virt-dmesg-0.3.0-6.fc18.x86_64 virt-manager-0.9.4-4.fc18.noarch virt-manager-common-0.9.4-4.fc18.noarch virt-top-1.0.8-3.fc18.x86_64 virt-what-1.12-2.fc18.x86_64 virt-who-0.2-3.fc18.noarch
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.
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ 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. Joshua
Created attachment 733940 [details] log
Created attachment 733941 [details] xml file
What kernel version was this?
Not sure of the F17 kernel version, sorry. I no longer have access to this machine.
Too bad. :(