Bug 1238569

Summary: [RHEL7.2] win7-64 guest failed to reboot with BSOD "Error Code: 0x0000001E"
Product: Red Hat Enterprise Linux 7 Reporter: Yang Meng <meyang>
Component: qemu-kvmAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED CURRENTRELEASE QA Contact: Yiqian Wei <yiwei>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: ailan, chayang, coli, ghammer, hhuang, huding, jinzhao, juzhang, knoel, meyang, michen, mkenneth, qzhang, rbalakri, rpacheco, shuang, virt-bugs, virt-maint, vrozenfe, xiagao, xuhan, yiwei
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1204453
: 1260341 (view as bug list) Environment:
Last Closed: 2017-11-13 09:45:23 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:
Bug Depends On: 1204453    
Bug Blocks: 1260341, 1401400    

Comment 1 Yang Meng 2015-07-02 08:05:04 UTC
the memory.dmp is in:

http://fileshare.englab.nay.redhat.com/pub/section2/images_backup/rhel7/bug1238569/


and the dmp analysis:

16.12: kd:x86> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1E

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16520 (debuggers(dbg).140127-0329) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

BUCKET_ID:  INVALID_KERNEL_CONTEXT

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:invalid_kernel_context

FAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}

Followup: MachineOwner
---------

Comment 3 Karen Noel 2015-07-06 10:53:33 UTC
Yang, Did you confirm that this bug still happens on RHEL 7.2 host? Are you using qemu-kvm-rhev?

Vadim, Can you provide more dump analysis so give us an idea where the problem might be?

Comment 5 Yang Meng 2015-07-22 07:47:35 UTC
(In reply to Karen Noel from comment #3)
> Yang, Did you confirm that this bug still happens on RHEL 7.2 host? Are you
> using qemu-kvm-rhev?
> 
> Vadim, Can you provide more dump analysis so give us an idea where the
> problem might be?

hi, when i clone this bug ,i am using:
kernel: kernel-3.10.0-276.el7.x86_64
qemu: qemu-kvm-1.5.3-94.el7.x86_64

i don't know if it still hapeens, i will try in the latest build

Comment 6 Yang Meng 2015-07-28 03:30:01 UTC

1.qemu-kvm

kernel: kernel-3.10.0-295.el7.x86_64.rpm
qemu: qemu-kvm-1.5.3-97.el7.x86_64.rpm
guest: Win7.x86_64.sp1

cpuinfo:

processor	: 23 
vendor_id	: AuthenticAMD 
cpu family	: 21 
model	: 1 
model name	: AMD Opteron(TM) Processor 6234 
stepping	: 2 
microcode	: 0x6000626 
cpu MHz	: 2400.106 
cache size	: 2048 KB 
physical id	: 1 
siblings	: 12 
core id	: 5 
cpu cores	: 6 
apicid	: 75 
initial apicid	: 43 
fpu	: yes 
fpu_exception	: yes 
cpuid level	: 13 
wp	: yes 
flags	: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold 
bogomips	: 4799.72 
TLB size	: 1536 4K pages 
clflush size	: 64 
cache_alignment	: 64 
address sizes	: 48 bits physical, 48 bits virtual 
power management: ts ttp tm 100mhzsteps hwpstate cpb 


steps:
1)reboot the guest for 75 times in amd host and didn't hit the blackscreen


2.qemu-kvm-rhev

kernel:kernel-3.10.0-292.el7.x86_64.rpm
qemu: qemu-kvm-rhev-2.3.0-9.el7.x86_64.rpm
guest: Win7.x86_64.sp1

cpuinfo:

processor	: 15 
vendor_id	: AuthenticAMD 
cpu family	: 16 
model	: 9 
model name	: AMD Opteron(tm) Processor 6128 
stepping	: 1 
microcode	: 0x10000d9 
cpu MHz	: 1999.968 
cache size	: 512 KB 
physical id	: 1 
siblings	: 8 
core id	: 3 
cpu cores	: 8 
apicid	: 39 
initial apicid	: 23 
fpu	: yes 
fpu_exception	: yes 
cpuid level	: 5 
wp	: yes 
flags	: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save pausefilter 
bogomips	: 4000.06 
TLB size	: 1024 4K pages 
clflush size	: 64 
cache_alignment	: 64 
address sizes	: 48 bits physical, 48 bits virtual 
power management: ts ttp tm stc 100mhzsteps hwpstate 

steps:
1)i tried to reboot the guest for 75 times, and don't hit the blackscreen

Comment 10 Amnon Ilan 2015-09-09 12:48:45 UTC
Based on comment #9 , closing as duplicate

*** This bug has been marked as a duplicate of bug 1260341 ***

Comment 11 Suqin Huang 2015-09-11 08:26:23 UTC
Re-open this bug becasue bug 1260341 is for qemu-kvm-rhev

Comment 15 Vadim Rozenfeld 2017-11-09 07:46:41 UTC
is it still reproducible on 7.5?

Thanks,
Vadim.

Comment 16 Yiqian Wei 2017-11-13 08:25:01 UTC
(In reply to Vadim Rozenfeld from comment #15)
> is it still reproducible on 7.5?

Hi Vadim,

I had tested 100 times by auto and manually on the latest qemu package and didn't reproduce this bug.

Host version:
qemu-kvm-1.5.3-148.el7.x86_64
kernl-3.10.0-781.el7.x86_64
virtio-win-1.9.3-1.el7.noarch
Guest:win7_64

Test steps:
1.boot up win7 64bit guest
2.reboot guest for 100 times

Test results:
reboot the guest for 100 times and didn't hit the blackscreen.


Additional info:
1)manually cli:
/usr/libexec/qemu-kvm \
    -name 'vm-1' \
    -M rhel6.6.0  \
    -nodefaults  \
    -vga qxl \
    -device AC97,bus=pci.0,addr=03  \
    -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1,server,nowait \
    -mon chardev=qmp_id_qmpmonitor1,mode=control  \
    -chardev socket,id=qmp_id_catch_monitor,path=/tmp/monitor-catch_monitor-1,server,nowait \
    -mon chardev=qmp_id_catch_monitor,mode=control  \
    -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0,server,nowait \
    -device isa-serial,chardev=serial_id_serial0  \
    -chardev socket,id=seabioslog_id,path=/tmp/seabios-2,server,nowait \
    -device isa-debugcon,chardev=seabioslog_id,iobase=0x402 \
    -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=04 \
    -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/home/kvm_autotest_root/images/win7-64-sp1-virtio.qcow2 \
    -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=05 \
    -device virtio-net-pci,mac=9a:a5:a6:a7:a8:a9,id=net0,vectors=4,netdev=hostnet0,bus=pci.0,addr=06  \
    -netdev tap,id=hostnet0,vhost=on   \
    -m 16384  \
    -smp 8,maxcpus=8,cores=4,threads=1,sockets=2  \
    -cpu 'Opteron_G4',hv_relaxed \
    -drive id=drive_cd1,if=none,snapshot=off,media=cdrom,file=/usr/share/virtio-win/virtio-win-1.9.3.iso \
    -device ide-drive,id=cd1,drive=drive_cd1,bootindex=1,bus=ide.0,unit=0 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -spice port=5930,disable-ticketing  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot menu=on \
    -enable-kvm  \
    -monitor stdio \

2)host cpuinfo:
processor	: 15
vendor_id	: AuthenticAMD
cpu family	: 21
model		: 2
model name	: AMD Opteron(tm) Processor 6320
stepping	: 0
microcode	: 0x600084f
cpu MHz		: 2800.000
cache size	: 2048 KB
physical id	: 1
siblings	: 8
core id		: 3
cpu cores	: 4
apicid		: 71
initial apicid	: 39
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
bogomips	: 5585.37
TLB size	: 1536 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro

Comment 17 Vadim Rozenfeld 2017-11-13 08:29:30 UTC
(In reply to Yiqian Wei from comment #16)
> (In reply to Vadim Rozenfeld from comment #15)
> > is it still reproducible on 7.5?
> 
> Hi Vadim,
> 
> I had tested 100 times by auto and manually on the latest qemu package and
> didn't reproduce this bug.
> 

Thanks a lot for your feedback.
If you don;t mind, I'm going to close this issue.

Best regards,
Vadim.

Comment 18 Yiqian Wei 2017-11-13 08:43:07 UTC
(In reply to Vadim Rozenfeld from comment #17)
> (In reply to Yiqian Wei from comment #16)
> > (In reply to Vadim Rozenfeld from comment #15)
> > > is it still reproducible on 7.5?
> > 
> > Hi Vadim,
> > 
> > I had tested 100 times by auto and manually on the latest qemu package and
> > didn't reproduce this bug.
> > 
> 
> Thanks a lot for your feedback.
> If you don;t mind, I'm going to close this issue.

Of course not,can close the bz.

Please re-open it if hit the issue again。