Restored Hyper-V Virtual Machines Won't Start

Article ID: 2502233
Expand all | Collapse all

SYMPTOMS

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.

CAUSE

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)


RESOLUTION

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.

MORE INFORMATION

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.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2502233 - Last Review: February 14, 2011 - Revision: 3.0
Keywords: 
KB2502233

Give Feedback