Solutions, whenever we have to go a vm disk up to a container that is different the exact same AHV Cluster.
For e.g. : we possibly may desire to go this VM Disk for a container with De-Dupliction Disabled. To relocate a digital machine’s disk to a new container for a passing fancy AHV group, following actions are needed:
Needs for the Move:
- Supply Container ID (in which the vmdisk is found initially)
- Destination Container ID (our target container regarding the cluster that is same
- VM Disk(s) UUID (UUID of every disk we have to move “acli vm.get ”)
- Power-off the VM
Overview of procedures:
- Determine the vmdisk_uuid of each and every disk that is virtual the VM.
- make certain the VM which is why the VMdisk we have been migrating is driven down.
- Utilize the Acropolis Image provider to clone the supply digital Disk(s) into Image(s) regarding the target container.
- Attach the disk through the Acropolis Image(s) which created in step three into the VM.
- Get rid of the VM disk this is certainly hosted from the initial container
- Optional: eliminate the VMdisk that is cloned image solutions
Detailed Procedures:
Why don’t we use the illustration of a VM named “EXAMPLE_VM”
we have to login up to a cvm and perform the after demand to have more information about “EXAMPLE_VM” :
Because of the above demand we are going to obtain the output that is following
From the aforementioned command you can view that the EXAMPLE_VM ‘ VM has 3 disks. The disks
on scsi.0 and scsi.2 are hosted on container with ID 8118 even though the disk on scsi.1 is on