Open
Description
When I enable rdtsc exiting within the primary processor controls of the VMCS, my entire system hangs (tested on both VM & baremetal).
- I have tried using a fresh download of gbhv to rule out any of my changes to the project.
- I have created a handler for rdtsc exiting, which never gets triggered. In fact, no exits occur overall. (So vmlaunch is definitely hanging/erroring??)
- I have tried installing a debug break directly before the vmlaunch and tracing the vmlaunch, however my entire system hangs and WinDbg cannot trace through the vmlaunch.
- I have downloaded a separate hypervisor (HyperPlatform) and enabled rdtsc exiting, which worked as intended
I am guessing that there is some conflict within the VMCS with rdtsc exiting and some other control, but I have read through the Intel SDM and looked for all references of the rdtsc exiting field, and there seems to be no information on control conflicts or requirements for rdtsc exiting other than that rdtsc offsetting must be disabled (which it is).
I have hit my experience cap when it comes to hypervisor development, and I am searching for further assistance. Thanks.
Metadata
Metadata
Assignees
Labels
No labels