VM to VM debugging with Hyper-V

NTDEV
1

All,

so far my attempts to setup kernel debug from one VM to another VM using
pipes on hyper-V (gen 1) has failed. it appears that it is not a supported
configuration and that MSFT expects us to debug the VM from the pysical
server hosting the hyper-v role itself.

i would like to confirm if indeed that is the case, or I am missing
something basic here?

also, has the situation changed with gen 2?

2

I believe you can do this by having *something* running on the Hyper-V host that can merge the 2 pipes from the VMs. This *something* has to read on one pipe and write to the other and vice versa.

3

Hi,

You should post the pipe name to see how you configured it. If the debugger is running on VMMachine1 then you could try the following pipe configuration:

\PhysicalMachineName\pipe\PipenameForComPortOnVMMachine2

Read this this:

http://blogs.msdn.com/b/ntdebugging/archive/2011/12/30/configuring-a-hyper-v-vm-for-kernel-debugging.aspx

Regards.

4

>so far my attempts to setup kernel debug from one VM to another VM using pipes on hyper-V (gen 1)

has failed. it appears that it is not a supported configuration and that MSFT expects us to debug the
VM from the pysical server hosting the hyper-v role itself.

No, it even works with the WinDbg client being a separate physical desktop on a network.

In the client, be it a VM or a separate physical box, use the \HyperVServerName\pipe.… pipe name.

–
Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com

5

Check com port of your printer as well sometimes printer use to prompt
Communication through com port for windbg.