Bug 1133228

(In reply to dernikov from comment #0)
> Description of problem:
> 
> Try to install driver for fake virtio disk.
> During virtio disk driver installation (virtio-win-0.1-81), got BSOD in VM
> Windows 2003 R2 (virtio-win-0.1-81). 
> Repeat once more, same behaviour BSOD two seconds after started driver
> installation. 
> 
> Version-Release number of selected component (if applicable):
> 
> Virtual maschine OS W2003 R2 (IDE DISK)
> virtio-win-0.1-81.iso
> 
> Host mashine Quad Core Phenom II X4
> OS:Proxmox pvetest (Debian wheezy)
> kernel:pve-kernel-2.6.32-32-pve
> pve-qemu-kvm                          2.1-3
> 
> How reproducible: Easy
> 
> Steps to Reproduce:
> 1.Add virtio fake disk to VM definition, add virtio-win-0.1-81.iso as cd
> 2.Start VM 
> 3.Try to install virtio disk driver 
> 
> Two seconds after BSOD
> 
> Actual results:
> Two seconds after BSOD
> 
> 
> Expected results:
> Installed virtio disk driver 
> 
> Additional info:

Hi,
We usually don't deal with Debian. So, it will be better if you can reproduce
this issue on any of RH products.

In any case, please provide the following information:
- BSOD bugcheck information or screenshot with BSOD information,
- qemu command line,
- steps, you followed, when installing virtio disk.

Thanks,
Vadim.

(In reply to Vadim Rozenfeld from comment #1)
> (In reply to dernikov from comment #0)
> > Description of problem:
> > 
> > Try to install driver for fake virtio disk.
> > During virtio disk driver installation (virtio-win-0.1-81), got BSOD in VM
> > Windows 2003 R2 (virtio-win-0.1-81). 
> > Repeat once more, same behaviour BSOD two seconds after started driver
> > installation. 
> > 
> > Version-Release number of selected component (if applicable):
> > 
> > Virtual maschine OS W2003 R2 (IDE DISK)
> > virtio-win-0.1-81.iso
> > 
> > Host mashine Quad Core Phenom II X4
> > OS:Proxmox pvetest (Debian wheezy)
> > kernel:pve-kernel-2.6.32-32-pve
> > pve-qemu-kvm                          2.1-3
> > 
> > How reproducible: Easy
> > 
> > Steps to Reproduce:
> > 1.Add virtio fake disk to VM definition, add virtio-win-0.1-81.iso as cd
> > 2.Start VM 
> > 3.Try to install virtio disk driver 
> > 
> > Two seconds after BSOD
> > 
> > Actual results:
> > Two seconds after BSOD
> > 
> > 
> > Expected results:
> > Installed virtio disk driver 
> > 
> > Additional info:
> 
> Hi,
> We usually don't deal with Debian. So, it will be better if you can reproduce
> this issue on any of RH products.
> 
> In any case, please provide the following information:
> - BSOD bugcheck information or screenshot with BSOD information,
> - qemu command line,
> - steps, you followed, when installing virtio disk.
> 
> Thanks,
> Vadim.

Thank for answer, sorry for late response. 
I am out of work for three weeks so i will try as you suggested, after return.
Do you have advice how to capture VM BSOD, because it happen to fast for screen capture.
For virtio disk, i simple add disk as virtio type 1GB size, with VM shut down that is all.
For qemu command i will try to find in logs which commnad proxmox execute.
Tnaks for support.

(In reply to dernikov from comment #2)
> Do you have advice how to capture VM BSOD, because it happen to fast for
> screen capture.

Try disabling "Automatically restart" option as described in
http://support.microsoft.com/kb/2621246

Vadim.

I get same issue, install virtio-win-0.1-81.iso disk drivers on windows 2003 virtual machines and immediately get BSOD ...pretty sure the error is 0x00007F but the screen is very quick to disappear. Host is Ubuntu 14.10, and the problem occurs on multiple windows 2003 virtual machines. 

Question - is there a way to remove the drivers once you get into this situation?

Is there a know good driver for windows 2003 disks (using qcow 2 format). Think in past I used version virtio-win-0.1-59.iso that worked on windows 2003. Should I just stick to that version ?

Sorry for lack of details - let me know if you would like me to provide any further debug, and how to do this.

(In reply to David Herring from comment #4)
> I get same issue, install virtio-win-0.1-81.iso disk drivers on windows 2003
> virtual machines and immediately get BSOD ...pretty sure the error is
> 0x00007F but the screen is very quick to disappear. Host is Ubuntu 14.10,
> and the problem occurs on multiple windows 2003 virtual machines. 
> 
> Question - is there a way to remove the drivers once you get into this
> situation?

Try switching disk type to IDE. It should work in any case.

> 
> Is there a know good driver for windows 2003 disks (using qcow 2 format).
> Think in past I used version virtio-win-0.1-59.iso that worked on windows
> 2003. Should I just stick to that version ?
> 
> Sorry for lack of details - let me know if you would like me to provide any
> further debug, and how to do this.

installed W2K3 without any problem on virtio-blk system disk with drivers from build 92 (viostor.sys for W2K3 is absolutely identical in builds 81 and 92)

qemu command line:
sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 -cpu host -m 1G -smp 2 -no-hpet -boot dc -drive file=/home/vrozenfe/work/images/w2k3.qcow2,if=none,id=drive-virtio0,cache=off,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:24:AE:93:CF:83,id=net0 -uuid e24af923-4b9b-4419-97b4-da6fe8fb7062 -monitor stdio -name W2K3-test -vga cirrus -cdrom /home/share/isos/Windows2003_r2_VLK.iso -fda /home/share/builds/usr/share/virtio-win/virtio-win.vfd -enable-kvm

qemu 2.0.95
kernel 3.15.10-201.fc20.x86_64

Thanks for the response. Switching the windows KVM back to IDE drivers for disks does not fix the booting problem.

Here is the command line for how I am running my virtual machines, if it is useful.

libvirt+ 31735     1 17 Oct09 ?        09:20:24 qemu-system-x86_64 -enable-kvm -name rbs1 -S -machine pc-1.2,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 29c10ed8-e6bb-224b-30ca-d7feb06ac8ee -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/rbs1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/rbs1.snapshotrbs11,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:e2:db:c4,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=52:54:00:ea:f8:59,bus=pci.0,addr=0x7 -netdev tap,fd=29,id=hostnet2 -device rtl8139,netdev=hostnet2,id=net2,mac=52:54:00:4f:73:00,bus=pci.0,addr=0x8 -netdev tap,fd=30,id=hostnet3 -device rtl8139,netdev=hostnet3,id=net3,mac=52:54:00:4d:10:10,bus=pci.0,addr=0x9 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:3 -device VGA,id=video0,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5



From reading the thread below, I will try the virtio-win-0.1-30.iso version, which appears to be good for Windows 2003.

http://forum.proxmox.com/threads/12568-new-virtio-0-1-52-Windows-drivers-available

The virtio-win-0.1-30.iso drivers do work on my systems - so sticking with these for now. Happy to provide debug / info as required. Details of system below:- 

$ uname -a
Linux big3.netfm.org 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ uname -r
3.13.0-37-generic

$ kvm --version
QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.5), Copyright (c) 2003-2008 Fabrice Bellard
dave@big3:~$ 


Note this is version 2.0.0 and Vadim above has 2.0.95 ....i s that relevant ?

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

There are newer public drivers available, but at a new URL:

https://fedoraproject.org/wiki/Windows_Virtio_Drivers#Direct_download

Can you test with the stable version and see if you still hit issues? If that is still failing, try the 'latest' version too

Closing as CURRENTRELEASE, but if anyone can still reproduce with the latest drivers, please reopen

viostor.sys is causing a BSOD for me with Win 7, all the latest updates.  
Using Ovirt 3.6.1 and  Ovirt Tools 3.6.0_0.2

(In reply to Blaster from comment #12)
> viostor.sys is causing a BSOD for me with Win 7, all the latest updates.  
> Using Ovirt 3.6.1 and  Ovirt Tools 3.6.0_0.2

Can you please specify the driver's version, qemu command line, and BSOD's bugcheck code?

Thanks,
Vadim.

I installed a 2008 server with virtio-win-0.1-30.iso  it worked, I updated the microsoft with all the updates, it worked. Then i loaded virtio-win-0.1.141.iso (latest stabele) then I get a BSOD. I undefined the vm and recreated it with IDE drives, still BSOD. How do I remove the driver? from the rescure CMD?

/usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 4096 -smp 2,sockets=2,cores=1,threads=1 -name mediaweb.powercraft.nl -uuid cff0d278-98ad-a207-02f3-136c0cba12bb -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/mediaweb.powercraft.nl.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/lvm2-vol/kvm21-disk,if=none,id=drive-ide0-0-0,format=raw -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/dev/lvm2-vol/kvm21-storage,if=none,id=drive-ide0-0-1,format=raw -device ide-hd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/images/virtio-win-0.1-30.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=34,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:28:c0:bb,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:3 -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4

workaround!: then reboot, uninstall the virtio drivers, checkbox remove from system, then reinstall with the virtio-win-0.1-30.iso

root@krystal:~# sudo mount -t ntfs-3g -o rw,loop,offset=105906176 /dev/lvm2-vol/kvm21-disk /mnt/windows/
root@krystal:~# find /mnt/windows/ -iname \*viostor.sys\* -print
/mnt/windows/Windows/System32/drivers/viostor.sys
/mnt/windows/Windows/System32/DriverStore/FileRepository/viostor.inf_amd64_neutral_5ba4c926d286f084/viostor.sys
/mnt/windows/Windows/System32/DriverStore/FileRepository/viostor.inf_amd64_neutral_ca049ce7e80f4177/viostor.sys
root@krystal:~# mv /mnt/windows/Windows/System32/drivers/viostor.sys /mnt/windows/Windows/System32/drivers/disabled.viostor.sys.disabled
root@krystal:~# mv /mnt/windows/Windows/System32/DriverStore/FileRepository/viostor.inf_amd64_neutral_5ba4c926d286f084/viostor.sys /mnt/windows/Windows/System32/DriverStore/FileRepository/viostor.inf_amd64_neutral_5ba4c926d286f084/disabled.viostor.sys.disabled
root@krystal:~# mv /mnt/windows/Windows/System32/DriverStore/FileRepository/viostor.inf_amd64_neutral_ca049ce7e80f4177/viostor.sys /mnt/windows/Windows/System32/DriverStore/FileRepository/viostor.inf_amd64_neutral_ca049ce7e80f4177/disabledviostor.sys.disabled
root@krystal:~# umount /mnt/windows