Skip to content

WaaG BSOD occur after Windows Update #8755

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yichongt opened this issue Jan 9, 2025 · 0 comments
Open

WaaG BSOD occur after Windows Update #8755

yichongt opened this issue Jan 9, 2025 · 0 comments
Labels
status: new The issue status: new for creation

Comments

@yichongt
Copy link
Contributor

yichongt commented Jan 9, 2025

Describe the bug
WaaG BSOD occur after Windows security update and reboot. Error code is 0xc0000225 without extra information. If there is recovery partition in WaaG image, it will enter recovery environment.

Platform
Issue is reproduced on RPL-P, ADL and TGL.

Codebase
ACRN master and release_3.3

Scenario
Industry

To Reproduce
Steps to reproduce the behavior:

  1. Launch WaaG and start Windows Update
  2. Restart and apply update
  3. BSOD occur
@yichongt yichongt added the status: new The issue status: new for creation label Jan 9, 2025
yichongt added a commit to yichongt/acrn-hypervisor that referenced this issue Feb 21, 2025
In current code process, hyperv data in struct vm_arch is never cleared
during VM shutdown and is retained to next VM launch. As the enabled
bit of hypercall_page msr is not clear, hypercall page might cause fatal
error such as Windows VM BSOD during VM restart and memory
remapping. Hyperv page destory function can ensure hyperv page is
destory during each VM shutdown so hyperv related config such as
hypercall page is established correctly during each VM launch.

Tracked-On: projectacrn#8755
Signed-off-by: Yichong Tang <[email protected]>
acrnsi-robot pushed a commit that referenced this issue Mar 10, 2025
In current code process, hyperv data in struct vm_arch is never cleared
during VM shutdown and is retained to next VM launch. As the enabled
bit of hypercall_page msr is not clear, hypercall page might cause fatal
error such as Windows VM BSOD during VM restart and memory
remapping. Hyperv page destory function can ensure hyperv page is
destory during each VM shutdown so hyperv related config such as
hypercall page is established correctly during each VM launch.

Tracked-On: #8755
Signed-off-by: Yichong Tang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: new The issue status: new for creation
Projects
None yet
Development

No branches or pull requests

1 participant