You can move a virtual machine to another vApp. When you move a VM, VMware Cloud Director removes the original VM from the source vApp.
When you move a VM to a different vApp, the snapshots that you have taken are lost.
Moving VMs across different vApps relies on VMware vSphere® vMotion® and Enhanced vMotion Compatibility (EVC). You can move a VM to a different vApp that belongs to the same or another organization VDC within the same organization. The organization VDC can be within the same or a different provider VDC.
Reconfiguration | VM state if the target vApp is in the same organization VDC | VM state if the target vApp in another organization VDC within the same provider VDC |
---|---|---|
change the network | powered off | N/A |
remove the network | powered on or off | N/A |
change the storage profile | powered on or off | powered off |
When you move a VM to a different vApp, VMware Cloud Director automatically copies any attached Trusted Platform Module (TPM) device. For more information on VMs with TPM devices, see Working with Virtual Machines in the VMware Cloud Director Tenant Portal.
Prerequisites
- Verify that you have the vApp Author role or an equivalent set of rights.
-
Verify that the underlying vSphere resources support vMotion and EVC. For information about the requirements and limitations of vMotion and EVC, see vCenter Server and Host Management.
-
If you want to change the VM network or the storage profile, check whether you must power off the VM. See table Reconfigurations During VM Movements and VM States.
- If you want work with VMs with TPM devices, verify that the following criteria are met.
- A VDC that supports TPM backs the VM.
- For operations across vCenter instances, verify that the key provider used to encrypt each VM is registered on the target vCenter instance under the same name.
- For operations across vCenter instances, verify that the VM and the target vCenter instance are on the same shared storage or that fast cross vCenter vApp instantiation is enabled.