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

150 PlateSpin Orchestrate 2.0 VM Client Guide and Reference
no
vd
ocx
(e
n)
13
Ma
y 20
09
10.3 Moving or Migrating the VMs
Š
“VM is out of sync in the VM Client after it was moved” on page 150
Š
“Moving or migrating VMs between two ESX hosts that are registered to a vCenter server by
using the Orchestrate Development Client fails” on page 150
Š “Moving a VM from one ESX host local storage to another ESX host local storage might fail”
on page 150
Š
“A migrated VM’s Orchestrate Agent loses connection with the Orchestrate Server” on
page 150
VM is out of sync in the VM Client after it was moved
Explanation: If you move a VM outside of the VM Client, such as from a command line or
in using the Development Client, the VM is out of sync and cannot be used.
Possible Cause: Moving a VM outside of the VM client causes its state to be out of sync
between the VM Client and the Orchestrate Server.
Action: To resynchronize the VM in the VM Client:
1 Right-click the VM that was moved, then select Resync State .
Moving or migrating VMs between two ESX hosts that are registered to a vCenter
server by using the Orchestrate Development Client fails
Source: The PlateSpin Orchestrate VM Client.
Action: Do the following:
1
Disconnect and remove one of the ESX hosts from the vCenter server.
2 Move or migrate the VMs by using the Orchestrate Development Client.
For more information, see
Section 5.9, “Moving VMs,” on page 108 or
Section 5.10, “Migrating VMs,” on page 110 .
Moving a VM from one ESX host local storage to another ESX host local storage
might fail
Source: The PlateSpin Orchestrate VM Client.
Explanation: When you try to use the VM Client to move a VM of considerable size from
one ESX host local storage to another ESX local storage, the move job might
fail with the following error message:
Job timeout, because Max elapsed time expired.
Action: In the policy associated with the VM, appropriately increase the time-out
value. For more information, see “ Provisioning a Virtual Machine ” in the
PlateSpin Orchestrate 2.0 Virtual Machine Management Guide .
A migrated VM’s Orchestrate Agent loses connection with the Orchestrate Server
Source: The PlateSpin Orchestrate VM Client.
Explanation: After you migrate a Xen VM that has the Orchestrate Agent installed, the
agent might lose connection with the Orchestrate Server.