Bug 1308276 - windows BSOD on restart with qemu-kvm.x86_64 2:2.5.0-5.fc23
Summary: windows BSOD on restart with qemu-kvm.x86_64 2:2.5.0-5.fc23
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-13 23:50 UTC by John L Magee
Modified: 2016-03-05 17:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-05 17:54:21 UTC
Type: Bug


Attachments (Terms of Use)
windows config from msinfo32 (476.54 KB, text/plain)
2016-02-14 11:55 UTC, John L Magee
no flags Details
log snippet with qemu command line (3.30 KB, text/plain)
2016-02-14 11:57 UTC, John L Magee
no flags Details
xml definition for the failing VM (4.08 KB, text/plain)
2016-02-15 19:33 UTC, John L Magee
no flags Details

Description John L Magee 2016-02-13 23:50:01 UTC
Description of problem: Following update to qemu-kvm.x86_64 2:2.5.0-5.fc23 
Windows restart gets BSOD with driver_irql_not_less_or_equal. dirver not specified on screen


Version-Release number of selected component (if applicable):
qemu-kvm.x86_64 2:2.5.0-5.fc23 

How reproducible:
every attempt to restart windows

Steps to Reproduce:
1.boot windows VM  (win7)
2.attempt windows restart
3.

Actual result: BSOD


Expected results: clean restart


Additional info: clean shutdown followed by boot works fine

I've downgraded qemu without gathering any diagnostic data. Let me know if you need additional info and I'll try to get it for you

Comment 1 Cole Robinson 2016-02-14 02:34:38 UTC
Please provide the full qemu command line. This is /var/log/libvirt/qemu/$YOUR-VM-NAME.log if using libvirt

If your VM is using virtio windows drivers, do you know what version they were installed with? Maybe try updating. Get the bits from here, attach the cdrom to the VM, do a manual driver update.

https://fedoraproject.org/wiki/Windows_Virtio_Drivers

Comment 2 John L Magee 2016-02-14 11:55:46 UTC
Created attachment 1127017 [details]
windows config from msinfo32

The driver file versions and installation dates are in this file.

Comment 3 John L Magee 2016-02-14 11:57:11 UTC
Created attachment 1127023 [details]
log snippet with qemu command line

Comment 4 John L Magee 2016-02-14 12:06:02 UTC
The requested log entries are now attached. One diagnostic step I tried was to create a new VM definition with all addresses deleted so libvirt could create everything clean. This log entry was from after that update. I'm still running that configuration with qemu-2.4.1

I installed the virtio-win drivers from the latest virtio-win package on 12-17-2015 as you can see in the attached msinfo32 text file. (You may recall I pinged you about the fact there is no qxl driver in that package.)

Comment 5 Cole Robinson 2016-02-15 17:23:35 UTC
Can you post the libvirt XML as well? sudo virsh dumpxml $VM-NAME

I'll try and reproduce.

Comment 6 John L Magee 2016-02-15 19:33:59 UTC
Created attachment 1127420 [details]
xml definition for the failing VM

Comment 7 John L Magee 2016-03-05 17:53:40 UTC
I installed qemu.x86_64 2:2.5.0-8.fc23  and associated libvirt updates from virt-preview and now everything is working fine.


Thanks for listening

Comment 8 John L Magee 2016-03-05 17:54:21 UTC
notabug anymore


Note You need to log in before you can comment on or make changes to this bug.