Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Please provide the version of virtio-win drivers installed.
From comment 0:
> Version-Release number of selected component (if applicable):
>
> qemu-kvm-1.5.3-86.el7_1.8.x86_64
>kernel-3.10.0-229.20.1.el7.x86_64
>
> ｉtried on kernel kernel-3.10.0-229 ,and didn't hit it .
>
> will try on rhel7.2 and then update the comment.
Can you clarify the above? You found the problem with the 229 kernel, but then found it did not reproduce with the same kernel? This is RHEL 7.2, so will you try RHEL 7.1?
Did you get this crash more than once? Was it a similar crash footprint each time? Thanks.
(In reply to Karen Noel from comment #4)
> Please provide the version of virtio-win drivers installed.
>
> From comment 0:
>
> > Version-Release number of selected component (if applicable):
> >
> > qemu-kvm-1.5.3-86.el7_1.8.x86_64
> >kernel-3.10.0-229.20.1.el7.x86_64
> >
> > ｉtried on kernel kernel-3.10.0-229 ,and didn't hit it .
> >
> > will try on rhel7.2 and then update the comment.
>
> Can you clarify the above? You found the problem with the 229 kernel, but
> then found it did not reproduce with the same kernel? This is RHEL 7.2, so
> will you try RHEL 7.1?
>
> Did you get this crash more than once? Was it a similar crash footprint each
> time? Thanks.
virtio_win_driver:
virtio-win-1.8.0-4.iso
got this problems on a z stream kernel ,so i use the formal one to retry..i got this problem 2 times,thanks.
Comment 7Yvugenfi@redhat.com
2016-01-12 16:52:12 UTC
*** This bug has been marked as a duplicate of bug 1241986 ***
Description of problem: Win7 64bit guest got BSOD Version-Release number of selected component (if applicable): qemu-kvm-1.5.3-86.el7_1.8.x86_64 kernel-3.10.0-229.20.1.el7.x86_64 ｉtried on kernel kernel-3.10.0-229 ,and didn't hit it . will try on rhel7.2 and then update the comment. How reproducible: repeat to reboot the guest with autotest script. Steps to Reproduce: 1. boot the guest with cmdline: /usr/libexec/qemu-kvm \ -name 'virt-tests-vm1' \ -sandbox off \ -machine pc \ -nodefaults \ -vga std \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20151021-144219-EBYaVDZi,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=qmp_id_catch_monitor,path=/tmp/monitor-catch_monitor-20151021-144219-EBYaVDZi,server,nowait \ -mon chardev=qmp_id_catch_monitor,mode=control \ -device pvpanic,ioport=0x505,id=idEy4Hb4 \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20151021-144219-EBYaVDZi,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -chardev socket,id=seabioslog_id_20151021-144219-EBYaVDZi,path=/tmp/seabios-20151021-144219-EBYaVDZi,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20151021-144219-EBYaVDZi,iobase=0x402 \ -device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \ -device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=1d.0,firstport=0,bus=pci.0 \ -device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=1d.2,firstport=2,bus=pci.0 \ -device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=1d.4,firstport=4,bus=pci.0 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file=/home/autotest/client/tests/virt/shared/data/images/win7-64-sp1-virtio.qcow2 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=03 \ -device virtio-net-pci,mac=9a:f3:f4:f5:f6:f7,id=id1Xs3Yn,vectors=4,netdev=idLCYBlF,bus=pci.0,addr=04 \ -netdev tap,id=idLCYBlF,vhost=on \ -m 16384 \ -smp 16,maxcpus=16,cores=8,threads=1,sockets=2 \ -cpu 'Westmere',hv_relaxed,+kvm_pv_unhalt,hv_spinlocks=0x1fff,hv_vapic,hv_time \ -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/home/autotest/client/tests/virt/shared/data/isos/windows/winutils.iso \ -device ide-cd,id=cd1,drive=drive_cd1,bootindex=1,bus=ide.0,unit=0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm \ -monitor stdio \ 2. reboot for several times. Actual results: win7 got bsod Expected results: win7 reboot with no error. Additional info: host info: cpu: processor : 23 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz stepping : 2 microcode : 0x15 cpu MHz : 2660.000 cache size : 12288 KB physical id : 1 siblings : 12 core id : 10 cpu cores : 6 apicid : 53 initial apicid : 53 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm arat epb dtherm tpr_shadow vnmi flexpriority ept vpid 1.memory.dmp analysis: 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000017800111, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800026a07d5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000017800111 CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+1e3 fffff800`026a07d5 488b00 mov rax,qword ptr [rax] DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.16520 (debuggers(dbg).140127-0329) amd64fre DPC_STACK_BASE: FFFFF80003D95FB0 TRAP_FRAME: fffff80003d8f8a0 -- (.trap 0xfffff80003d8f8a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000017800111 rbx=0000000000000000 rcx=fffff88003f969d8 rdx=fffffa800e1561a0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800026a07d5 rsp=fffff80003d8fa30 rbp=0000000000000002 r8=0000000000000100 r9=0000000000000000 r10=0000000017800111 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po cy nt!KeSetEvent+0x1e3: fffff800`026a07d5 488b00 mov rax,qword ptr [rax] ds:00000000`17800111=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000269bbe9 to fffff8000269c640 STACK_TEXT: fffff800`03d8f758 fffff800`0269bbe9 : 00000000`0000000a 00000000`17800111 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`03d8f760 fffff800`0269a860 : 00000000`00000001 00000000`000000fe fffffa80`0e3c74d0 fffff880`03f969d0 : nt!KiBugCheckDispatch+0x69 fffff800`03d8f8a0 fffff800`026a07d5 : fffff880`03f969d0 00000000`00000002 00000000`00000000 fffff800`0280ee80 : nt!KiPageFault+0x260 fffff800`03d8fa30 fffff880`01691407 : fffff880`00000000 fffffa80`00000000 fffffa80`0e156100 fffffa80`0e3c7200 : nt!KeSetEvent+0x1e3 fffff800`03d8faa0 fffff880`04a3e870 : fffffa80`0e3c7200 00000000`00000000 00000000`00000000 fffffa80`0e3d5870 : ndis!NdisMPauseComplete+0x67 fffff800`03d8fad0 fffff880`04a3b6d9 : fffffa80`0e3d5968 fffffa80`0e3d58b0 fffffa80`0e3d5870 fffff880`04a37acb : netkvm+0xc870 fffff800`03d8fb00 fffff880`04a351ed : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : netkvm+0x96d9 fffff800`03d8fbb0 fffff880`04a40750 : fffffa80`0e3c7200 00000000`00000000 00000000`00000000 00000000`00000000 : netkvm+0x31ed fffff800`03d8fbe0 fffff880`01603b51 : 00000000`00000315 fffff800`02811528 fffff800`0280ee80 01d10c51`6c92e7ca : netkvm+0xe750 fffff800`03d8fc40 fffff800`026a7b1c : fffffa80`0e0bf518 fffff800`00000000 00000000`00000000 fffff800`0280ee80 : ndis!ndisInterruptDpc+0x151 fffff800`03d8fcd0 fffff800`0269436a : fffff800`0280ee80 fffff800`0281ccc0 00000000`00000000 fffff880`01603a00 : nt!KiRetireDpcList+0x1bc fffff800`03d8fd80 00000000`00000000 : fffff800`03d90000 fffff800`03d8a000 fffff800`03d8fd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: netkvm+c870 fffff880`04a3e870 4883c420 add rsp,20h SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: netkvm+c870 FOLLOWUP_NAME: MachineOwner MODULE_NAME: netkvm IMAGE_NAME: netkvm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5600f3af FAILURE_BUCKET_ID: X64_0xA_netkvm+c870 BUCKET_ID: X64_0xA_netkvm+c870 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xa_netkvm+c870 FAILURE_ID_HASH: {a0fd52a1-6318-6df3-8a75-2e294a5758ca} Followup: MachineOwner ---------