WinDBG and Vista x64 in VMWare

WINDBG
1

First of all, I already posted this message 4 hours ago via the webinterface. Unfortunately the message does not appear till now, and so I try it again via email.

I set up a Windows Vista x64 virtual machine in VMWare 6. I connect to that machine via a named pipe.
My WinDBG command line is:
windbg.exe -b -k com:pipe,port=\.\pipe\VistaX64,resets=0

Everything works fine. WinDBG connects to the virtual machine, and I am able to break the whole machine via Ctrl+Break.

Unfortunately the debug output does not appear in the WinDBG command output. Neither the user mode one (via OutputDebugString), nor the kernel mode one (via DbgPrint). DbgView (running inside the virtual machine) recognizes the debug output though. A Windows XP x86 virtual machine works fine.

What did I do wrong?

-Christopher

Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker.

2

This is a Vista/Longhorn issue/feature; it has nothing to do with
VMWare. By default, these versions of Windows disable output from
KdPrint/DbgPrint, which results in basically nothing being displayed
other than the os loader messages. To enable it, the easiest thing to
do is enter

ed nt!Kd_DEFAULT_Mask 0x0F

This will replicate the scenario you are used to on XP.

You can also set a registry key on your host so that you don’t have to
set this each time the target boots. For the full details, which are
messy, see the documentation in the WDK for KdPrintEx. In a nutshell,
it is possible to specify greater granularity controlling which
components display traces and which don’t, but I don’t personally find
it worth the trouble, for my purposes.

Good luck,

mm

Chrissi13378 Chrissi13378 wrote:

First of all, I already posted this message 4 hours ago via the
webinterface. Unfortunately the message does not appear till now, and so
I try it again via email.

I set up a Windows Vista x64 virtual machine in VMWare 6. I connect to
that machine via a named pipe.
My WinDBG command line is:
windbg.exe -b -k com:pipe,port=\.\pipe\VistaX64,resets=0

Everything works fine. WinDBG connects to the virtual machine, and I am
able to break the whole machine via Ctrl+Break.

Unfortunately the debug output does not appear in the WinDBG command
output. Neither the user mode one (via OutputDebugString), nor the
kernel mode one (via DbgPrint). DbgView (running inside the virtual
machine) recognizes the debug output though. A Windows XP x86 virtual
machine works fine.

What did I do wrong?

-Christopher

*Ihre erste Baustelle?* Wissenswertes für Bastler und Hobby Handwerker.
http:
></http:>

3

By the way, posting delays do occur sometimes on these lists, although
I’m not sure that’s what happened here. In any case, if you want to
guarantee the quickest possible post time, I would consider using the
news reader interface. I don’t know how the web interface figures in to
this, but the e-mail interface is the slowest when there are problems,
and the newsreader, in my experience, always works well, which may be
the case for the web interface as well; I really don’t know. I’m sure
that Scott and/or Peter will be along sometime to correct me if I am
wrong here.

Good luck,

mm

Martin O’Brien wrote:

This is a Vista/Longhorn issue/feature; it has nothing to do with
VMWare. By default, these versions of Windows disable output from
KdPrint/DbgPrint, which results in basically nothing being displayed
other than the os loader messages. To enable it, the easiest thing to
do is enter

ed nt!Kd_DEFAULT_Mask 0x0F

This will replicate the scenario you are used to on XP.

You can also set a registry key on your host so that you don’t have to
set this each time the target boots. For the full details, which are
messy, see the documentation in the WDK for KdPrintEx. In a nutshell,
it is possible to specify greater granularity controlling which
components display traces and which don’t, but I don’t personally find
it worth the trouble, for my purposes.

Good luck,

mm

Chrissi13378 Chrissi13378 wrote:
> First of all, I already posted this message 4 hours ago via the
> webinterface. Unfortunately the message does not appear till now, and
> so I try it again via email.
>
> I set up a Windows Vista x64 virtual machine in VMWare 6. I connect to
> that machine via a named pipe.
> My WinDBG command line is:
> windbg.exe -b -k com:pipe,port=\.\pipe\VistaX64,resets=0
>
> Everything works fine. WinDBG connects to the virtual machine, and I
> am able to break the whole machine via Ctrl+Break.
>
> Unfortunately the debug output does not appear in the WinDBG command
> output. Neither the user mode one (via OutputDebugString), nor the
> kernel mode one (via DbgPrint). DbgView (running inside the virtual
> machine) recognizes the debug output though. A Windows XP x86 virtual
> machine works fine.
>
> What did I do wrong?
>
> -Christopher
>
> ------------------------------------------------------------------------
> *Ihre erste Baustelle?* Wissenswertes für Bastler und Hobby
> Handwerker.
> http:
>>
></http:>