Bug 876061
| Summary: | [whql][wlk][block] windows 2003 can not generate dump file when hitting BSOD | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Cao <bcao> | ||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 6.4 | CC: | acathrow, bcao, bsarathy, dawu, dyasny, mdeng, michen, rhod | ||||||
| Target Milestone: | rc | Keywords: | Regression, TestBlocker | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||||
| Doc Text: |
In Red Hat Enterprise Linux 6.4 Beta, no dump file is generated when a Stop Error (or Blue Screen of Death) occurs on a Microsoft Windows Server 2003 guest.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-02-21 10:42:13 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
Mike Cao
2012-11-13 07:55:29 UTC
Hi Dawn, Could you please try drivers from build 46 available at http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/46/win/virtio-win-prewhql-0.1.zip ? Thank you, Vadim. (In reply to comment #1) > Hi Dawn, > > Could you please try drivers from build 46 available at > http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/46/ > win/virtio-win-prewhql-0.1.zip ? > > Thank you, > Vadim. Verified this bug on build 46 with manually testing (through NMI), steps is the same with comment #0 Actually Results: Dump still fail to be generated after hitting BSOD.Please refer to the attachment "Build46-2k3-FailTo-generate-dump.png" for details. Based on above, this issue haven't fixed yet, re-assign this bug. Best Regards, Dawn Created attachment 649606 [details]
Build46-2k3-FailTo-generate-dump
that's strange, could you try crashing the system with notmyfault utility available at http://download.sysinternals.com/files/NotMyFault.zip ? Thank you, Vadim. (In reply to comment #4) > that's strange, > could you try crashing the system with notmyfault utility available at > http://download.sysinternals.com/files/NotMyFault.zip ? > > Thank you, > Vadim. Hi Vadim, Tried with notmyfault utility, dump can generate successfully, please refer to the attachment "Build46-dump-saved-Notmyfault.png". Thanks! Best Regards, Dawn Created attachment 650170 [details]
Build46-dump-saved-Notmyfault
good, now can you please check that NMICrashDump is enabled? http://support.microsoft.com/kb/927069 Thanks, Vadim. Hi Vadim, I set the NMICrashDump as 1, so it had been enabled when I verified this issue by NMI in comment 2. I'm not sure what kind of the method to trigger crash when doing whql, if it's not trigger by NMI, I think I can have a try for whql with build 46 instead of manually verification by NMI. Best Regards, Dawn (In reply to comment #8) > Hi Vadim, > > I set the NMICrashDump as 1, so it had been enabled when I verified this > issue by NMI in comment 2. > > I'm not sure what kind of the method to trigger crash when doing whql, if It is not NMI, Winwows should crash with MANUALLY_INITIATED_CRASH bugcheck code Cheers, Vadim. > it's not trigger by NMI, I think I can have a try for whql with build 46 > instead of manually verification by NMI. > > Best Regards, > Dawn (In reply to comment #7) > good, > now can you please check that NMICrashDump is enabled? > http://support.microsoft.com/kb/927069 > > Thanks, > Vadim. Hi Vadim, Sorry for my mistake, I create NMICrashDump under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control instead of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl. Tried with the correct setting, now dump can generate successfully with build 46,and we still will keep this bug open till related job pass for whql. Thanks for your efforts! Best Regards, Dawn (In reply to comment #10) > (In reply to comment #7) > > good, > > now can you please check that NMICrashDump is enabled? > > http://support.microsoft.com/kb/927069 > > > > Thanks, > > Vadim. > > Hi Vadim, > Sorry for my mistake, I create NMICrashDump under > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control instead of > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl. > No problem, btw, crashdump test triggers the crash dump generation almost the same way as keyboard does http://msdn.microsoft.com/en-us/library/windows/hardware/ff545499%28v=vs.85%29.aspx Vadim. > Tried with the correct setting, now dump can generate successfully with > build 46,and we still will keep this bug open till related job pass for whql. > > Thanks for your efforts! > Best Regards, > Dawn Reproduce this bug on virtio-win-prewhql-43, verified this bug on virtio-win-prewhql-48 with the same steps in comment #0, also verified this bug on virtio-win-prewhql-48 for related whql job "Crashdump Support Test(LOGO)": Actually Results: on version virtio-win-prewhql-43, can reproduce this bug. on version virtio-win-prewhql-48, dump can generate successfully and pass whql related job "Crashdump Support Test(LOGO)". Based on above this issue has been fixed. Thanks! Best Regards, Dawn According to comment#12 move status to VERIFIED. 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-2013-0441.html |