Bug 894277
| Summary: | Boot windows 8 guest BSoD after shutdown | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | mazhang <mazhang> | ||||||||||||
| Component: | qemu-kvm | Assignee: | Yvugenfi <yvugenfi> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | high | ||||||||||||||
| Version: | 6.4 | CC: | acathrow, areis, bcao, bsarathy, dfleytma, drjones, dyasny, flang, ghammer, juzhang, michen, mkenneth, mprpic, qzhang, rhod, virt-maint, vrozenfe, yvugenfi | ||||||||||||
| Target Milestone: | rc | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||||||||||
| Doc Text: |
"Fast startup" used in Microsoft Windows 8 is not fully compatible with qemu-kvm in Red Hat Enterprise Linux 6. Windows 8 can therefore fail to boot the second time after its shutdown. To ensure successful boot of Windows 8 inside qemu-kvm, disable Windows 8 "fast startup" in System Settings.
|
Story Points: | --- | ||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-02-19 13:57:42 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
mazhang
2013-01-11 09:48:23 UTC
Created attachment 676751 [details]
win8 dump file
Created attachment 676759 [details]
win8 dump file(export with windbg)
(In reply to comment #2) > Created attachment 676759 [details] > win8 dump file(export with windbg) Can you please run '!analyze -v' on the dmp from windbg and paste the output? Created attachment 676778 [details]
dump file
also bsod with follow command line: 1 win8-32 guest #/usr/libexec/qemu-kvm -M rhel6.4.0 -cpu SandyBridge,+sep -m 8G -smp 4,sockets=2,cores=2,threads=1,maxcpus=16 -enable-kvm -name win8-32 -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 -k en-us -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -monitor stdio -qmp tcp:0:6666,server,nowait -boot menu=on -bios /usr/share/seabios/bios.bin -drive file=/home/win8-32-install.qcow2,if=none,id=drive-scsi-disk,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0,addr=0x5 -device scsi-hd,drive=drive-scsi-disk,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk,bootindex=1 -chardev socket,path=/tmp/isa-serial,server,nowait,id=isa1 -device isa-serial,chardev=isa1,id=isa-serial1 -vga qxl -spice port=5900,disable-ticketing -device virtio-balloon-pci,id=balloon1,bus=pci.0,addr=0x8 -netdev tap,id=hostnet0,downscript=no -device e1000,netdev=hostnet0,id=net0,mac=00:1d:45:0d:3a:fe,bus=pci.0,addr=0x7,bootindex=2 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -drive file=/root/images/storage0.qcow2,if=none,id=drive-scsi-disk1,format=qcow2,cache=none,werror=stop,rerror=stop -device scsi-hd,drive=drive-scsi-disk1,bus=scsi0.0,scsi-id=0,lun=1,id=scsi-disk1 2 win8-64 guest #/usr/libexec/qemu-kvm -M rhel6.4.0 -cpu SandyBridge -m 8G -smp 4,sockets=2,cores=2,threads=1,maxcpus=16 -enable-kvm -name win8-64 -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 -k en-us -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -monitor stdio -qmp tcp:0:6666,server,nowait -boot menu=on -bios /usr/share/seabios/bios.bin -drive file=/home/win8-64-install.qcow2,if=none,id=drive-scsi-disk,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0,addr=0x5 -device scsi-hd,drive=drive-scsi-disk,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk,bootindex=1 -chardev socket,path=/tmp/isa-serial,server,nowait,id=isa1 -device isa-serial,chardev=isa1,id=isa-serial1 -vga qxl -spice port=5900,disable-ticketing -device virtio-balloon-pci,id=balloon1,bus=pci.0,addr=0x8 -netdev tap,id=hostnet0,downscript=no -device e1000,netdev=hostnet0,id=net0,mac=00:1d:45:0d:3a:fc,bus=pci.0,addr=0x7,bootindex=2 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -drive file=/root/images/storage0.qcow2,if=none,id=drive-scsi-disk1,format=qcow2,cache=none,werror=stop,rerror=stop -device scsi-hd,drive=drive-scsi-disk1,bus=scsi0.0,scsi-id=0,lun=1,id=scsi-disk1 Set blocker flag since the win8 hits BSOD and win8 is supported guest on rhel6.4. (In reply to comment #5) > Created attachment 676778 [details] > dump file Thanks. The symbol path wasn't setup, but we see that the bug check code is DRIVER_POWER_STATE_FAILURE, with subcode 3. From [1] we see that means "A device object has been blocking an IRP for too long a time." So maybe some I/O emulation is hanging in qemu? We should reproduce this while connected to qemu with gdb. After the BSOD we can can attempt to see what, if anything, qemu was attempting to do by looking at its backtrace. To do so, we need to make sure the guest is set to preserve on crash. Can you make the reproducing environment accessible for debug? [1] http://msdn.microsoft.com/en-us/library/ff559329%28v=vs.85%29.aspx Try connected to qemu with gdb, but after the BSOD, qemu will reboot ,did not quit, so I can't get backtrace. I found if without "-global PIIX4_PM.disable_s4=0" it will boot up without BSOD. Created attachment 676820 [details]
attach minidump of win8-64
Created attachment 676821 [details]
memory dump of win8-64
(In reply to comment #9) > Try connected to qemu with gdb, but after the BSOD, qemu will reboot ,did > not quit, so I can't get backtrace. > Did you configure the guest's on_crash to preserve? See http://libvirt.org/formatdomain.html#elementsEvents (In reply to comment #13) > (In reply to comment #9) > > Try connected to qemu with gdb, but after the BSOD, qemu will reboot ,did > > not quit, so I can't get backtrace. > > > > Did you configure the guest's on_crash to preserve? See > http://libvirt.org/formatdomain.html#elementsEvents boot guest by command line directly (refer #c0) caused by win8 fast startup ,close it should workaound it referring to http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html (In reply to comment #15) > caused by win8 fast startup ,close it should workaound it referring to > http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a. > html Deferring the fix to 6.5 and adding a "known issue" doc text. If this bug is reproduced Gal, please check if it is duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=846912 Closing as duplicate. I was able to reproduce this bug with the default BIOS and was unable to reproduce with a patched BIOS that doesn't allow interrupt disabling on LNKS. *** This bug has been marked as a duplicate of bug 846912 *** |