Remote debugging of WinDbg is done. There are two virtual machines. The debugger is installed on the machine (host), which is connected via the port with the target OS (target). Virtual machines are connected via a pipe with the host system. Here is an example of a Boot.ini file for Windows xp.

[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /sos multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /sos /debug /debugport=com1 /baudrate=115200 

There is no Boot.ini file in Win7. But there is a wonderful utility BCDEDIT. Tell me how to use it to configure the bootloader in the same way as it was done for XP

  • I recommend configuring with neosmart.net/EasyBCD - it even prefers to write to Linux. However, they say, it works only with a classical BIOS, and is not friendly with UEFI, but I can’t verify it. - Qwertiy ♦
  • Thanks, I’ll look at it, but I would still like to figure out the way I’ve described it, it seems that only the “edits” of Boot.ini are lacking, which doesn’t look complicated - May
  • To translate and write in response is too much. So I’ll leave it here: Remote Debugging Using WinDbg - Sergey Nudnov
  • Oh, here it is, closer to answering the question: Setting Up Kernel-Mode Debugging over a Serial Cable Manually - Sergey Nudnov
  • What you need, thank you - art__

1 answer 1

Source: Setting Up Kernel-Mode Debugging over a Serial Cable Manually

Important! Before using bcdedit to change boot information, you must temporarily stop security options such as BitLocker and Secure Boot on a test PC. You can re-enable them when debugging is complete, and you have disabled kernel debugging .

  1. On the computer being debugged, open Command Prompt with elevated privileges and enter the following commands, where n is the COM port number used for debugging this computer and rate is the connection speed used for debugging:

 bcdedit /debug on bcdedit /dbgsettings serial debugport:n baudrate:rate 

For information: The connection speed must be the same on the host and the computer being debugged. Recommended speed: 115200.

  1. Restart the computer being debugged.

Similar instructions for debugging a virtual machine through a virtual COM port are available here: Setting Up Kernel-Mode Debugging of a Virtual Machine Manually using a Virtual COM Port