Virtual machines that were created on the beta version of the Hyper-V role do not start after the Hyper-V role is updated to a later version

Virtual machines that were created on the beta version of the Hyper-V role do not start after the Hyper-V role is updated to a later version

Article ID : 949222
Last Review : March 19, 2008
Revision : 1.0
On This Page

SYMPTOMS

You have the beta version of the Hyper-V role installed on the release version of Windows Server 2008.You update the Hyper-V role to a later version. In this situation, virtual machines that were created on the beta version of the Hyper-V role do not start. Additionally, you receive the following error message:

An error occurred while attempting to chance the state of the virtual machine vmname.
‘vmname’ failed to initialize.
Failed to read or update VM configuration.

Back to the top

CAUSE

This issue occurs because virtual machine configurations that were created on the beta version of the Hyper-V role are incompatible with later versions of the Hyper-V role.

Back to the top

RESOLUTION

If the virtual machine is running a Hyper-V-supported release version of an operating system, you can use the existing virtual hard disk (.vhd) file. However, the virtual machine configuration settings must be re-created. If the virtual machine is running a prerelease version of Windows Server 2008, the virtual machine configuration settings and the operating system .vhd file must be re-created.

To delete and then re-create the virtual machines, follow these steps.

Back to the top

Step 1: Remove the virtual machines

To remove virtual machines that were created on the beta version of the Hyper-V role, follow these steps:

1. Open the Hyper-V Manager console.
2. Document the configuration settings for each virtual machine.
3. Click Delete Save State for each virtual machine that is currently in a Saved state.
4. Click Delete Snapshot Subtree for each virtual machine that has snapshots.

Note As soon as you delete the snapshots, the changes that exist in the snapshot files (.avhd files) will merge into the parent .vhd file. This operation may take a while. To verify that the snapshots have merged into the parent .vhd file, check the location in which the snapshots are stored to verify that no .avhd files exist.

5. On the Action menu, click Virtual Network Manager, and then verify that all virtual networks that were created on the beta version of the Hyper-V role have been deleted.

Note All virtual networks that were created on the beta version of the Hyper-V role will be removed when you update the Hyper-V role to a later version.

6. Copy the .vhd file to a safe location.

Note If the virtual machine is running a prerelease version of Windows Server 2008, the operating system .vhd file must be re-created.

7. In the Hyper-V Manager console, delete all virtual machines that were created on the beta version of the Hyper-V role.

Back to the top

Step 2: Re-create the virtual machines

To re-create the virtual machines, follow these steps:

1. Open the Hyper-V Manager console.
2. On the Action menu, click Virtual Network Manager, and then re-create your virtual networks.
3. Use the New Virtual Machine Wizard to re-create your virtual machines.

Note If you previously saved a .vhd file that contains a Hyper-V-supported release version of an operating system, you can click Use an existing virtual hard disk, and then point to your existing .vhd file. If the virtual machine is running a prerelease version of Windows Server 2008, the operating system .vhd file must be re-created.

4. As soon as the operating system is installed, install the Integration Services in the virtual machine:

• To install the latest version of the Integration Services for operating systems other than Windows Server 2008, open the Virtual Machine Connection window, and then click Insert Integration Services Setup Disk on the Action menu.
• To install the latest version of the Integration Services for Windows Server 2008, apply the update package to the virtual machine.

For example, to update the virtual machine, you would use the Hyper-V Release Candidate that is mentioned in the following article in the Microsoft Knowledge Base article:

949219 (/Feedback.aspx?kbNumber=949219/) Description of the Hyper-V Release Candidate update for Windows Server 2008

You can use one of the following methods to apply the update to the virtual machine:

• Add a Legacy Network Adapter to the virtual machine, and then copy the update package from another computer. Or, use Windows Update to apply the update.
• Burn the update package to a CD or to a DVD, and then mount the CD or the DVD in the virtual machine.
• Create an ISO image that contains the update package, and then mount the ISO in the virtual machine.

Back to the top

MORE INFORMATION

For more information about Hyper-V, visit the following Microsoft Web site:

http://technet2.microsoft.com/windowsserver2008/en/servermanager/virtualization.mspx (http://technet2.microsoft.com/windowsserver2008/en/servermanager/virtualization.mspx)

Back to the top


APPLIES TO
• Windows Server 2008 Datacenter
• Windows Server 2008 Enterprise
• Windows Server 2008 Standard

Back to the top

Keywords: 
kbsnapin kbconsole kbtshoot kbexpertiseinter kbprb KB949222

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image