The virtual machine cannot be restored from a saved state and therefore cannot run. The virtual machine, including its saved state (.vsv) file, may have been moved from Virtual PC to Virtual Server or from a computer running a different type of processor. As a result of this move, the .vsv file is not compatible with the current environment. Move the virtual machine back to the original environment, restore the virtual machine, and then try again to move the virtual machine to the new environment.
The .vsv file is not compatible with the current environment. This is because:
The virtual machine was saved on one computer and restored on a different computer with a different processor type. For example, the virtual machine may have been saved on a computer running an Intel processor and moved to a computer running an AMD processor.
The virtual machine, including its saved state (.vsv) file, was moved from Virtual PC to Virtual Server.
Restore the virtual machine in the environment where its state was originally saved; in other words, either on the original computer or on Virtual PC. For instructions, see the topic on saving or restoring the state of a virtual machine in the Virtual Server 2005 Administrator’s Guide.
After restoring the virtual machine, shut it down, and then again move it to the new computer or to Virtual Server.
Virtual Server 2005 Administrator's Guide, available at http://go.microsoft.com/fwlink/?LinkID=27540
Sample Events
%1 could not be restored because the saved state was either corrupt or incompatible with this version of Virtual Server.
Target | Microsoft.Virtualization.VirtualServer.2005R2.VMHost | ||
Category | AvailabilityHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | Virtual Server |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Virtualization.VirtualServer.2005R2.VirtualMachine_Incompatible_saved_state.rule" Enabled="true" Target="Microsoft.Virtualization.VirtualServer.2005R2.VMHost">
<Category>AvailabilityHealth</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Virtual Server</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Virtual Server</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventCategory</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesMOM2005RegularExpression</Operator>
<Pattern>^(1077|1078)$</Pattern>
</RegExExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Virtualization.VirtualServer.2005R2.VirtualMachine_Incompatible_saved_state_Rule.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>