Description of problem: When I want to install virtio drivers on a Windows 2008 R2 VM, I have a BSOD when I try to install virtio-serial driver. Version-Release number of selected component (if applicable): virtio-win-1.113-1 How reproducible: Always Steps to Reproduce: 1.Install virtio-serial driver 2. 3. Actual results: BSOD Expected results: Working driver to install ovirt-guest-agent
Hi, There is a bug on build 113 for win2008R2, it cannot be installed on windows2008R2 but not BSOD. More details refer: https://bugzilla.redhat.com/show_bug.cgi?id=1289406. Could you try with build117? Thanks wyu
Looks fine with build117 downloaded from here https://fedoraproject.org/wiki/Windows_Virtio_Drivers. But I now have a BSOD when installing balloon.sys or viostor.sys.
(In reply to Kevin Cousin from comment #3) > Looks fine with build117 downloaded from here > https://fedoraproject.org/wiki/Windows_Virtio_Drivers. > > But I now have a BSOD when installing balloon.sys or viostor.sys. It looks fine w/ both balloon and viostor (build 117) on our side. more info: qemu-kvm-rhev-2.5.0-4.el7.x86_64 kernel-3.10.0-382.el7.x86_64 seabios-1.7.5-11.el7.x86_64
All drivers from http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/ovirt-guest-tools-iso-3.6-3.fc23.noarch.rpm works great with Windows 2008 R2. I don't have any BSOD with this drivers.
Can you please double check with build 117? see comment#4 above.
I still have BSOD with build 117.
Created attachment 1161354 [details] VM screenshot
(In reply to Kevin Cousin from comment #8) > Created attachment 1161354 [details] > VM screenshot Can you please provide more information about your setup? We need to know kvm and qemu versions along with qemu command line. It also will be helpful if you can share the relevant crash dump files with us. Best regards, Vadim.
Here is the qemu command line : /usr/libexec/qemu-kvm -name CloneDPM -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu SandyBridge,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m size=8388608k,slots=16,maxmem=4294967296k -realtime mlock=off -smp 2,maxcpus=16,sockets=16,cores=1,threads=1 -numa node,nodeid=0,cpus=0-1,mem=8192 -uuid 16e83514-4119-44c6-87b1-1bb285f5e654 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-2.1511.el7.centos.2.10,serial=32333536-3030-5A43-3334-303831324C39,uuid=16e83514-4119-44c6-87b1-1bb285f5e654 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-CloneDPM/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2016-05-27T14:21:17,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot menu=on,strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x8.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x8 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x8.0x2 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x8.0x1 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x9 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive 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 -drive file=/rhev/data-center/ec214a92-5ebb-4411-a86a-6823fccacf26/f4d243d1-b2fc-4490-8f19-92fb99fac65a/images/86b90f25-010a-46e8-806e-6080903a1e8a/e2b347de-5125-4128-9f05-a5d68551ecd5,if=none,id=drive-virtio-disk0,format=qcow2,serial=86b90f25-010a-46e8-806e-6080903a1e8a,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -chardev socket,id=charserial0,path=/var/run/ovirt-vmconsole-console/16e83514-4119-44c6-87b1-1bb285f5e654.sock,server,nowait -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/16e83514-4119-44c6-87b1-1bb285f5e654.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/16e83514-4119-44c6-87b1-1bb285f5e654.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice port=5902,tls-port=5903,addr=172.20.69.23,x509-dir=/etc/pki/vdsm/libvirt-spice,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vgamem_mb=16,bus=pci.0,addr=0x2 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -chardev spicevmc,id=charredir2,name=usbredir -device usb-redir,chardev=charredir2,id=redir2 -chardev spicevmc,id=charredir3,name=usbredir -device usb-redir,chardev=charredir3,id=redir3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on I use oVirt 3.6.6 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.4.x86_64 qemu-img-ev-2.3.0-31.el7_2.10.1.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch qemu-kvm-common-ev-2.3.0-31.el7_2.10.1.x86_64 qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64 qemu-kvm-tools-ev-2.3.0-31.el7_2.10.1.x86_64
I cannot log into my Windows VM, i have BSOD on each boot. I will try to export VM disk.
Created attachment 1162773 [details] BSOD
(In reply to Kevin Cousin from comment #12) > Created attachment 1162773 [details] > BSOD First of all the problem is not with virtio-serial but with virtio-scsi. Second, according to the BSOD screen shot it looks like you installed a wrong driver (probably from Win8 directory, which is not a right location) For more information please visit the following links for more information: https://github.com/YanVugenfirer/kvm-guest-drivers-windows/issues/8#issuecomment-204406016 and https://bugzilla.redhat.com/show_bug.cgi?id=1296633 best regards, Vadim.
virtio-serial works fins with build117. BSOD with virtio-stor is another issue. I selected the CD drive in the driver window, so I thought Windows will choose the rightd driver. REgards
(In reply to Kevin Cousin from comment #14) > virtio-serial works fins with build117. > > BSOD with virtio-stor is another issue. I selected the CD drive in the > driver window, so I thought Windows will choose the rightd driver. ^^^^^^^^^^^^^ It can be a "right driver" because Vendor and Device IDs in .inf file are match Vendor and Device IDs reported by PCI, but it is not guaranteed that this particular driver is compatible with platform (OS) where you are trying to install it. Please always check if platform version in the highlighted by Windows Installer string matches the VM platform version. Best regards, Vadim. > > REgards