Problems running WinDBG with VirtualBox

WINDBG
1

I am just starting out with device driver writing after years of application programming.

I want to be able to get WinDbg to work with a driver running on a virtual machine (VirtualBox).

I have followed the instructions on http://www.personal.psu.edu/jdl5225/blogs/eportfolio/Instruction_Set.pdf

The operating system (Win 7 Home Premium) is installed on the virtual system. The boot settings are set for debug on a com port. The virtual system has a piped com port. I have started windbg and entered kernel debug, setting the com port settings to match the pipe. The command window opens with the following text:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\pipe\com_debug_1
Waiting to reconnect…

The status bar says “Debuggee not connected”.

I have selected “break” from the debug menu. The target operating systems stops (No mouse control), but no change to the command window.

What am I doing wrong?

2

Hmm. It’s been a while since I’ve heard a report of this one. Target
halted, but windbg not breaking in.

It did get fixed, so while it’s not likely your problem, the first thing
I’d recommend doing is upgrading your windbg by installing the win7 ddk.
It’s included.

Otherwise, what version of vbox are you using?

Another option I’d recommend is using virtualkd. It’s the best way to use
windbg with a vm, and I know that the instructions are accurate (though
they are fairly sketchy sounding).

Mm
On Apr 19, 2012 2:49 AM, wrote:

> I am just starting out with device driver writing after years of
> application programming.
>
> I want to be able to get WinDbg to work with a driver running on a virtual
> machine (VirtualBox).
>
> I have followed the instructions on
> http://www.personal.psu.edu/jdl5225/blogs/eportfolio/Instruction_Set.pdf
>
> The operating system (Win 7 Home Premium) is installed on the virtual
> system. The boot settings are set for debug on a com port. The virtual
> system has a piped com port. I have started windbg and entered kernel
> debug, setting the com port settings to match the pipe. The command window
> opens with the following text:
>
> --------------------------------------------------------------------------------------------------------
> Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\pipe\com_debug_1
> Waiting to reconnect…
>
> --------------------------------------------------------------------------------------------------------
>
> The status bar says “Debuggee not connected”.
>
> I have selected “break” from the debug menu. The target operating systems
> stops (No mouse control), but no change to the command window.
>
> What am I doing wrong?
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

3

If you know everything is configured correctly then I recommend hitting ‘break’ aggressively. Sometimes it can be a pest!

4

Maybe u can try using virtualkd…it is more easier and straight forward
based on my experience…

On Thu, Apr 19, 2012 at 9:55 PM, wrote:

> If you know everything is configured correctly then I recommend hitting
> ‘break’ aggressively. Sometimes it can be a pest!
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

5

The VirtualKD solution worked. Thanks to everyone that replied.