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

オープン
#972 コメント 1 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 6 日以内に返信

まだ誰も着手していません。

評価

難易度
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 はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

VirtualBox/virtualbox のほかの issue

VirtualBox/virtualbox の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。