[Bug]: Windows 11 25H2 host — Intermittent VM freezes using NEM/WHPX with VBS enabled (Ryzen 9950X3D)

未关闭
#972 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c

调研方向

Start by reading the attached sanitized log and tracing the NEM/WHPX initialization and guest heartbeat paths mentioned in the report. The issue provides no source files or failing test, and the freeze is intermittent, so first identify a reproducible diagnostic path; done means the guest remains responsive with Windows virtualization-based security enabled or the cause and supported workaround are documented.

由索引模型根据 Issue 内容生成。

描述

bug
Version

7.2.20

Host OS Type

Windows

Host OS name + version

Windows 11 Pro 10.0.26200 Build 26200

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Both Windows and Linux VMs

Component

GUI

What happened?

Environment
VirtualBox: 7.2.20 r175154
Host OS: Windows 11, build 26200.9711
Host architecture: x86-64
Processor: AMD Ryzen 9 9950X3D
Host RAM: 32 GB
Guest OS: Windows 11 64-bit
Guest RAM: 6 GB
Guest processors: 8 vCPUs
Graphics: VMSVGA, 3D acceleration disabled
Windows Core Isolation / Memory Integrity: Enabled
Component: VMM / NEM / Windows Hypervisor Platform

Description

I am experiencing recurring, intermittent freezes of VirtualBox virtual machines on my Windows 11 workstation. Includes both Windows and Linux OS machines.

The issue has persisted across multiple VirtualBox updates over several months. I previously used VirtualBox on an Intel-based Windows 10 computer without experiencing this behavior.

The Windows 11 host has its normal virtualization-based security features enabled. VirtualBox falls back to the Windows Hypervisor Platform (NEM/WHPX) rather than accessing AMD-V directly.

The attached log explicitly reports that NEM's reduced-performance execution mode is active, followed by guest heartbeat failures.

Relevant log entries

HM: HMR3Init: Attempting fall back to NEM:
AMD-V is not available

NEM: WHvCapabilityCodeHypervisorPresent is TRUE

[VirtualBox_Win11_25H2_Sanitized_Log.txt](https://github.com/user-attachments/files/34638673/VirtualBox_Win11_25H2_Sanitized_Log.txt)

NEM: NEMR3Init: Snail execution mode is active!

The guest subsequently becomes unresponsive:

00:04:33 Guest seems to be unresponsive.
Last heartbeat received 4 seconds ago

00:04:54 GuestHeartBeat: Guest is alive

00:04:59 Guest seems to be unresponsive.
Last heartbeat received 5 seconds ago
How can we reproduce this?

Run an existing Windows 11 guest in VirtualBox on the described Windows 11 host.
Leave the host's default security features, including Memory Integrity, enabled.
Start the VM while VirtualBox is using the NEM/WHPX execution backend.
Use the guest normally and observe intermittent freezes and heartbeat failures.
The issue is intermittent rather than reliably triggered by a particular application.

VirtualBox reports reduced-performance NEM execution mode, and the guest experiences intermittent periods of unresponsiveness.

Troubleshooting performed
Tested multiple VirtualBox versions over several months.
Confirmed the host hypervisor is active.
Confirmed VirtualBox is using NEM/WHPX.
Captured guest heartbeat failures in the VirtualBox log.

I would prefer to retain Windows 11's built-in security protections, including Memory Integrity and virtualization-based security.

Could the VirtualBox development team investigate whether this is a known Windows 11 NEM/WHPX compatibility or scheduling issue?

Is there a planned correction, development build, or supported workaround that allows VirtualBox to operate reliably while Windows virtualization-based security remains enabled?

Please advise whether additional diagnostic traces would help identify the cause.

Attachment: VirtualBox_Win11_25H2_Sanitized_Log.txt

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
主要语言
C
星标
1.4k
派生
219
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

VirtualBox/virtualbox 的其他 Issue

查看 VirtualBox/virtualbox 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。