Can’t connect when use bootdebug option

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Can’t connect when use bootdebug option

Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • September 14, 2011 at 12:27 #347
    Anonymous
    Participant

    I’m using VMWare 7.1.4 + VirtualKD 2.5.4. Guest OS is Windows 7 Pro SP1

    I’m current work on a HBA driver, and I need debug from bootloader.
    So, I do such as thing:
    bcdedit /bootdebug {bootmgr} on

    The VirtualKD was work perfect, but after use bootdebug option, WinDBG can’t connect to guest OS.
    Then I try to use pipe com port, it’s connected!

    I guess that is bootloader try to access hardware directly, not via kdext module?

    Is there is any way to solve this problem? or I must debug via pipe com_1 ?

    November 26, 2011 at 22:09 #1958
    support
    Keymaster

    Not 100% sure, but I think I’ve stumbled upon some article from Microsoft explaining that the loader debugging is only possible using COM1. I would suggest googling around to see if anyone managed to set up other protocol for the bootloader (e.g. FireWire).

  • Author
    Posts
Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.