Hyper-V bug resulting in: Cannot access the data folder of the virtual machine
Is there a fix yet for this issue?
Hyper-v snapshot becomes unusable until you manually edit the corrupted xml after deleting a historical snap shot.
Easily reproducable. Just delete a historical snap and the .xml gets extra characters resulting in the corrupted state of: Cannot access the data folder of the virtual machine
Work around: Open xml and scroll to the bottom. Remove any extra characters from the bottom of the xml. Normally just one character (‘>’) at the end but can be an "echo"
of the last 1-30 characters.
Then restart the hyper-v and it works till you descide to delete another historical snap.
This issues has been happening for over a year and is reproducable. Others have had the issue so I am suprised that it hasn’t been addressed yet.
Same as locked issue:
- Hyper V Node performance Issues February 19, 2019
- Cannot take checkpoint for ‘because one or more synthetic fibre channel controllers are attached February 19, 2019
- Cannot take checkpoint for ‘because one or more synthetic fibre channel controllers are attached February 19, 2019
- Hyper-V more than 8 NIC for VM February 19, 2019
- How to monitor performance for a specific VM in Hyper-V February 19, 2019