Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


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/


Using WinDbg to debug Hyper-V

MetekMetek Member - All Emails Posts: 55

Hello All!

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,

Al

Comments

  • 0xrepnz0xrepnz Member Posts: 41

    I think you need two instances of Windbg to debug HyperV. This should be a good resource for debugging HyperV: https://msrc-blog.microsoft.com/2018/12/10/first-steps-in-hyper-v-research/

    - Ori Damari
  • MetekMetek Member - All Emails Posts: 55

    I tried initially with two instances of WinDbg. As I wrote in my initial post - The The same setup work fine for debug Virtual Partition (Windows Kernel) using, of course, another named pipe).

    Unfortunately regardless second instance of WinDbg is connected or not - the problem remain: I can debug Hyper-V initialization, but as soon as Virtual Partition is up and running, any break to WinDbg instance connected to Hyper-V itself will be the last one.

    Is anybody encountered similar problem? Any suggestion?

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

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 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters 8 March 2021 LIVE ONLINE