Hide Forgot
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:
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
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
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
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.
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