Bug 858698
| Summary: | when run Win2008r2.64.migrate.with_reboot.tcp guest BSOD | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | yunpingzheng <yunzheng> | ||||
| Component: | kvm | Assignee: | Yvugenfi <yvugenfi> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.9 | CC: | chayang, juzhang, michen, mkenneth, rhod, shuang, virt-maint, 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-03-28 17:41:22 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
yunpingzheng
2012-09-19 12:51:36 UTC
Created attachment 614357 [details]
bsod snapshot
1.now this bug appear only once. i have tried to reproduce it, but i can not reproduce it. 2.host info: rhel 5.9.64 : kernel: 2.6.18-339 qemu-kvm: kvm-83-259.el5 cpuinfo processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz stepping : 7 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 6784.36 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual Yan, Do you have any insights? Postponed to RHEL5.10 for now. Reproduced only once. Too late for 5.9. Hi Ronen, There is probably some memory corruption - Bug Check 0x109 - according to MS: CRITICAL_STRUCTURE_CORRUPTION: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557228(v=vs.85).aspx The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109. This indicates that the kernel has detected critical kernel code or data corruption. Cause There are generally three different causes for this bug check: * A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems. * A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time. * A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed. ---------------------------------------- We need dump file to get more info or to try to understand why region of guest physical memory was corrupted. Best regards, Yan. Assigned to Yan for the Windows-side analysis. Will be dealt with when we start working on RHEL5.10 yunpingzheng, Please provide a dump file. Thanks. Ronen I am trying to reproduce this bug now, if i can get the dump file, i will provide it. (this test was run in virtlab. the host that run this case have been reinstalled,when i analysing.) |