Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
Description
This is possible thankfully to this GitHub project: https://github.com/MovAX0xDEAD/KDNET
How to reproduce:
- Configure your VM with Intel E1000 network adapter
- Download patched kdnet.dll and kdstub.dll for Intel network adapters
- Place both files in %SystemRoot%\system32 directory
- Add new entry to the freeldr.ini (or boot.ini in Windows case)
/DEBUG /DEBUGPORT=NET /HOST_IP=192.168.1.100 /HOST_PORT=50000 /ENCRYPTION_KEY=make.reactos.great.again /W2003 /CPUFREQ=3000
- Modify HOST_IP with your host machine local IP address
- Remove /W2003 parameter in case you are testing on XP
- Change CPUFREQ to your CPU MHz value — when doubt, you can take it from registry key HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\0 value ~MHz
- Allow traffic on UDP port 50000 in firewall settings
- Start WinDbg kernel debug with NET option (available since version 6.3.9600), it should have port 50000 by default, set the key to make.reactos.great.again accordingly
- Reboot the VM and select new boot option
- Expected behavior:
VM starts and attaches to WinDbg via network (tested with Windows XP SP3 x86) - Observed behavior:
System boots to debug mode, but it doesn't try to access network adapter, so it doesn't attach to WinDbg (tested with ReactOS MSVC build 0.4.15-dev-1249-g1f377076d78)
Attachments
Issue Links
- blocks
-
CORE-18223 Implement KDNET NIC driver for nVidia nForce adapters
- Open
- is blocked by
-
CORE-17808 Missing cookie generation in the very early stage of boot
- Open