If the Backup Application being used to restore a Hyper V Virtual Machine restores a VM to a new Hyper V Host machine the Virtual Machine may not start.
The failure to start the Virtual Machine after a successful restore may be caused by the following failures:
1) The network adapater name is not consistent with the new Host
2) There is a conflict in the saved state data from the original Host and the new Host regarding machine configuration (ie video state)
The steps to resolve this are:
1) Open the Hyper-V Management Console.
2) Open Virtual Network Managerwhich can be found in the right side pane.
3) Rename the network adapater to the same name as the name used on the New Host.
4) Attempt to start the virtual machine. If it does not start, delete the saved state files for this virtual machine by right clicking on the virtual machine and selecting the Delete Saved State... menu item.
5) If step 4 doesn't work then you will have to navigate to thevirtual machines folder and locate the appropriate GUID folder and manually delete these files (.bin and .vsv files).
6) The virtual machine should now start.
This behavior is expected and by design. Step 4 will resolve the 2nd cause listed, by deleting the saved state data you allow the machine to reset the video state.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Artikel-ID: 2502233 - Geändert am: Montag, 14. Februar 2011 - Version: 3.0
Kontaktieren Sie uns, um weitere Hilfe zu erhalten