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
container ID 1795364.
Tip : You can drop in the command that is acli whenever logged on to your cvm also it offers tab conclusion.
- Action -1 : energy off the vm
Through the command line that is acli
nutanix@cvm$ acli vm.shutdown EXAMPLE_VM
From the Prism system :
Prism > VM > Table > Click on VM > energy off
- Move – 2 : Clone the vmdisk
First confirm the container names and particular ids:
nutanix@cvm$ ncli ctr ls >
VStore Name(s) : Source_Container
nutanix@cvm$ ctr that is ncli >
VStore Name(s) : Destnation_Container
- Step – 3 : Clone the vmdisk from initial container in to the preferred one:
Above command without having the particulars:
- Move – 4 : connect the disk
Through the Acropolis Image created in step three towards the VM.
This is done from Prism > VM > Table > click vm EXAMPLE_VM > modify.
Under Disks click on “Add New Disk” and use the following settings:
Procedure = “Clone from Image provider”
Coach Type = as required
IMAGE = choose the image that people recently cloned (SCSI1_EXAMPLE_VM as our instance)
Click the Add key.
- Step – 5 : Removing the source disk that is original
Eliminate the VM disk this is certainly hosted from the initial container
This could be done from Prism > VM > Table > click vm EXAMPLE_VM > modify.
Under Disks click in the “X” beside the disk hosted on the container that is non-desired.
- Move – 6 : (Optional) eliminate the vmdisk that is cloned image solutions
This could be done from Prism’s Image Configuration Window
Prism > Gear Icon > Image Configuration
Get the image (SCSI1_EXAMPLE_VM as our example) and then click from the “X” to get rid of.
If for a few reason you can not begin to see the “X” beside the image, you could get for this by eliminating the image through the CVM demand line:
To record the images:
Image title Image kind Image UUID
To delete the image:
nutanix@cvm$ acli image.delete 475106ad-9c2a-432a-afa8-f9073c76548c
This concludes disk moving for A ahv that is single group.
For e.g. : we possibly may like to go this VM Disk for a container with De-Dupliction Disabled. To relocate a digital machine’s disk to another 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 in the cluster that is same
- VM Disk(s) UUID (UUID of every disk we must go “acli vm.get ”)
- Power-off the VM
Overview of procedures:
- Determine the vmdisk_uuid of every digital disk on the VM.
- Make certain the VM which is why the VMdisk we have been migrating is driven down.
- Make use of the Acropolis Image provider to clone the supply virtual s that are disk( ukrainian dating into Image(s) from the target container.
- Connect the disk through the Acropolis Image(s) which created in Step 3 into the VM.
- Get rid of the VM disk this is certainly hosted from the initial container
- Optional: Remove the cloned VMdisk from image solutions
Detailed Procedures:
Let’s make the exemplory instance of a VM named “EXAMPLE_VM”
we have to login to a cvm and perform the after demand to have more information about “EXAMPLE_VM” :
Because of the above demand we’re going to have the output that is following
From the aforementioned command you can observe that the EXAMPLE_VM ‘ VM has 3 disks. The disks
on scsi.2 and scsi.0 are hosted on container with ID 8118 as the disk on scsi.1 is on
container ID 1795364.
Tip : You can drop in the command that is acli whenever logged on to your cvm also it provides tab conclusion.
- Action -1 : energy off the vm
Through the command line that is acli
nutanix@cvm$ vm that is acli EXAMPLE_VM
From the Prism system :
Prism > VM > Table > click VM > energy off
- Move – 2 : Clone the vmdisk
First confirm the container names and ids that are respective
nutanix@cvm$ ncli ctr ls >
VStore Name(s) : Source_Container
nutanix@cvm$ ctr that is ncli >
VStore Name(s) : Destnation_Container
- Move – 3 : Clone the vmdisk from initial container to the preferred one:
Above command with no details:
- Move – 4 : connect the disk
Through the Acropolis Image created in step three to your VM.
This is done from Prism > VM > Table > click vm EXAMPLE_VM > modify.
Under Disks click on “Add New Disk” and use the settings that are following
Operation = “Clone from Image provider”
Coach Type = as required
IMAGE = choose the image that individuals recently cloned (SCSI1_EXAMPLE_VM as our instance)
Click the Add key.
- Move – 5 : eliminating the initial source disk
Eliminate the VM disk that is hosted in the container that is original
This is often done from Prism > VM > Table > Click on vm EXAMPLE_VM > modify.
Under Disks click regarding the “X” beside the disk hosted regarding the container that is non-desired.
- Move – 6 : (Optional) get rid of the cloned vmdisk from image solutions
This is done from Prism’s Image Configuration Window
Prism > Gear Icon > Image Configuration
Get the image (SCSI1_EXAMPLE_VM as our instance) and then click from the “X” to eliminate.
If for many reason you simply cannot understand “X” beside the image, you may get for this by eliminating the image through the CVM demand line:
To record the pictures:
Image title Image kind Image UUID
To delete the image:
nutanix@cvm$ acli image.delete 475106ad-9c2a-432a-afa8-f9073c76548c
This concludes disk moving on A ahv that is single group.
