I have not been to enable PT with this project on a bare-metal with VBS enabled.
I found that after enabling TraceEn in StartCpuTrace(), IA32_RTIT_STATUS.Error is set to 1, indicating some buffer configuration error. Is VBS-enabled environment no longer supported? From what I see from README, I believe this project was support to work under a VBS-enabled configuration. I was also able to enable to PT when VBS/Hyper-V is not enabled.
Here is logs from the PtControlApp and debug print:
[WindowsPtDriver] Info: The processor 0 supports maximum of 2 IP ranges.
[WindowsPtDriver] Successfully mapped the local APIC to 0xFFFFD780794D2000.
[WindowsPtDriver] Successfully registered system PMI handler to function 0xFFFFF80147F68CD0.
[WindowsPtDriver] (Re)allocating 0x00010000 bytes of PT buffer for CPU 0...
[WindowsPtDriver] Requested the allocation of 0x00010000 bytes buffer for 1 CPUs (affinity 0x00000001)[WindowsPtDriver] Starting Intel Processor Trace for processor 0. Target CR3: 0x45CE8A000
[WindowsPtDriver] Enabled 1 filtering windows. IP range 1. Start VA: 0x7FF747130000, Size 0x00038000
[WindowsPtDriver] Error: unable to successfully enable Intel PT tracing for processor 0.
Windows version: 10.0.19041.423
Reactions are currently unavailable
I have not been to enable PT with this project on a bare-metal with VBS enabled.
I found that after enabling TraceEn in StartCpuTrace(), IA32_RTIT_STATUS.Error is set to 1, indicating some buffer configuration error. Is VBS-enabled environment no longer supported? From what I see from README, I believe this project was support to work under a VBS-enabled configuration. I was also able to enable to PT when VBS/Hyper-V is not enabled.
Here is logs from the PtControlApp and debug print:
Windows version: 10.0.19041.423