Taliesin,

By first reboot, do you mean that it installed fine on first run, just the reboot failed? Also, what version of kvm are you using? What linux distro are you using?

Can you try using the basic command line options from the example in the post and see if that makes a difference?

Henry,

I would try compiling a newer version of kvm or qemu-kvm to a specified location and testing with that. KVM-72 is pretty old. Try that and see if it works.

I know this is post is a bit old, but it's the first google result I got for this problem so maybe the following will help someone:

block virtio worked great for me on ubuntu 9.10, set up at install time on XP using the floppy image viostor-31-03-2010-floppy.img. After upgrading to 10.04, guests that had this driver installed BSOD on boot (or sometimes a bit later, at the login prompt):
DRIVER_CORRUPTED_MMPOOL
STOP: 0x000000D0 (0x00000008,0x00000002,0x0000000,0x8054A06C)

Switching to the driver found at http://www.linux-kvm.com/sites/default/files/viostor-xp-2010-02-06.iso appears to have fixed the problem. This is confusing because the version info is the same as on the floppy image (both in the file version resources and .inf) but the files are different:
viostor-31-03-2010-floppy.img \i386\WinXP md5sum
8b5e809a7f2b9821ff8b229f3bda9269 viostor.sys
viostor-xp-2010-02-06.iso \winxp\i386 md5sum
a584ba5c5b966b8eb15df7f772f97be9 viostor.sys

guests are 32 bit XP pro sp3.

Switching to IDE also makes the problem go away, with the obvious performance cost. (To my surprise XP didn't freak out when the SCSI disks suddenly became IDE). Used DEVMGR_SHOW_NONPRESENT_DEVICES to update the driver on the non-present SCSI controllers.

host is
2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux

QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3)

The 9.10 version of qemu was 0.11.?

host cpu
family:17 model:3 stepping:1
model name: AMD Athlon(tm) X2 Dual-Core QL-60

example command line
qemu -enable-kvm -soundhw ac97 -localtime -boot order=dca,menu=on -m 512 \
-cdrom /dev/cdrom \
-drive file=/home/reed/virtualmachines/xp-work.qcow,cache=writeback,index=0,if=virtio,boot=on,media=disk \
-drive file=/home/reed/virtualmachines/xp-data1.qcow,cache=writeback,index=1,if=virtio,media=disk \
-net nic,vlan=0,model=virtio,macaddr=52:54:00:12:69:02 -net tap,ifname=tap2,vlan=0,script=no,downscript=no \
-monitor stdio -vnc localhost:3

Clayton,

I'm curious. Is your host architecture AMD as well?

About the BSOD on 9.10->10.04 upgrade:

Unfortunately, I can't find the bugreport right now in Redhat bugzilla, but AFAIR there was a bug report there, related to upgrading RHEL 5 -> 6, which would cause BSOD due to changes in the hostside kernel/virtio-driver. As I remember it, the conclusion was that they needed to do a workaround fix inside qemu-kvm to allow moving of Windows guests with the old virtio-blk driver to a later host RHEL version. If the workaround wasn't implemented, users would have to upgrade the Windows block driver prior to upgrading the host system.

So, my guess is that a newer version (already released or upcoming) Windows block driver will be capable of the upgrade. Or a workaround fix in qemu-kvm (probably not likely outside qemu-kvm in RHEL).

As I wrote above, this is purely from my memory, so the information might be more less accurate...nevertheless, it seems to match your experience with ubuntu 10.04 (which uses a ~2.6.32 kernel like RHEL6).

Is it possible to use KVM virtio drivers with Windows 2008 64 bit? I noticed Win 2008 installer does not recognize the virtio drivers during the installation.

Hi, I just test it in Win2003.

Everything work fine before reboot, after it, just blank screen.

/usr/bin/qemu-kvm -S -M pc-0.11 -m 512 -smp 2 -name test -uuid 97d400c2-7bfa-a3dd-ff03-7c0046f829d4 -monitor unix:/var/lib/libvirt/qemu/test.monitor,server,nowait -localtime -boot c -drive file=,if=floppy,index=0 -drive file=/home/Arthur/[Windows.Server.2003.SP2].win2003.Enterprise.VOL_SP2_CN.iso,if=ide,media=cdrom,index=2 -drive file=/var/lib/libvirt/images/test.img,if=virtio,index=0,boot=on,format=raw -net nic,macaddr=52:54:00:08:ef:7f,vlan=0,name=nic.0 -net tap,fd=20,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:1 -k en-us -vga vmware -soundhw es1370

No more information I can provide.

Hi,

I'm working on KVM and I wanted to thank you for these drivers. Same for Network and vmware driver.

I'm running Windows server 2003 and 2008. First needs 2-3 seconds for booting only. It's pretty fast. For Windows 2008, sometimes it's slow, mouse pointer is not smooth but it's ok.

Hi Henry,

It is working on my side now, copying is ok. Try to copy all the driver files you needed to the root of the floppy image.

And it looks the unpublished option boot=on is needed. I lost the link, but you can search the discussion in kvm mail list, it is for virtio interface.

But it is not working on spice if you want to try it. The virtio of network is working, but block device is not yet till now. The spice team is working on one version of upstream qemu, not qemu-kvm, so not all up-to-date features are supported.

it happened to me. windows installation starts and then after a while it prompts you to insert cd/dvd for driver. i tried to burn on another disk and verify just to make sure it's not my dvd making the problem. this time it worked and it doesnt ask for any driver or anything. so i guess my previous windows 7 disk did not burn correctly, probably yours too.

I made an updated floppy image file with the current virtio driver for Windows XP (extracted from virtio-win-0.1-22.iso). It resolves the BSOD after first reboot for me. If anyone wants or needs it, please feel free to email me at ironiridis@gmail.com.

Your instructions worked perfectly. Installation of the XP guest was quite a bit quicker than using the IDE bus.

I have built an updated floppy image with the 2012 WinXP / Windows 2003 virtio drivers from the latest ISO (virtio-win-0.1-22.iso)

The "boot=on" command line option is now deprecated & I used:

#!/bin/sh
kvm -boot order=dca -m 512 \
-cdrom /home/user/KVM/WinXP_corporate.iso \
-drive file=/home/user/KVM/WinXP/WinXP.qcow2,if=virtio \
-fda /home/user/KVM/viostor-22-01-2012-floppy.img