Seems like VirtualKD 3.0 does not work after updating to VMWare Workstation 14

[s0ne]

I’m using Windows 10 Insider Preview 17017(rs4 pre_release) x64 as a local host OS, and also using VMWare Workstation 14 latest version.

I want to debug Windows 10 Enterprise 15063 x64 as guest OS. VirtualKD’s virtual machine monitor can detect CPU utilization and pipe_name, but it can not get information such as packets, resets, OS, Debugger, Poll rate.

So it windbg cannot attach to guest kernel.

Here is log message from virtual machine monitor.

<hr />

*******************************************************************************
*VirtualKD patcher DLL successfully loaded. Patching the GuestRPC mechanism…*
*******************************************************************************
Searching patch database for information about current executable…
No information found.
Waiting for VMWare to initialize (5966 ms more to wait)
Analyzing VMWARE-VMX executable…
Building list of EXE sections… 22935K of data found.
Scanning for RPC command name strings…
Finished scanning. Found 55 strings.
Searching for string references…
Found 31 string references.
Found 3 structures resemblant to RPC dispatcher table.
(address 8F885190, matched pointers: 1)
(address 8F8851A0, matched pointers: 1)
(address 8FC77AA8, matched pointers: 29)
Analyzing potential RPC dispatcher tables…
Potential RPC table analyzis complete. Found 1 candidates.
(address 8FC76F18, entries: 105, free entries: 32)
Using RPC dispatcher table at 0x7FF78FC76F18 (105 entries)
Waiting for RPC table to be initialized by VMWare…
RPC table initialized. Patching it…
Successfully patched entry #2
VMWare reset monitor activated…

 

Does anybody have experience like this?

• This topic was modified 6 years, 6 months ago by s0ne.
• This topic was modified 6 years, 6 months ago by s0ne.
• This topic was modified 6 years, 6 months ago by s0ne.

[manu]

VMWare Workstation 14 comes with support for VBS (with Secure Boot) and all other security related features based on Hypervisor.

I worked around it by disabling it and following the previous steps that used to work.

https://github.com/sysprogs/VirtualKD/issues/8

 

[Author]

Posts