Bug 1261797
Summary: | contents of MSR_TSC_AUX are not migrated | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaoqing Wei <xwei> | ||||||
Component: | qemu-kvm-rhev | Assignee: | Amit Shah <amit.shah> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
Severity: | high | Docs Contact: | Jiri Herrmann <jherrman> | ||||||
Priority: | medium | ||||||||
Version: | 7.2 | CC: | ailan, amit.shah, areis, chayang, dgilbert, hhuang, jen, juzhang, knoel, lijin, pbonzini, virt-maint, zhguo | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Windows | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | qemu-kvm-rhev-2.5.0-1.el7 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 1265427 1265428 (view as bug list) | Environment: | |||||||
Last Closed: | 2016-11-07 20:37:33 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: | |||||||||
Bug Blocks: | 1265427, 1265428, 1287070, 1288337, 1305606, 1313485 | ||||||||
Attachments: |
|
Description
Xiaoqing Wei
2015-09-10 07:44:38 UTC
Created attachment 1072052 [details]
bsod minidump
Created attachment 1072053 [details]
windbg output
1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a01f58a88e3638, Reserved Arg2: b3b72bdefb0f076f, Reserved Arg3: 00000001c0000103, Failure type dependent information Arg4: 0000000000000007, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification 8 : Object type 9 : A processor IVT a : Modification of a system service function b : A generic session data region c : Modification of a session function or .pdata d : Modification of an import table e : Modification of a session import table f : Ps Win32 callout modification 10 : Debug switch routine modification 11 : IRP allocator modification 12 : Driver call dispatcher modification 13 : IRP completion dispatcher modification 14 : IRP deallocator modification 15 : A processor control register 16 : Critical floating point control register modification 17 : Local APIC modification 18 : Kernel notification callout modification 19 : Loaded module list modification 1a : Type 3 process list corruption 1b : Type 4 process list corruption 1c : Driver object corruption 1d : Executive callback object modification 1e : Modification of module padding 1f : Modification of a protected process 20 : A generic data region 21 : A page hash mismatch 22 : A session page hash mismatch 23 : Load config directory modification 24 : Inverted function table modification 25 : Session configuration modification 102 : Modification of win32k.sys > CRITICAL_STRUCTURE_CORRUPTION (109) > Arg4: 0000000000000007, Type of corrupted region, can be > 7 : Critical MSR modification Hmm, that doesn't look usb-storage related at all. Probably formating usb-storage just creates some load which increases the chance to hit this. Cc'ing paolo. The first three arguments are "reserved", but they strongly look like old value, new value (or a hash of it) and MSR index. In fact the third is definitely the MSR index and it is MSR_TSC_AUX. Do you remember if the crash happened before migration finished, or afterwards? It looks like QEMU is not saving and restoring MSR_TSC_AUX. (In reply to Paolo Bonzini from comment #7) > The first three arguments are "reserved", but they strongly look like old > value, new value (or a hash of it) and MSR index. In fact the third is > definitely the MSR index and it is MSR_TSC_AUX. > > Do you remember if the crash happened before migration finished, or > afterwards? not sure :( I was started the formatting in guest and type 'migrate -d ' in qemu monitor and leave a while, when I back, the cmd terminal in guest is gone, so I check if it has a dump and it's there. then I tried to reproduce as C#1, but failed, with 4 attempts with exactly identical steps, on origin host. no luck . Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2673.html This was upstream commit c9b8f6b6210847b4381c5b2ee172b1c7eb9985d6. |