Novell PLATESPIN ORCHESTRATE 2.0.2 - ADMINISTRATOR REFERENCE 06-17-2009, Client Manual, Page: 82 / 164

82 PlateSpin Orchestrate 2.0 VM Client Guide and Reference
no
vd
ocx
(e
n)
13
Ma
y 20
09
Š
To cancel an action in the Development Client , go to the Explorer tree view. Under the
Resources subsection, locate the VM in one of the Resources subsections (such as VMs ), right-
click the VM, then select Cancel Action .
In the VM Client window, the Status column should now show the previous state of the VM.
5.3.3 Starting a VM
In order to start a VM on a host server, the following conditions must exist:
Š
The VM’s files and image must be either:
Š
Stored locally on the host server.
or
Š
Stored in a shared repository accessible by the host server.
Š
The host server and VM must have the same architecture (such as 32-bit or 64-bit), mount
points, and routing of network connections to the virtual network.
For example, a 64-bit paravirtualized guest created on a 64-bit hypervisor can be started on a
host server running a 64-bit hypervisor, but not a 32-bit hypervisor. Or, a 32-bit VM created on
a 64-bit hypervisor can be started on a 64-bit hypervisor host. In other words, you cannot start a
VM on a host that has a different architecture from the host where the VM was created.
Š
The host server cannot be fully utilized, because it would be incapable of hosting the VM.
Š
The host server cannot have met its maximum allowable VMs. This value is set in the
Development Client in the
Max Hosted VMs field. The default is 8. It doesn’t matter whether
the maximum VMs that the host server is already hosting are fully utilizing it.
Š
The VM cannot be disabled by having its Resource Enabled check box deselected in the
Development Client. By default, this check box is enabled.
Š The VM cannot be out of sync, which can occur if it is manually accessed or manipulated via a
third-party tool. For example, you could manually start the VM on the physical host machine.
However, you can
resynchronize the VM with the Orchestrate Server.
Host servers are only available if they are not out of sync .
These conditions are automatically enforced with constraints .
If the above criteria are met by the VM and only one host server, then the VM is automatically
started on that host server, provided the VM’s files reside on that server or in a shared repository.
If the criteria are met by multiple host servers and the VM’s files reside in a shared repository, you
can start the VM by selecting any host server, or by selecting to have the Orchestrate Server
automatically select the host server.
If no host servers meet these requirements, or if the VM doesn’t meet its requirements, the No Start
Target Available dialog box is displayed, indicating that you need to resolve the issues to continue.
You can start any VM that is not running. However, starting a paused or suspended VM can cause its
previously saved state to be lost. For more information on paused or suspended VMs, see
Section 5.3.6, “Pausing a VM,” on page 85 and Section 5.3.8, “Suspending a VM,” on page 85 .