Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Windbg "waiting to reconnect" with Laptop and VM as target

fusepoppedfusepopped Member Posts: 1

It seems that Im leagally required to tell you that I belong in the group of Students, Hobbyists, Dilettantes, and Dabblers. Strong emphasis on the last two.

I tried several guides and things related to them:

VM is VirtualBox btw.

The end result is always the same. Windbg says "waiting to reconnect" and nothing happend bexonf this point.

If I would at least know how to properly check if all preconditions are met on host and target side. But Im really not sure.

bcdedit on target VM for example does not look right to me:

PS C:\Windows\system32> bcdedit

Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
default                 {current}
resumeobject            {0f9b6fad-dcd5-11eb-9458-a05e50d80135}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows-Startladeprogramm
-------------------------
Bezeichner              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 10
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {0f9b6faf-dcd5-11eb-9458-a05e50d80135}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {0f9b6fad-dcd5-11eb-9458-a05e50d80135}
nx                      OptIn
bootmenupolicy          Standard
debug                   Yes
PS C:\Windows\system32>

kdnet says NIC is supported. The

PS C:\Windows\system32> & "C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\kdnet.exe"

Network debugging is supported on the following NICs:
busparams=0.3.0, Intel(R) PRO/1000 MT Desktop Adapter, KDNET is running on this NIC.

Network debugging is not supported on any of this machine's USB controllers.


KDNET transport initialization failed during a previous boot.  Status = 0xC00000B5.
InitializeNetwork failed to get the MAC address of the host debugger. Check the dbgsettings hostip!
PS C:\Windows\system32>

Comments

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 14,111

    You'd need to say bcdedit /debugsettings to see how the network debugging is configured. If you are debugging a VM from its host system, often the easiest option is to use a fake serial port.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Internals & Software Drivers 15 November 2021 Live, Online
Writing WDF Drivers 24 January 2022 Live, Online
Developing Minifilters 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online