This site requires JavaScript to be enabled to function correctly, please enable it.
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Summary:
win8 (installed virtio-win-1.6.3 netkvm driver) virtio-net guest BSOD when shutdown
Product:
Red Hat Enterprise Linux 5
Reporter:
CongLi <coli>
Component:
virtio-win Assignee:
Vadim Rozenfeld <vrozenfe>
Status:
CLOSED
WONTFIX
QA Contact:
Virtualization Bugs <virt-bugs>
Severity:
unspecified
Docs Contact:
Priority:
unspecified
Version:
5.10 CC:
bsarathy, dfleytma, hannsj_uhl, juzhang, michen, mkenneth, rhod, shuang, virt-maint, xwei, yvugenfi
Target Milestone:
rc
Target Release:
---
Hardware:
Unspecified
OS:
Unspecified
Whiteboard:
Fixed In Version:
Doc Type:
Bug Fix
Doc Text:
Story Points:
---
Clone Of:
Environment:
Last Closed:
2013-04-10 13:35:12 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 of problem: win8 (installed virtio-win-1.6.3 netkvm driver) virtio-net guest BSOD when shutdown Version-Release number of selected component (if applicable): kernel-2.6.18-348.el5 kvm-83-263.el5 guest: win8-64 enterprise virtio-win1.6.3 How reproducible: 100% Steps to Reproduce: 1.Install a Win8-64 guest 2.Install a virtio-net driver CML: /home/autotest-devel/client/tests/kvm/qemu -S -name vm1 -monitor stdio -serial unix:/tmp/serial-serial1-20130319-192842-287sCXHR,server,nowait -drive file=/home/autotest-devel/client/tests/kvm/images/win8-64-virtio.qcow2,if=ide,media=disk,cache=none,boot=on,snapshot=off,format=qcow2 -net nic,vlan=0,model=virtio,macaddr=9a:27:28:29:2a:2b,id=id21MFFL -net tap,vlan=0 -m 2048 -smp 4,cores=2,threads=1,sockets=2 -M rhel5.6.0 -drive file=/home/qemu/virtio-win/virtio-win-1.6.3.iso,media=cdrom -soundhw ac97 -spice port=4000,ic=on,disable-ticketing -qxl 1 -rtc-td-hack -boot c -usbdevice tablet -cpu qemu64 3.shutdown guest Actual results: guest BSOD with dump ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {ffffffffc0000005, fffff88003f1cc6e, fffff88004ced9b8, fffff88004ced1f0} *** ERROR: Module load completed but symbols could not be loaded for netkvm.sys Probably caused by : netkvm.sys ( netkvm+3c6e ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff88003f1cc6e, The address that the exception occurred at Arg3: fffff88004ced9b8, Exception Record Address Arg4: fffff88004ced1f0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: netkvm+3c6e fffff880`03f1cc6e 488b4108 mov rax,qword ptr [rcx+8] EXCEPTION_RECORD: fffff88004ced9b8 -- (.exr 0xfffff88004ced9b8) ExceptionAddress: fffff88003f1cc6e (netkvm+0x0000000000003c6e) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000008 Attempt to read from address 0000000000000008 CONTEXT: fffff88004ced1f0 -- (.cxr 0xfffff88004ced1f0) rax=fffffa8003309000 rbx=fffffa8003289ab8 rcx=0000000000000000 rdx=0000000000000000 rsi=fffffa8003c2adf0 rdi=fffffa80032897a0 rip=fffff88003f1cc6e rsp=fffff88004cedbf0 rbp=fffffa80018dba20 r8=0000000000000ff0 r9=0000000000000001 r10=0000000000000002 r11=0000000000000000 r12=fffff8026428c770 r13=0000000050085d00 r14=fffffa800196bbd0 r15=fffff8026448bfc0 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 netkvm+0x3c6e: fffff880`03f1cc6e 488b4108 mov rax,qword ptr [rcx+8] ds:002b:00000000`00000008=???????????????? Resetting default scope PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000008 READ_ADDRESS: 0000000000000008 FOLLOWUP_IP: netkvm+3c6e fffff880`03f1cc6e 488b4108 mov rax,qword ptr [rcx+8] BUGCHECK_STR: AV DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff88003f27e3c to fffff88003f1cc6e STACK_TEXT: fffff880`04cedbf0 fffff880`03f27e3c : fffffa80`0307b8a0 fffff880`03aeb660 fffffa80`03e80090 fffff880`03b04f30 : netkvm+0x3c6e fffff880`04cedc20 fffff802`6426e45b : fffffa80`0196bbd0 00000000`00000000 fffff880`0191205c 00000000`0000000a : netkvm+0xee3c fffff880`04cedc50 fffff802`642bb391 : fffff802`6448c080 fffffa80`04054b00 fffff802`6426e3fc 00000000`00000000 : nt!IopProcessWorkItem+0x5f fffff880`04cedcc0 fffff802`6422a521 : 00000000`00000000 00000000`00000080 fffff802`642bb250 fffffa80`04054b00 : nt!ExpWorkerThread+0x142 fffff880`04cedd50 fffff802`64268dd6 : fffff880`02a5c180 fffffa80`04054b00 fffffa80`03602080 fffffa80`01886840 : nt!PspSystemThreadStartup+0x59 fffff880`04cedda0 00000000`00000000 : fffff880`04cee000 fffff880`04ce8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: netkvm+3c6e FOLLOWUP_NAME: MachineOwner MODULE_NAME: netkvm IMAGE_NAME: netkvm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 50b73ae2 STACK_COMMAND: .cxr 0xfffff88004ced1f0 ; kb FAILURE_BUCKET_ID: AV_netkvm+3c6e BUCKET_ID: AV_netkvm+3c6e Followup: MachineOwner --------- Expected results: shutdown successfully Additional info: This problem doesn't exist when reboot. Host cpuinfo: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU 5130 @ 2.00GHz stepping : 11 cpu MHz : 1994.999 cache size : 4096 KB physical id : 3 siblings : 2 core id : 1 cpu cores : 2 apicid : 7 fpu : yes fpu_exception : yes cpuid level : 10 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 syscall nx lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr lahf_lm bogomips : 3990.03 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: