-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.4
-
None
-
No
-
Important
-
rhel-virt-core
-
ssg_virtualization
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
Attempting to collect crash dump within a Windows guest VM
What is the impact of this issue to you?
Unable to properly collect crash dump information, as the VM hangs instead of completing the BSOD process
Please provide the package NVR for which the bug is seen:
Virtio-win
How reproducible is this bug?:
100%
Steps to reproduce
- Configure crash dumps inside Windows VM
- Use "NotMyFault" to test a crash dump within the VM and collect system dump
- VM will start the crash process but will not enter a BSOD
Expected results
VM should BSOD and crash dump data should be collected
Actual results
Crash dump data is collected, however, a BSOD is not seen. This is needed so that in the event of a crash, the CU can provide the BSOD information to Microsoft for analysis.
Note:
This issue has been determined that the blue screen is displayed when Display Driver is used as the default Microsoft driver, however, when the Red Hat VirtIO GPU DOD controller driver is used the freeze of the screen occurs.
In short, when using a display type such as "VGA" the VM will properly display the BSOD. When using a display type "virtio" the VM console will hang - and not provide a BSOD.
- relates to
-
RHEL-113406 BSOD screen doesn't show up with VirtIO VGA and dump fails
-
- Planning
-