Version
trunk/main
Host OS Type
Linux
Host OS name + version
NixOS 25.11-pre
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
No response
Component
Unspecified
What happened?
In this line
|
|| !(pVmcs->u32ProcCtls & VMX_EXIT_CTLS_SAVE_PREEMPT_TIMER)) |
the check applies to the
procCtls, however, the
SAVE_PREEMPT_TIMER setting is an
exitCtls setting.
This thus allows nested vms to start with invalid configurations, while killing valid guests.
How can we reproduce this?
Start a nested vm with VMX preemption disabled and nmi-window exiting( The corresponding bit in procCtls) enabled. This fails with error kVmxVDiag_Vmentry_SavePreemptTimer even though it is a valid configuration.
Did you upload all of your necessary log files, screenshots, etc.?
Version
trunk/main
Host OS Type
Linux
Host OS name + version
NixOS 25.11-pre
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
No response
Component
Unspecified
What happened?
In this line
virtualbox/src/VBox/VMM/VMMAll/target-x86/IEMAllCImplVmxInstr-x86.cpp
Line 6677 in 793b64c
procCtls, however, theSAVE_PREEMPT_TIMERsetting is anexitCtlssetting.This thus allows nested vms to start with invalid configurations, while killing valid guests.
How can we reproduce this?
Start a nested vm with VMX preemption disabled and
nmi-window exiting( The corresponding bit inprocCtls) enabled. This fails with errorkVmxVDiag_Vmentry_SavePreemptTimereven though it is a valid configuration.Did you upload all of your necessary log files, screenshots, etc.?