[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Windows 10 Kernel Debugging on Xen

I have managed to get windbg working with a serial bridge between two
Win10 VMs using the following script:
The debugee has to enable a couple options so that windbg can attach:


On Tue, Jun 22, 2021 at 12:01 PM Neil Sikka <neilsikka@xxxxxxxxx> wrote:
> 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://bugzilla.redhat.com/show_bug.cgi?id=1947015):
> -cpu 
> Skylake-Server-IBRS,ss=on,vmx=on,hypervisor=on,tsc-adjust=on,clflushopt=on,umip=on,pku=on,md-clear=on,stibp=on,arch-capabilities=on,ssbd=on,xsaves=on,ibpb=on,amd-ssbd=on,
>  \
> skip-l1dfl-vmentry=on,mpx=off,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vendor-id=KVMKVMKVM
> note: i had to remove the following 2 arguments due to errors from QEMU:
> pschange-mc-no=on
> hv_vpindex
> Here was the error:
> C:\Users\user\Desktop\oldDebuggers\x64>kdnet.exe
> Network debugging is supported on the following NICs:
> busparams=0.4.0, Intel(R) PRO/1000 MT Network Connection, Plugged in.
> The Microsoft hypervisor running this VM does not support KDNET.
> Please upgrade to the hypervisor shipped in Windows 8 or WS2012 or later.
> KDNET initialization failed.  Status = 0xC0000182.
> NIC hardware initialization failed.
> I am using an Intel e1000 NIC emulated through QEMU because its supposedly a 
> supported NIC for Windows kernel NET debugging.
> Thanks in Advance!
> --
> My Blog: http://www.neilscomputerblog.blogspot.com/
> Twitter: @neilsikka



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.