Share via

Unable to remove remnants of migrated guests in hyper-v cluster

Dieter Modig 1 Reputation point
2021-03-29T11:02:45.437+00:00

We're running a 2019 Hyper-V cluster. During a patch operation the host was not drained of all roles before paused and rebooted. This has resulted in a virtual machine that can't be migrated to the specific host again. The mentioned host gets an error at boot (when VMMS starts) because it tries to find a missing virtual machine. The virtual machine resides on another host in the cluster.

We've tried stopping VMMS and removing files in "%Programdata%\Microsoft\Windows\Hyper-V\Virtual Machines Cache" but the files keep re-appearing once VMMS starts up again.

Where else should we look for this ghost entry?

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xiaowei He 9,941 Reputation points
    2021-03-30T06:15:06.023+00:00

    Hi,

    Please check if the configuration file still exists in the following place:

    C:\ ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.