11-29-2007 14:24 janiquec

Virtual Server 2005 R2 Common Issues and Tips - Virtual Machine Saved State Failures

This post is content adapted from Chapter 11 of the Microsoft Virtual Server 2005 R2 Resource Kit.

Virtual Machine in Saved State Fails to Restart After a Change in Hardware-Assisted Virtualization State

If you enable hardware-assisted virtualization in your computer BIOS and try to start a virtual machine that was previously in a saved state, the virtual machine will not start up.

When hardware-assisted virtualization is enabled, Virtual Server internal data structures differ. Therefore, saved state files that are created when hardware-assisted virtualization is disabled cannot be used to restore a virtual machine after hardware-assisted virtualization is enabled.

Resolution

In this case, the only solution is to ensure that you shut down all virtual machines prior to switching the hardware-assisted virtualization setting in your computer BIOS.

Virtual Machine in Saved State Fails During Start Up on a Different Virtual Server Host

If you move a virtual machine that is in a saved state to another Virtual Server host, your virtual machine might fail at startup. Saved state files are not compatible when moving between different processor brands (Intel, AMD) or processor steppings (Intel Northwood, Intel Prescott).

Resolution

If you need to move a virtual machine to a Virtual Server host whose motherboard contains a different processor manufacturer or processor stepping than the originating Virtual Server host, you must completely shut down the virtual machine prior to moving the files.

Filed under: , , , ,

# re: Virtual Server 2005 R2 Common Issues and Tips - Virtual Machine Saved State Failures

Wednesday, December 19, 2007 2:17 PM by Todd Ogasawara

An additional reason for failure to restore from saved state (regardless of virtualization assist issues) is that VS2005R2 is shutdown before it can save state for all running VMs. I ran into this and was pointed to KB 888745. I had to increase the WaitToKillServiceTimeout from the default of 20000 to 90000 in order to give an HP DL385 server enough time to save the states of 6 running VMs.

Leave a Comment

(required) 
(required) 
(optional)
(required)