Description of problem: When generating a WS2012R2 Image with virtio-win-0.1-81.iso, it will boot without any problems. When generating a WS2012R2 Image with virtio-win-0.1-94.iso, it will BSOD with IRQL_NOT_LESS_OR_EQUAL Version-Release number of selected component (if applicable): 0.94 How reproducible: Always Steps to Reproduce: 1. Generate a WS2012R2 2. Try to boot it 3. Actual results: BSOD Expected results: Boots Additional info: QEMU 2.2.0 Libvirt 1.2.11 Kernel 3.18.1
Hi David, Could you please provide the QEMU CLI and crash dump file if it is available? Thanks, Vadim.
Hello Vad, I'll try to get the crash dump but for the time being , I only have this: virt-install --connect qemu:///system --name WS2012R2 --ram 8192 --vcpus 2 --disk path=/var/images/tmp/WS2012R2.qcow2,format=qcow2,cache=none --disk path=/var/images/isos/virtio-win-0.1-94.iso,device=cdrom --vnc --os-type=windows --os-variant win2k8 --vnclisten 0.0.0.0 --noautoconsole --accelerate --noapic --keymap=en-us --network=bridge:br100,mac=fa:16:3e:09:b4:7b --force --cdrom /var/images/isos/ws2012r2.iso --disk path=unattend/Autounattend.vfd,device=floppy ws2012r2 contains almost all the latest patch. Dave
Hello Vad, I will take some times as I need to create a new image since I deleted the old one. I'm generating a new one with the new drivers in order to get a crash dump for you. Thank you very much, Dave
Hello again, Another thing I need to precise is that I'm generating an image with qemu (and jenkins and friends) and then send it to glance/openstack. Then a bunch of tests are done on this image and as soon as the VM boots for the first time after the installation of the virtio drivers it will simply BSOD with IRQL_NOT_LESS_OR_EQUAL and then nothing can be done to recover the server. Dave
(In reply to David Hill from comment #4) > Hello again, > Another thing I need to precise is that I'm generating an image with > qemu (and jenkins and friends) and then send it to glance/openstack. Then a > bunch of tests are done on this image and as soon as the VM boots for the > first time after the installation of the virtio drivers it will simply BSOD > with IRQL_NOT_LESS_OR_EQUAL and then nothing can be done to recover the > server. > Dave Try doing the following thing; for storage stack - replace virtio-blk(scsi) device with ide, for other stacks - just remove virtio devices one by one from the command line. It will give you pretty good indication about which driver/stack is broken. Vadim.
It is a known issue dup of https://bugzilla.redhat.com/show_bug.cgi?id=1168119 which will be fixed in future version. I personal recommend you using stable one (build81). Mike
Hi Mike, Where can we have a list of what is stable/unstable? Because when I go to the virtio webpage, they link to the fedora people page with the 0.1-94 version only. Dave
When visiting fedoraproject site http://alt.fedoraproject.org/pub/alt/virtio-win/ you will see two folders - stable and latest Stable is almost equal to the latest official virtio-win package released with the latest RHEL version. Latest is just one of the latest internal builds created for testing purpose. Some sort of preview, nothing more.
Thanks for the information! We like to be bleeding edge here and for some reasons, I like finding bugs ! We have an automated build system that tests latest versions against all centos 6/centos 7/windows server 2008r2, 2012 and 2012r2. I'll keep in mind I'm using the latest virtio which isn't stable sometimes. ;) I guess you can close this bug . Dave
*** This bug has been marked as a duplicate of bug 1168119 ***