Resetting the Virtual Machine Root Volume on Reboot
97
• When scaling memory or CPU for a Linux VM on VMware, you might need to run scripts in addition
to the other steps mentioned above. For more information, see Hot adding memory in Linux
(1012764)2 in the VMware Knowledge Base.
• (VMware) If resources are not available on the current host, scaling up will fail on VMware because
of a known issue where CloudPlatform and vCenter calculate the available capacity differently. For
more information, see https://issues.apache.org/jira/browse/CLOUDSTACK-1809.
• On VMs running Linux 64-bit and Windows 7 32-bit operating systems, if the VM is initially assigned
a RAM of less than 3 GB, it can be dynamically scaled up to 3 GB, but not more. This is due to a
known issue with these operating systems, which will freeze if an attempt is made to dynamically
scale from less than 3 GB to more than 3 GB.
11.12. Resetting the Virtual Machine Root Volume onReboot
For secure environments, and to ensure that VM state is not persisted across reboots, you can reset
the root disk. For more information, see Section 14.4.7, “Reset VM to New Root Disk on Reboot”.
11.13. Moving VMs Between Hosts (Manual Live Migration)
The CloudPlatform administrator can move a running VM from one host to another without interrupting
service to users or going into maintenance mode. This is called manual live migration, and can be
done under the following conditions:
• The root administrator is logged in. Domain admins and users can not perform manual live migration
of VMs.
• The VM is running. Stopped VMs can not be live migrated.
• The destination host must have enough available capacity. If not, the VM will remain in the
"migrating" state until memory becomes available.
• (KVM) The VM must not be using local disk storage. (On XenServer and VMware, VM live migration
with local disk is enabled by CloudPlatform support for XenMotion and vMotion.)
• (KVM) The destination host must be in the same cluster as the original host. (On XenServer and
VMware, VM live migration from one cluster to another is enabled by CloudPlatform support for
XenMotion and vMotion.)
• (OVM) If the VM is running on the OVM hypervisor, it must not have an ISO attached. Live migration
of a VM with attached ISO is not supported in OVM.
To manually live migrate a virtual machine:
1. Log in to the CloudPlatform UI as a user or admin.
2. In the left navigation, click Instances.
3. Choose the VM that you want to migrate.
4. Click the Migrate Instance button.
5. From the list of suitable hosts, choose the one to which you want to move the VM.