Bug 750191

Summary: Wrong LINT1/NMI ACPI and mptable descriptors
Product: Red Hat Enterprise Linux 6 Reporter: Avi Kivity <avi>
Component: seabiosAssignee: Karen Noel <knoel>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: juzhang, knoel, michen, tburke, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: seabios-0.6.1.2-8.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 17:01:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 738565    

Description Avi Kivity 2011-10-31 10:09:25 UTC
Description of problem:

Windows requires an NMI descriptor so it knows the NMI button is connected to LINT1, or it will not enable NMIs.


Version-Release number of selected component (if applicable):
0.6.1.2-7.el6

How reproducible:
Always

Steps to Reproduce:
1. Configure Windows to generate a memory dump on NMI
2. Run under qemu-kvm-0.12.1.2-2.201.el6 or later
3. Generate an NMI
  
Actual results:

Windows does not dump memory


Expected results:

Windows dumps memory


Additional info:

Comment 2 juzhang 2011-10-31 10:24:46 UTC
Just kindly reminder,when we verify this bug,had better associate with Bug 738565 - [FJ6.2 Bug]: Failed to capture kdump due to redundant NMIs

Comment 5 FuXiangChun 2011-11-03 08:46:15 UTC
Reproduced with qemu-kvm-0.12.1.2-2.172.el6.x86_64 and
seabios-0.6.1.2-4.el6.x86_64

Result:
Can not got dump files

Tested with  qemu-kvm-0.12.1.2-2.208.el6.x86_64 and
seabios-0.6.1.2-8.el6.x86_64.
I tried the following windows systems

Results:
Guest name      status

Win2008-64      can get dumps memory files
Win7-64         can get dumps memory files
Winxp           can not get dumps memory files.

Questions:
for now,still winxp failed to get dumps memory files.would you please tell us
why?xp guest handle nmi mechanism or this issue is still not fixed very
well,the more details,the better.thanks

Comment 6 FuXiangChun 2011-11-07 13:42:55 UTC
for winxp guest, i according to below link to change registry. after booting guest, hit Ctrl_R + scrolllock+scrolllock to trigger BSOD and can get memory dump files.  Use inject_nmi could trigger a BSOD but without any memory dumped.
https://redmine.englab.nay.redhat.com/issues/8219

Comment 7 FuXiangChun 2011-11-08 02:32:09 UTC
base above result, this bug is fixed. (In reply to comment #6)
> for winxp guest, i according to below link to change registry. after booting
> guest, hit Ctrl_R + scrolllock+scrolllock to trigger BSOD and can get memory
> dump files.  Use inject_nmi could trigger a BSOD but without any memory dumped.
> https://redmine.englab.nay.redhat.com/issues/8219

(In reply to comment #6)
> for winxp guest, i according to below link to change registry. after booting
> guest, hit Ctrl_R + scrolllock+scrolllock to trigger BSOD and can get memory
> dump files.  Use inject_nmi could trigger a BSOD but without any memory dumped.
> https://redmine.englab.nay.redhat.com/issues/8219

thanks for Avi vadim's help, after I used below link and email provide method to re-modify registry of winxp/win2003, they can get dumps memory files when send NMI怀from host to guest.

http://support.microsoft.com/kb/927069

final testing result:

   Guest name      status

  Win2008-64      can get dumps memory files
  Win7-64         can get dumps memory files
  Winxp           can get dumps memory files.
  win2003-64      can get dumps memory files.

base above testing result, this bug is fixed in qemu-kvm-0.12.1.2-2.208.el6.x86_64 and
seabios-0.6.1.2-8.el6.x86_64.

Comment 9 errata-xmlrpc 2011-12-06 17:01:30 UTC
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.

http://rhn.redhat.com/errata/RHBA-2011-1680.html