The virtual machine could not be started. The virtual machine is in a saved state and either its saved state (.vsv) file cannot be found, the user does not have permissions to restore the virtual machine from a saved state, or there is not enough physical memory available to start the virtual machine.
Possible causes include:
The virtual machine is in a saved state, and its .vsv file cannot be found. The .vsv file may have been deleted or moved from its location in the virtual machine configuration folder.
The user does not have required permissions to restore the virtual machine from a saved state on the virtual machine configuration (.vmc) file, the virtual hard disk (.vhd) file, or the .vsv files.
The virtual machine is in a saved state and there is not enough physical memory to restore it from a saved state.
There is not enough available CPU capacity to start the virtual machine. This can occur when all available CPU capacity is being used by currently running virtual machines and the host operating system.
You can take one or more of the following steps to resolve this problem:
Ensure that the .vsv file is in same folder as the virtual machine configuration file and that the user has the permissions required to save the state of the virtual machine. The user needs Write permissions on the .vmc file, the .vsv file, and the .vhd file. For more information about required permissions, see the topic on securing Virtual Server in the Virtual Server 2005 Administrator’s Guide.
Check the amount available memory in Task Manager on the host computer. If there isn’t enough available memory to start the virtual machine, make more available. You can do this by stopping any unnecessary system processes or shutting down any virtual machines that are not currently needed. As a longer-term solution, you can add more physical memory to the host computer.
Ensure that there are sufficient CPU resources available to start the virtual machine. There must be sufficient CPU capacity to run the host operating system, any currently running virtual machines, and the virtual machine that the user is attempting to restore from a saved state. For more information about CPU requirements, see the topic on system requirements in the Virtual Server 2005 Administrator’s Guide.
Virtual Server 2005 Administrator's Guide, available at http://go.microsoft.com/fwlink/?LinkID=27540
Sample Events
%1 could not be started because there is not enough free physical memory.
| 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 |
Home<Rule ID="Microsoft.Virtualization.VirtualServer.2005R2.VirtualMachine_Virtual_machine_could_not_be_started.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>^(1060|1061)$</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_Virtual_machine_could_not_be_started_Rule.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>