5. Creating and Managing vApps : 5.1 Migrating Workloads to a vCloud : 5.1.3 vApp Migration : 5.1.3.6. Resource Allocation
   
5.1.3.6. Resource Allocation
Resource allocation controls set on the individual virtual machines in a vApp are maintained across a migration from vCloud A to vCloud B. However, for the settings to be used, the vApp must be deployed to a virtual datacenter that uses a Reservation Pool allocation model. Datacenters that use the Allocation Pool or Pay-As-You-Go model do not support resource allocation controls.
The following table summarizes vApp parameters and notes whether they are maintained across a migration.
Table 2. vApp Parameters
Configuration Item
Maintained?
Notes
Start/Stop Order
Yes
 
Start Action
Yes
 
Stop Action
Yes
 
Start/Stop Delay
Yes
 
vApp Networks
No
Networks and associated configurations are lost. Networks must be redefined and NICs attached.
NIC Assignment
(non-vApp network)
No
NICs must be reassigned.
Guest Customization Enabled
No
Checkbox is selected in target vCloud.
CPU Hot Add
No
 
Memory Hot Add
No
 
Synchronize Virtual Machine Time
No
 
Password Reset
Yes
 
Default Password
No
Defaults to blank field in UI.
Disk Bus Type
Yes
 
Network Adapter Type
No
Defaults to flexible.
Resource Allocation
Yes
When vApp is deployed to Reservation Pool virtual datacenter.
OVF Properties
Yes
Accessed through VMware Tools and used for scripting, fetching, and for post-configuration and provisioning.