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/
I'm trying to debug Hyper-V communication and come across of the strange problem.
My Setup: Windows 10 w/o HYPER-V installed + VMWare Workstation 16 Pro + WinDbg.
In VMWARE I have a VM running Windows 10 2004 with HYPER-V enabled. VM uses Serial Port connected to the named pipe. WinDbg connects to the named pipe as well. The same setup work fine for the Kernel debugger (using, of course, another named pipe)
When I'm breaking into WinDbg at startup (e.g. using "-d" switch for WinDbg), I can do everything: set break points, stop on break points, dump memory, debug initialization of Hyper-V, etc). However, after VM is completely started, I can break into WinDbg only once. After resuming the VM execution (F5 or 'g') VM is completely frozen. I also cannot break into debugger for the second time.
Is anybody encountered similar problem? Any suggestion?
Thank you in advance,
|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!|
|Writing WDF Drivers||12 September 2022||Live, Online|
|Internals & Software Drivers||23 October 2022||Live, Online|
|Kernel Debugging||14 November 2022||Live, Online|
|Developing Minifilters||5 December 2022||Live, Online|