I figured it out. Microsoft did not document that testsigning needs to be
enabled for kdnet to work.
On Tue, Jun 22, 2021 at 2:12 PM Tamas K Lengyel
wrote:
> Make sure windbg is already waiting for the connection from the
> debugee by the time Windows starts booting. If you try to attach
> windb
Make sure windbg is already waiting for the connection from the
debugee by the time Windows starts booting. If you try to attach
windbg later it won't work. It worked for me but obviously YMMV.
Tamas
On Tue, Jun 22, 2021 at 2:07 PM Neil Sikka wrote:
>
> I tried that, but it seems like I'm gettin
I tried that, but it seems like I'm getting an interrupt storm on the
debugger VM (CPU spends all its time in the kernel) when I try to attach
the debugger. This observation furthers my suspicion that there is
communication, but there is something wrong with the protocol...
On Tue, Jun 22, 2021 at
I used Xen 4.15 and a pretty new version of Windows 10. It is a bit
finicky, you have to run the debug commands on the debugee and then
reboot. When the VM is rebooting the domain ID changes so you have to
start the serial bridge then. Windbg will attach afterwards. Just make
sure both VMs have ser
Thanks for the quick response, Tamas. I tried what you said and windbg
waits and the debugee hangs when I click the break button in windbg, but I
don't see any output in windbg. This means that there is SOME communication
over the serial port that causes the debugee to hang when I click break.
Coul
I have managed to get windbg working with a serial bridge between two
Win10 VMs using the following script:
https://github.com/intel/kernel-fuzzer-for-xen-project/blob/master/scripts/serial-bridge.sh.
The debugee has to enable a couple options so that windbg can attach:
https://github.com/intel/ker
Hello,
Has anyone gotten a Windows10 (Version 1709 of later) kernel debugger
attached when running the Windows10 debugger VM and the Windows10 debugee
VM on Xen 4.13.0 hypervisor? I am getting a "NIC hardware initialization
failed" error. I tried the suggestions in the discussion here (
https://bug
