I went to setup a Server 2012 R2 Hyper-V system for guest debugging but found the WMI classes had changed with the new root\virtualization\V2 namespace. Is the method of guest debugging with the kdvm transport no longer supported?
I have firewire to the Hyper-V host. It seems like there used to be a way to debug guests with firewire too, like back in very early Hyper-V days. Am I just imagining that?
So what is a high performance kernel debugging transport for hyper-v guests? I read you can still configure a virtual serial over named pipe debugger port, but those are just so slow, especially when my host has an LSI firewire card.
I suppose I could use a different hypervisor, like one that supports emulating an Intel NIC. I suppose I could just forget about debugging in a VM, and just use firewire to the physical machine, although just today the ability to snapshot a VM came in very handy.
I was hoping we could do fast debugging in a VM, but perhaps the only options now are fast OR a have a VM 
Jan
I don’t know the answer to this, but you might want to try asking this in
NTDEV. Hyper-V folks aren’t necessarily monitoring this side.
-scott
@OSRDrivers
“Jan Bottorff” wrote in message
news:xxxxx@windbg…
I went to setup a Server 2012 R2 Hyper-V system for guest debugging but
found the WMI classes had changed with the new root\virtualization\V2
namespace. Is the method of guest debugging with the kdvm transport no
longer supported?
I have firewire to the Hyper-V host. It seems like there used to be a way to
debug guests with firewire too, like back in very early Hyper-V days. Am I
just imagining that?
So what is a high performance kernel debugging transport for hyper-v guests?
I read you can still configure a virtual serial over named pipe debugger
port, but those are just so slow, especially when my host has an LSI
firewire card.
I suppose I could use a different hypervisor, like one that supports
emulating an Intel NIC. I suppose I could just forget about debugging in a
VM, and just use firewire to the physical machine, although just today the
ability to snapshot a VM came in very handy.
I was hoping we could do fast debugging in a VM, but perhaps the only
options now are fast OR a have a VM L
Jan
com port is the only supported option as of now.
While it might be a bit slow, I typically attach the debugger to VM on the host and create a remote to connect to it from other host and that’s been working just fine for me.