Hide Forgot
Created attachment 1216321 [details] bsod detail info Description of problem: Windows 7 Ultimate 32 bit bsod 0x50 when boot Version-Release number of selected component (if applicable): kernel ver: 3.10.0-327.28.3.el7.x86_64 qemu ver: qemu-kvm-rhev-2.3.0-32.el7. How reproducible: Steps to Reproduce: 1. Install win7 Ultimate 32bit(7601.17514), and then install standard spice guest version spice-guest-tools-0.100 2. With windows task scheduler making VM to auto restart in there mins, the vm will bsod 0x50 in a single boot 3. Actual results: VM BSOD Expected results: VM not BSOD Additional info: qemu cmd line:/usr/libexec/qemu-kvm -name i-00000025 -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu IvyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid a9af1a93-c2df-4965-bad9-ea9aa7fd6e29 -smbios type=1,manufacturer=Fedora Project,product=OpenStack Nova,version=12.0.0-4,serial=f8474f12-f24f-45e9-b702-00f3c6fe7cc8,uuid=a9af1a93-c2df-4965-bad9-ea9aa7fd6e29,family=Virtual Machine -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-i-00000025/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/opt/ssd/volume-bd8d9e5e-9971-48fa-a86d-0385a276fdd4,if=none,id=drive-virtio-disk0,format=qcow2,serial=bd8d9e5e-9971-48fa-a86d-0385a276fdd4,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/etc/thor/virtio-win-1.1.16.vfd,if=none,id=drive-fdc0-0-0,readonly=on,format=raw -global isa-fdc.driveA=drive-fdc0-0-0 -drive file=/var/lib/nova/instances/a9af1a93-c2df-4965-bad9-ea9aa7fd6e29/guest_meta/guest_meta.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/opt/nfs/iso/Windows_Win7SP1.7601.17514.101119-1850.X86FRE.Symbols.msi.iso,if=none,id=drive-ide0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=40 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:1a:0c:5d,bus=pci.0,addr=0x3 -chardev socket,id=charserial0,host=127.0.0.1,port=4445,server,nowait -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -chardev socket,id=charchannel1,path=/tmp/extra_channles/a9af1a93-c2df-4965-bad9-ea9aa7fd6e29/com.morningcloud.tcloud,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.morningcloud.tcloud -chardev socket,id=charchannel2,path=/tmp/extra_channles/a9af1a93-c2df-4965-bad9-ea9aa7fd6e29/com.morningcloud.tcloud.multimedia,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.morningcloud.tcloud.multimedia -device usb-tablet,id=input0 -vnc 0.0.0.0:24 -k en-us -spice port=5925,addr=0.0.0.0,agent-mouse=on,disable-ticketing,image-compression=auto_glz,streaming-video=filter,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,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=0x8 -msg timestamp=on cpu: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz bsod detail info see attachement.
Thank you for reporting this issue. Will it be possible to upload the crash dump file itself? Best regards, Vadim.
Created attachment 1216346 [details] bsod0x50 mini dump
Thanks, Can you try temporary switching system disk from virtio to ide, or at least trying to boot in safe mode, to see if it makes any difference? Can you also check the cpu microcode update version? It might be that you are hitting the following issue: Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page Translation when EPT is enabled" http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e5-v2-spec-update.pdf Best regards, Vadim.
(In reply to Vadim Rozenfeld from comment #3) > Thanks, > > Can you try temporary switching system disk from virtio to ide, or at least > trying to boot in safe mode, to see if it makes any difference? > > Can you also check the cpu microcode update version? It might be that you > are hitting the following issue: > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > Translation when EPT is enabled" > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > updates/xeon-e5-v2-spec-update.pdf > > Best regards, > Vadim. Thanks, dmesg | grep -i microcode [ 0.000000] CPU0 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.141659] CPU1 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.157111] CPU2 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.171889] CPU3 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.186671] CPU4 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.201467] CPU5 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.216729] CPU6 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.309445] CPU7 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.324180] CPU8 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.338913] CPU9 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.353651] CPU10 microcode updated early to revision 0x428, date = 2014-05-29 [ 0.368397] CPU11 microcode updated early to revision 0x428, date = 2014-05-29 [ 1.258417] microcode: CPU0 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258429] microcode: CPU1 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258443] microcode: CPU2 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258464] microcode: CPU3 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258473] microcode: CPU4 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258481] microcode: CPU5 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258490] microcode: CPU6 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258496] microcode: CPU7 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258503] microcode: CPU8 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258521] microcode: CPU9 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258529] microcode: CPU10 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258542] microcode: CPU11 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258552] microcode: CPU12 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258563] microcode: CPU13 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258573] microcode: CPU14 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258595] microcode: CPU15 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258603] microcode: CPU16 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258610] microcode: CPU17 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258617] microcode: CPU18 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258625] microcode: CPU19 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258634] microcode: CPU20 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258641] microcode: CPU21 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258657] microcode: CPU22 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258669] microcode: CPU23 sig=0x306e4, pf=0x1, revision=0x428 [ 1.258710] microcode: Microcode Update Driver: v2.00
It may not caused by cpu microcode, in my env, bsod asm code is mov dx, word ptr[eax] not same as intel cpu spec mov cr3, **
(In reply to uljtg from comment #5) > (In reply to Vadim Rozenfeld from comment #3) > > Thanks, > > > > Can you try temporary switching system disk from virtio to ide, or at least > > trying to boot in safe mode, to see if it makes any difference? > > > > Can you also check the cpu microcode update version? It might be that you > > are hitting the following issue: > > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > > Translation when EPT is enabled" > > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > > updates/xeon-e5-v2-spec-update.pdf > > > > Best regards, > > Vadim. > > Thanks, > > dmesg | grep -i microcode > > [ 0.000000] CPU0 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.141659] CPU1 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.157111] CPU2 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.171889] CPU3 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.186671] CPU4 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.201467] CPU5 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.216729] CPU6 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.309445] CPU7 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.324180] CPU8 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.338913] CPU9 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.353651] CPU10 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.368397] CPU11 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 1.258417] microcode: CPU0 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258429] microcode: CPU1 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258443] microcode: CPU2 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258464] microcode: CPU3 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258473] microcode: CPU4 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258481] microcode: CPU5 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258490] microcode: CPU6 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258496] microcode: CPU7 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258503] microcode: CPU8 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258521] microcode: CPU9 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258529] microcode: CPU10 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258542] microcode: CPU11 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258552] microcode: CPU12 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258563] microcode: CPU13 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258573] microcode: CPU14 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258595] microcode: CPU15 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258603] microcode: CPU16 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258610] microcode: CPU17 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258617] microcode: CPU18 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258625] microcode: CPU19 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258634] microcode: CPU20 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258641] microcode: CPU21 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258657] microcode: CPU22 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258669] microcode: CPU23 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258710] microcode: Microcode Update Driver: v2.00 (In reply to Vadim Rozenfeld from comment #3) > Thanks, > > Can you try temporary switching system disk from virtio to ide, or at least > trying to boot in safe mode, to see if it makes any difference? > > Can you also check the cpu microcode update version? It might be that you > are hitting the following issue: > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > Translation when EPT is enabled" > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > updates/xeon-e5-v2-spec-update.pdf > > Best regards, > Vadim. I will try to update the cpu microcode to check the problem exist. Thanks.
(In reply to uljtg from comment #5) > (In reply to Vadim Rozenfeld from comment #3) > > Thanks, > > > > Can you try temporary switching system disk from virtio to ide, or at least > > trying to boot in safe mode, to see if it makes any difference? > > > > Can you also check the cpu microcode update version? It might be that you > > are hitting the following issue: > > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > > Translation when EPT is enabled" > > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > > updates/xeon-e5-v2-spec-update.pdf > > > > Best regards, > > Vadim. > > Thanks, > > dmesg | grep -i microcode > > [ 0.000000] CPU0 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.141659] CPU1 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.157111] CPU2 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.171889] CPU3 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.186671] CPU4 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.201467] CPU5 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.216729] CPU6 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.309445] CPU7 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.324180] CPU8 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.338913] CPU9 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.353651] CPU10 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 0.368397] CPU11 microcode updated early to revision 0x428, date = > 2014-05-29 > [ 1.258417] microcode: CPU0 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258429] microcode: CPU1 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258443] microcode: CPU2 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258464] microcode: CPU3 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258473] microcode: CPU4 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258481] microcode: CPU5 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258490] microcode: CPU6 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258496] microcode: CPU7 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258503] microcode: CPU8 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258521] microcode: CPU9 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258529] microcode: CPU10 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258542] microcode: CPU11 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258552] microcode: CPU12 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258563] microcode: CPU13 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258573] microcode: CPU14 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258595] microcode: CPU15 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258603] microcode: CPU16 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258610] microcode: CPU17 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258617] microcode: CPU18 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258625] microcode: CPU19 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258634] microcode: CPU20 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258641] microcode: CPU21 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258657] microcode: CPU22 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258669] microcode: CPU23 sig=0x306e4, pf=0x1, revision=0x428 > [ 1.258710] microcode: Microcode Update Driver: v2.00 (In reply to Vadim Rozenfeld from comment #3) > Thanks, > > Can you try temporary switching system disk from virtio to ide, or at least > trying to boot in safe mode, to see if it makes any difference? > > Can you also check the cpu microcode update version? It might be that you > are hitting the following issue: > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > Translation when EPT is enabled" > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > updates/xeon-e5-v2-spec-update.pdf > > Best regards, > Vadim. I will try to update the cpu microcode to check the problem exist or not. Thanks.
(In reply to uljtg from comment #8) > (In reply to uljtg from comment #5) > > (In reply to Vadim Rozenfeld from comment #3) > > > Thanks, > > > > > > Can you try temporary switching system disk from virtio to ide, or at least > > > trying to boot in safe mode, to see if it makes any difference? > > > > > > Can you also check the cpu microcode update version? It might be that you > > > are hitting the following issue: > > > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > > > Translation when EPT is enabled" > > > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > > > updates/xeon-e5-v2-spec-update.pdf > > > > > > Best regards, > > > Vadim. > > > > Thanks, > > > > dmesg | grep -i microcode > > > > [ 0.000000] CPU0 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.141659] CPU1 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.157111] CPU2 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.171889] CPU3 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.186671] CPU4 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.201467] CPU5 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.216729] CPU6 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.309445] CPU7 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.324180] CPU8 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.338913] CPU9 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.353651] CPU10 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 0.368397] CPU11 microcode updated early to revision 0x428, date = > > 2014-05-29 > > [ 1.258417] microcode: CPU0 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258429] microcode: CPU1 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258443] microcode: CPU2 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258464] microcode: CPU3 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258473] microcode: CPU4 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258481] microcode: CPU5 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258490] microcode: CPU6 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258496] microcode: CPU7 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258503] microcode: CPU8 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258521] microcode: CPU9 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258529] microcode: CPU10 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258542] microcode: CPU11 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258552] microcode: CPU12 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258563] microcode: CPU13 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258573] microcode: CPU14 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258595] microcode: CPU15 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258603] microcode: CPU16 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258610] microcode: CPU17 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258617] microcode: CPU18 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258625] microcode: CPU19 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258634] microcode: CPU20 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258641] microcode: CPU21 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258657] microcode: CPU22 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258669] microcode: CPU23 sig=0x306e4, pf=0x1, revision=0x428 > > [ 1.258710] microcode: Microcode Update Driver: v2.00 > > (In reply to Vadim Rozenfeld from comment #3) > > Thanks, > > > > Can you try temporary switching system disk from virtio to ide, or at least > > trying to boot in safe mode, to see if it makes any difference? > > > > Can you also check the cpu microcode update version? It might be that you > > are hitting the following issue: > > Intel Xeon Processor E5 v2 Product Family: CA135 May 2014 -"Incorrect Page > > Translation when EPT is enabled" > > http://www.intel.com/content/dam/www/public/us/en/documents/specification- > > updates/xeon-e5-v2-spec-update.pdf > > > > Best regards, > > Vadim. > > I will try to update the cpu microcode to check the problem exist or not. > Thanks. In my env, microcode version: microcode_ctl-2.1-12.el7.x86_64 I can't find any newest version can be used in my env. How can i try next step? Thanks.
Thanks, Just for the record, this issue started to happen right after installing spice-guest-tools-0.100, right? Is it a permanent problem, happens on every (re-)reboot? bsod 0x50 is the only crash that you see on your system? Moving forward, we can try the following steps: - Changing system disk type from virtio to ide - or try booting into Safe mode. Best regards, Vadim.
(In reply to Vadim Rozenfeld from comment #10) > Thanks, > > Just for the record, this issue started to happen right after installing > spice-guest-tools-0.100, right? Is it a permanent problem, happens on every > (re-)reboot? > bsod 0x50 is the only crash that you see on your system? > > Moving forward, we can try the following steps: > - Changing system disk type from virtio to ide > - or try booting into Safe mode. > > Best regards, > Vadim. Not happen on every reboot Only happen in little probability, but can be reproduced with steps below in my env. Steps to Reproduce: 1. Install win7 Ultimate 32bit(7601.17514), and then install standard spice guest version spice-guest-tools-0.100 2. With windows task scheduler making VM to auto restart in there mins, the vm will bsod 0x50 in a single boot 3.
(In reply to uljtg from comment #11) > (In reply to Vadim Rozenfeld from comment #10) > > Thanks, > > > > Just for the record, this issue started to happen right after installing > > spice-guest-tools-0.100, right? Is it a permanent problem, happens on every > > (re-)reboot? > > bsod 0x50 is the only crash that you see on your system? > > > > Moving forward, we can try the following steps: > > - Changing system disk type from virtio to ide > > - or try booting into Safe mode. > > > > Best regards, > > Vadim. > > Not happen on every reboot > > Only happen in little probability, but can be reproduced with steps below in > my env. > > Steps to Reproduce: > 1. Install win7 Ultimate 32bit(7601.17514), and then install standard spice > guest version spice-guest-tools-0.100 > 2. With windows task scheduler making VM to auto restart in there mins, the > vm will bsod 0x50 in a single boot > 3. but it happens on reboots only or also during fresh boots? in any case we can try enabling some driver verifier options and hopefully get more information: Start > type "verifier" without the quotes > Select the following options - 1. Select - "Create custom settings (for code developers)" 2. Select - "Select individual settings from a full list" 3. Check the following boxes - - Special Pool - Pool Tracking - Force IRQL Checking - Deadlock Detection - Security Checks - Miscellaneous Checks 4. Select - "Select driver names from a list" 5. Click on the "Provider" tab. This will sort all of the drivers by the provider. 6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation (viostor and vioser in your case) 7. Click on Finish. 8. Restart.
(In reply to Vadim Rozenfeld from comment #12) > (In reply to uljtg from comment #11) > > (In reply to Vadim Rozenfeld from comment #10) > > > Thanks, > > > > > > Just for the record, this issue started to happen right after installing > > > spice-guest-tools-0.100, right? Is it a permanent problem, happens on every > > > (re-)reboot? > > > bsod 0x50 is the only crash that you see on your system? > > > > > > Moving forward, we can try the following steps: > > > - Changing system disk type from virtio to ide > > > - or try booting into Safe mode. > > > > > > Best regards, > > > Vadim. > > > > Not happen on every reboot > > > > Only happen in little probability, but can be reproduced with steps below in > > my env. > > > > Steps to Reproduce: > > 1. Install win7 Ultimate 32bit(7601.17514), and then install standard spice > > guest version spice-guest-tools-0.100 > > 2. With windows task scheduler making VM to auto restart in there mins, the > > vm will bsod 0x50 in a single boot > > 3. > > but it happens on reboots only or also during fresh boots? > in any case we can try enabling some driver verifier options > and hopefully get more information: > > Start > type "verifier" without the quotes > Select the following options - > > 1. Select - "Create custom settings (for code developers)" > 2. Select - "Select individual settings from a full list" > 3. Check the following boxes - > - Special Pool > - Pool Tracking > - Force IRQL Checking > - Deadlock Detection > - Security Checks > - Miscellaneous Checks > 4. Select - "Select driver names from a list" > 5. Click on the "Provider" tab. This will sort all of the drivers by the > provider. > 6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation > (viostor and vioser in your case) > 7. Click on Finish. > 8. Restart. Enable the verifier OS BSOD at 0xCD when boot. minidump see attachment.
Created attachment 1216884 [details] enable verifier BSOD minidump
(In reply to uljtg from comment #14) > Created attachment 1216884 [details] > enable verifier BSOD minidump Thanks a lot. Can you try changing memory dump options from "small memory dump" to "kernel memory dump", and upload a fresh crashdump file? (btw, it is always a good idea to compress crashdump files before uploading). Best regards, Vadim.
(In reply to Vadim Rozenfeld from comment #15) > (In reply to uljtg from comment #14) > > Created attachment 1216884 [details] > > enable verifier BSOD minidump > > Thanks a lot. > Can you try changing memory dump options from "small memory dump" to "kernel > memory dump", and upload a fresh crashdump file? (btw, it is always a good > idea to compress crashdump files before uploading). > Best regards, > Vadim. Sorry, when i use .dump /ma file to gen dump file windbg give me "Extra character error in .dump /ma mem.dmp". I have try to debug the BSOD use windbg. I hvae found the problem occured in rltinitunicodeex when test pszSrc is NULL end or not. When the OS BSOD, the pszSrc contain string Boot Bus Extender, but not end with NULL. I use windbg dc command to show the memory, found the verifier is enable, all memorys are inited with 2f cause the problem be reproduced 100% I don't konw why? Memory with BOSD string see attachment. Thanks. NTSTATUS RtlUnicodeStringInitEx( _Out_ PUNICODE_STRING DestinationString, _In_opt_ NTSTRSAFE_PCWSTR pszSrc, _In_ DWORD dwFlags );
Created attachment 1217211 [details] dc memory of the string
(In reply to uljtg from comment #16) > (In reply to Vadim Rozenfeld from comment #15) > > (In reply to uljtg from comment #14) > > > Created attachment 1216884 [details] > > > enable verifier BSOD minidump > > > > Thanks a lot. > > Can you try changing memory dump options from "small memory dump" to "kernel > > memory dump", and upload a fresh crashdump file? (btw, it is always a good > > idea to compress crashdump files before uploading). > > Best regards, > > Vadim. > > Sorry, when i use .dump /ma file to gen dump file windbg give me "Extra > character error in .dump /ma mem.dmp". > > I have try to debug the BSOD use windbg. > I hvae found the problem occured in rltinitunicodeex when test pszSrc is > NULL end or not. > > When the OS BSOD, the pszSrc contain string Boot Bus Extender, but not end > with NULL. > > I use windbg dc command to show the memory, found the verifier is enable, > all memorys are inited with 2f cause the problem be reproduced 100% 2f is just '/' ascii symbol, I don't think we should blame it for that :) > > I don't konw why? > > Memory with BOSD string see attachment. Thanks. > > > > > NTSTATUS RtlUnicodeStringInitEx( > _Out_ PUNICODE_STRING DestinationString, > _In_opt_ NTSTRSAFE_PCWSTR pszSrc, > _In_ DWORD dwFlags > ); Actually it is not exactly like this, but more likely as NTSTATUS RtlInitUnicodeStringEx ( OUT PUNICODE_STRING DestinationString, IN PCWSTR SourceString OPTIONAL ) ( just take a look at the disassembly, it rets 8 bytes) kd> uf RtlInitUnicodeStringEx nt!RtlInitUnicodeStringEx: 83d07bdc 8bff mov edi,edi 83d07bde 55 push ebp 83d07bdf 8bec mov ebp,esp 83d07be1 8b4d08 mov ecx,dword ptr [ebp+8] 83d07be4 33c0 xor eax,eax 83d07be6 668901 mov word ptr [ecx],ax //DestinationString->Length = 0; 83d07be9 66894102 mov word ptr [ecx+2],ax //DestinationString->MaximumLength = 0; 83d07bed 8b450c mov eax,dword ptr [ebp+0Ch] <---Here we fail //DestinationString->Buffer = SourceString; 83d07bf0 894104 mov dword ptr [ecx+4],eax ............ nt!RtlInitUnicodeStringEx+0x4a: 83d07c26 5d pop ebp 83d07c27 c20800 ret 8 I'm not sure yet, but since the problem happens on reboot, could you please check MTRR registers (rdmsr 174 (175,176) after start up and right when the crash happens? Thanks, Vadim.
(In reply to Vadim Rozenfeld from comment #18) > (In reply to uljtg from comment #16) > > (In reply to Vadim Rozenfeld from comment #15) > > > (In reply to uljtg from comment #14) > > > > Created attachment 1216884 [details] > > > > enable verifier BSOD minidump > > > > > > Thanks a lot. > > > Can you try changing memory dump options from "small memory dump" to "kernel > > > memory dump", and upload a fresh crashdump file? (btw, it is always a good > > > idea to compress crashdump files before uploading). > > > Best regards, > > > Vadim. > > > > Sorry, when i use .dump /ma file to gen dump file windbg give me "Extra > > character error in .dump /ma mem.dmp". > > > > I have try to debug the BSOD use windbg. > > I hvae found the problem occured in rltinitunicodeex when test pszSrc is > > NULL end or not. > > > > When the OS BSOD, the pszSrc contain string Boot Bus Extender, but not end > > with NULL. > > > > I use windbg dc command to show the memory, found the verifier is enable, > > all memorys are inited with 2f cause the problem be reproduced 100% > 2f is just '/' ascii symbol, I don't think we should blame it for that :) > > > > I don't konw why? > > > > Memory with BOSD string see attachment. Thanks. > > > > > > > > > > NTSTATUS RtlUnicodeStringInitEx( > > _Out_ PUNICODE_STRING DestinationString, > > _In_opt_ NTSTRSAFE_PCWSTR pszSrc, > > _In_ DWORD dwFlags > > ); > > Actually it is not exactly like this, but more likely as > NTSTATUS > RtlInitUnicodeStringEx ( > OUT PUNICODE_STRING DestinationString, > IN PCWSTR SourceString OPTIONAL > ) > > ( just take a look at the disassembly, it rets 8 bytes) > kd> uf RtlInitUnicodeStringEx > nt!RtlInitUnicodeStringEx: > 83d07bdc 8bff mov edi,edi > 83d07bde 55 push ebp > 83d07bdf 8bec mov ebp,esp > 83d07be1 8b4d08 mov ecx,dword ptr [ebp+8] > 83d07be4 33c0 xor eax,eax > 83d07be6 668901 mov word ptr [ecx],ax > //DestinationString->Length = 0; > 83d07be9 66894102 mov word ptr [ecx+2],ax > //DestinationString->MaximumLength = 0; > 83d07bed 8b450c mov eax,dword ptr [ebp+0Ch] <---Here we fail > //DestinationString->Buffer = SourceString; > 83d07bf0 894104 mov dword ptr [ecx+4],eax > ............ > nt!RtlInitUnicodeStringEx+0x4a: > 83d07c26 5d pop ebp > 83d07c27 c20800 ret 8 > > > I'm not sure yet, but since the problem happens on reboot, could you please > check MTRR registers (rdmsr 174 (175,176) after start up and right when the > crash happens? > > Thanks, > Vadim. Thanks, when crash happens: [MSR174] = 00000000`00000008 [MSR175]= 00000000`80792000 [MSR176]= 00000000`83E920C0 when start up normal: [MSR174] = 00000000`00000008 [MSR175]= 00000000`80790000 [MSR176]= 00000000`83E510C0
(In reply to Vadim Rozenfeld from comment #18) > (In reply to uljtg from comment #16) > > (In reply to Vadim Rozenfeld from comment #15) > > > (In reply to uljtg from comment #14) > > > > Created attachment 1216884 [details] > > > > enable verifier BSOD minidump > > > > > > Thanks a lot. > > > Can you try changing memory dump options from "small memory dump" to "kernel > > > memory dump", and upload a fresh crashdump file? (btw, it is always a good > > > idea to compress crashdump files before uploading). > > > Best regards, > > > Vadim. > > > > Sorry, when i use .dump /ma file to gen dump file windbg give me "Extra > > character error in .dump /ma mem.dmp". > > > > I have try to debug the BSOD use windbg. > > I hvae found the problem occured in rltinitunicodeex when test pszSrc is > > NULL end or not. > > > > When the OS BSOD, the pszSrc contain string Boot Bus Extender, but not end > > with NULL. > > > > I use windbg dc command to show the memory, found the verifier is enable, > > all memorys are inited with 2f cause the problem be reproduced 100% > 2f is just '/' ascii symbol, I don't think we should blame it for that :) > > > > I don't konw why? > > > > Memory with BOSD string see attachment. Thanks. > > > > > > > > > > NTSTATUS RtlUnicodeStringInitEx( > > _Out_ PUNICODE_STRING DestinationString, > > _In_opt_ NTSTRSAFE_PCWSTR pszSrc, > > _In_ DWORD dwFlags > > ); > > Actually it is not exactly like this, but more likely as > NTSTATUS > RtlInitUnicodeStringEx ( > OUT PUNICODE_STRING DestinationString, > IN PCWSTR SourceString OPTIONAL > ) > > ( just take a look at the disassembly, it rets 8 bytes) > kd> uf RtlInitUnicodeStringEx > nt!RtlInitUnicodeStringEx: > 83d07bdc 8bff mov edi,edi > 83d07bde 55 push ebp > 83d07bdf 8bec mov ebp,esp > 83d07be1 8b4d08 mov ecx,dword ptr [ebp+8] > 83d07be4 33c0 xor eax,eax > 83d07be6 668901 mov word ptr [ecx],ax > //DestinationString->Length = 0; > 83d07be9 66894102 mov word ptr [ecx+2],ax > //DestinationString->MaximumLength = 0; > 83d07bed 8b450c mov eax,dword ptr [ebp+0Ch] <---Here we fail > //DestinationString->Buffer = SourceString; > 83d07bf0 894104 mov dword ptr [ecx+4],eax > ............ > nt!RtlInitUnicodeStringEx+0x4a: > 83d07c26 5d pop ebp > 83d07c27 c20800 ret 8 > > > I'm not sure yet, but since the problem happens on reboot, could you please > check MTRR registers (rdmsr 174 (175,176) after start up and right when the > crash happens? > > Thanks, > Vadim. You are right. NTSTATUS RtlInitUnicodeStringEx ( OUT PUNICODE_STRING DestinationString, IN PCWSTR SourceString OPTIONAL ) u nt!rtlinitunicodestringex nt!RtlInitUnicodeStringEx: 83ec2bdc 8bff mov edi,edi 83ec2bde 55 push ebp 83ec2bdf 8bec mov ebp,esp 83ec2be1 8b4d08 mov ecx,dword ptr [ebp+8] 83ec2be4 33c0 xor eax,eax 83ec2be6 668901 mov word ptr [ecx],ax 83ec2be9 66894102 mov word ptr [ecx+2],ax 83ec2bed 8b450c mov eax,dword ptr [ebp+0Ch] kd> uf nt!rtlinitunicodestringex nt!RtlInitUnicodeStringEx: 83ec2bdc 8bff mov edi,edi 83ec2bde 55 push ebp 83ec2bdf 8bec mov ebp,esp 83ec2be1 8b4d08 mov ecx,dword ptr [ebp+8] 83ec2be4 33c0 xor eax,eax 83ec2be6 668901 mov word ptr [ecx],ax 83ec2be9 66894102 mov word ptr [ecx+2],ax 83ec2bed 8b450c mov eax,dword ptr [ebp+0Ch] 83ec2bf0 894104 mov dword ptr [ecx+4],eax 83ec2bf3 85c0 test eax,eax 83ec2bf5 742d je nt!RtlInitUnicodeStringEx+0x48 (83ec2c24) nt!RtlInitUnicodeStringEx+0x1b: 83ec2bf7 56 push esi 83ec2bf8 8d7002 lea esi,[eax+2] nt!RtlInitUnicodeStringEx+0x1f: 83ec2bfb 668b10 mov dx,word ptr [eax] Here cause BSOD 83ec2bfe 40 inc eax 83ec2bff 40 inc eax 83ec2c00 6685d2 test dx,dx 83ec2c03 75f6 jne nt!RtlInitUnicodeStringEx+0x1f (83ec2bfb) nt!RtlInitUnicodeStringEx+0x29: 83ec2c05 2bc6 sub eax,esi 83ec2c07 d1f8 sar eax,1 83ec2c09 5e pop esi 83ec2c0a 3dfe7f0000 cmp eax,7FFEh 83ec2c0f 7607 jbe nt!RtlInitUnicodeStringEx+0x3c (83ec2c18) nt!RtlInitUnicodeStringEx+0x35: 83ec2c11 b8060100c0 mov eax,0C0000106h 83ec2c16 eb0e jmp nt!RtlInitUnicodeStringEx+0x4a (83ec2c26) nt!RtlInitUnicodeStringEx+0x3c: 83ec2c18 03c0 add eax,eax 83ec2c1a 668901 mov word ptr [ecx],ax 83ec2c1d 83c002 add eax,2 83ec2c20 66894102 mov word ptr [ecx+2],ax nt!RtlInitUnicodeStringEx+0x48: 83ec2c24 33c0 xor eax,eax nt!RtlInitUnicodeStringEx+0x4a: 83ec2c26 5d pop ebp 83ec2c27 c20800 ret 8 C code should like: NTSTATUS RtlInitUnicodeStringEx ( OUT PUNICODE_STRING DestinationString, IN PCWSTR SourceString OPTIONAL ) { INT i = 0; DestinationString->Length = 0; DestinationString->MaximumLength = 0; DestinationString->Buffer = SourceString; if ( NULL == SourceString ) { return STATUS_SUCCESS; } // check end while ( SourceString[i] ) // BSOD { i++; } ... return STATUS; }
Here's a recent bug report that looks very similar. Also intermittent BSOD 50 on Win7-32 reboot. The crash happens in RtlInitUnicodeStringEx as well. https://github.com/YanVugenfirer/kvm-guest-drivers-windows/issues/84
Can QE try to reproduce this problem? Then we should start trying to narrow this problem down. Thanks, Vadim.
(In reply to Vadim Rozenfeld from comment #22) > Can QE try to reproduce this problem? Then we should start trying to narrow > this problem down. > > Thanks, > Vadim. Thanks. I am sorry for that i have ignored that beyond the standard spice version, i have add group registry in virt-serial service entry manually, and the REG_SZ value i add is not end with NULL, so cause the problem. I add NULL to the value, and then i can not reproduce the problem again. Thanks.
(In reply to uljtg from comment #23) > (In reply to Vadim Rozenfeld from comment #22) > > Can QE try to reproduce this problem? Then we should start trying to narrow > > this problem down. > > > > Thanks, > > Vadim. > > Thanks. > I am sorry for that i have ignored that beyond the standard spice version, i > have add group registry in virt-serial service entry manually, and the > REG_SZ value i add is not end with NULL, so cause the problem. > > I add NULL to the value, and then i can not reproduce the problem again. > > Thanks. Hi Vadim, Would you please comment? Is it still worth reproducing by QE?
(In reply to Chao Yang from comment #24) > (In reply to uljtg from comment #23) > > (In reply to Vadim Rozenfeld from comment #22) > > > Can QE try to reproduce this problem? Then we should start trying to narrow > > > this problem down. > > > > > > Thanks, > > > Vadim. > > > > Thanks. > > I am sorry for that i have ignored that beyond the standard spice version, i > > have add group registry in virt-serial service entry manually, and the > > REG_SZ value i add is not end with NULL, so cause the problem. > > > > I add NULL to the value, and then i can not reproduce the problem again. > > > > Thanks. > > Hi Vadim, > > Would you please comment? Is it still worth reproducing by QE? Oh, no. If it's gone then let's close the case. Thank you, Vadim.