Using Virtual PC for Windows kernel debugging

The following is an example of Virtual PC 2004, which describes the detailed process of using a Virtual PC for Windows kernel debugging.

1, download and install Virtual PC 2004, Conlio.

2, start Virutal PC Console (console), create a new Virtual PC, installation Wizard prompts configure the hard disk, memory and other parameters.

3, install the operating system on the Virtual PC you just created, which should be the version of Windows you want to debug. For example, if you want to debug a problem with your driver on Windows Server 2003, install Windows Server 2003. Let's take Windows 2000 for example.

4, configure the Virtual PC serial port, select Windows 2000 in the Avatar console, then click the Settings button to eject the Setup dialog, and then select COM1 in the list on the left (as shown below).

On the right, select the Named pipe option, which uses named pipes to simulate the serial port, and then enter the full name of the pipe: File://./pipe/com_1,com_1 can be other names, but the previous section should remain unchanged.

5, start Windows 2000 in the Virtual PC, and then go to the Command Line window and execute the following command to add debug Options to the Startup menu:

C:

cd\

Attrib-r-H

Edit Boot.ini

The last line is then copied and the debug option is added to the following state:

6, select Restart Windows 2000 in the Virtual PC, and when the boot menu appears, press the arrow keys to stop the automatic timing and wait here.

7, on the host (debugger) ready to start WinDbg, consider each input command-line parameters too cumbersome, so it is recommended to create a batch file of the following content, and put it in the same location as the WinDbg.exe directory.

Windbg-k com:pipe,port=\\.\pipe\com_1

8, run the batch file so that it also enters the wait state: