RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 876061 - [whql][wlk][block] windows 2003 can not generate dump file when hitting BSOD
Summary: [whql][wlk][block] windows 2003 can not generate dump file when hitting BSOD
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-13 07:55 UTC by Mike Cao
Modified: 2013-02-21 10:42 UTC (History)
8 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-02-21 10:42:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Build46-2k3-FailTo-generate-dump (8.90 KB, image/png)
2012-11-22 09:59 UTC, dawu 		no flags Details
Build46-dump-saved-Notmyfault (18.47 KB, image/png)
2012-11-23 02:42 UTC, dawu 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0441 0 normal SHIPPED_LIVE virtio-win bug fix and enhancement update 2013-02-20 20:48:13 UTC

Description Mike Cao 2012-11-13 07:55:29 UTC 
Description of problem:
When windows server 2003 hit BSOD ,there is no generate dump file generated ,which cause "crashdump support test "job failed

Version-Release number of selected component (if applicable):
virtio-win-prewhql-43
win2k3 32/64

How reproducible:
100%

Steps to Reproduce:
1.Start VM with virtio-block
CLI:/usr/libexec/qemu-kvm -M rhel6.4.0 -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k3-32.raw,format=raw,if=none,id=drive-virtio0,boot=on,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:11:1a:06:33:26,bus=pci.0,addr=0x4 -boot c -uuid 7768409c-460c-4deb-ba44-7570b2cab3c6 -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/2k3-32-blk-43-new,server,nowait -mon chardev=111a,mode=readline -name win2k3-32-blk-new -vnc :1 -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio
2.enable NMI crashdump or Run crashdump job in WLK1.6
3.(qemu)inject-nmi or waiting for WLK make the guest cause BSOD
  
Actual results:
no dump file generated

Expected results:
generate dump file

Additional info:
Tried on virtio-win-1.5.3.iso ,it can generate dump file successfully .mark this bug as regression
Comment 1 Vadim Rozenfeld 2012-11-22 08:11:36 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.
Comment 2 dawu 2012-11-22 09:58:30 UTC 
(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
Comment 3 dawu 2012-11-22 09:59:29 UTC 
Created attachment 649606 [details]
Build46-2k3-FailTo-generate-dump
Comment 4 Vadim Rozenfeld 2012-11-22 10:10:32 UTC 
that's strange,
could you try crashing the system with notmyfault utility available at
http://download.sysinternals.com/files/NotMyFault.zip ?

Thank you,
Vadim.
Comment 5 dawu 2012-11-23 02:41:00 UTC 
(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
Comment 6 dawu 2012-11-23 02:42:51 UTC 
Created attachment 650170 [details]
Build46-dump-saved-Notmyfault
Comment 7 Vadim Rozenfeld 2012-11-23 08:16:48 UTC 
good,
now can you please check that NMICrashDump is enabled?
http://support.microsoft.com/kb/927069

Thanks,
Vadim.
Comment 8 dawu 2012-11-23 08:31:05 UTC 
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
Comment 9 Vadim Rozenfeld 2012-11-23 09:51:53 UTC 
(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
Comment 10 dawu 2012-11-23 10:08:10 UTC 
(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
Comment 11 Vadim Rozenfeld 2012-11-23 10:29:57 UTC 
(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
Comment 12 dawu 2012-12-07 03:30:44 UTC 
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
Comment 13 Mike Cao 2012-12-18 07:19:01 UTC 
According to comment#12 move status to VERIFIED.
Comment 14 errata-xmlrpc 2013-02-21 10:42:13 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-2013-0441.html
Note You need to log in before you can comment on or make changes to this bug.