Thus began something like two weeks of pain, suffering, and debugging, that lead us to discussions with the Windows debugger people, the Hyper-V people, and the Redhat QEMU developers (Aside: Anybody wanna bet who the most supportive/responsive team was? Anybody?)Īnyhow, we suffered so you don’t have to. And, yes, everything was swell… until we tried to hook up the kernel debugger via a network connection to that Windows VM. Installing RHEL on a spare server machine and on that a Windows VM using virt-manager is a piece of cake. I’ll spare you all the gory details about why we had to actually dev and test the driver on a Windows system running in a VM hosted by Linux, but suffice it to say there was absolutely no alternative.Īnd, really, in the beginning, we didn’t much mind. We spent several months working on a very intensive (and very interesting) project that required a writing a driver that was specifically intended to run on a Windows system running under QEMU-KVM hosted on a Linux system (specifically, RHEL 8).

Windows 10 kernel debug network