Comments on: How to Set Up Kernel Debugging For Windows in VMWare ESX

By: used plant machinery

used plant machinery — Tue, 20 Apr 2010 09:06:51 +0000

There may be few questions rising in your thoughts concerning machinery. Where I can buy this equipment? Methods to get one of the best inexpensive costs? The right way to test the standard of the machinery? Yes, these questions are obvious and you’re going to get the solutions as properly on this article.

By: steve heller

steve heller — Mon, 02 Nov 2009 17:54:11 +0000

Thanks for the reply. By the way, I found some additional instructions here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007086

and am trying it at present. I’ll let you know what I find out.

By: sdelmas

sdelmas — Mon, 02 Nov 2009 17:46:35 +0000

The named pipe you create with the above steps won’t be exposed to windbg. At the application (windbg) level you will just use the created com ports. So I would expect more something like -k com:port=com2 (where com2 is the newly created com port).

I tried doing a shared pipe setup myself for some time, but that just never worked properly. I hope this helps…

By: steve heller

steve heller — Mon, 02 Nov 2009 17:24:35 +0000

I’m trying to follow these steps to connect a kernel debugger between two ESX virtual machines, but I don’t know exactly what to put in the windbg startup parameters to connect to the target virtual machine. The problem seems to be the com part. Right now I have that as:
-k com:port=\\109091584855338,pipe,baud=115200,resets=0,reconnect

But that pipe name seems to be invalid. I’ve already tried what I would use for the pipe name if using two Hyper-V VMs, namely “\\.\pipe\109091584855338″, with no success. What should I have for the -k setting?

Thanks!