Solutions, as soon as we want to go a vm disk up to a various container on exactly the same AHV Cluster.

For e.g. : we might would you like to go this VM Disk for a container with De-Dupliction Disabled. To relocate a digital machine’s disk to some other container on a single AHV group, after steps are needed:

Demands for the Move:

• Supply Container ID (where in actuality the vmdisk is situated initially)
• Destination Container ID (our target container regarding the same group)
• VM Disk(s) UUID (UUID of each and every disk we have to go that is“acli vm.get
• Power-off the VM

Overview of procedures:

• Determine the vmdisk_uuid of every disk that is virtual the VM.
• Ensure that the VM which is why the VMdisk we have been migrating is driven down.
• Utilize the Acropolis Image provider to clone the supply virtual s that are disk( into Image(s) regarding the target container.
• Connect the disk through the Acropolis Image(s) which created in step three towards the VM.
• Get rid of the VM disk this is certainly hosted in the container that is original
• Optional: get rid of the VMdisk that is cloned image services

Detailed Procedures:

Why don’t we use the exemplory case of a VM named “EXAMPLE_VM”

we must login to a cvm and execute the command that is following have more information about “EXAMPLE_VM” :

Because of the above command we are going to obtain the output that is following

From the above mentioned command you can see that the EXAMPLE_VM ‘ VM has 3 disks. The disks

on scsi.2 and scsi.0 are hosted on container with ID 8118 whilst the disk on scsi.1 is on

container ID 1795364.

Tip : You can drop in the acli demand shell when logged on to your cvm plus it provides tab conclusion.

• Action -1 : energy off the vm

Through the acli demand line :

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$ ctr that is ncli >

VStore Name(s) : Source_Container

nutanix@cvm$ ncli ctr ls >

VStore Name(s) : Destnation_Container

• Move – 3 : Clone the vmdisk from original container to the preferred one:

Above command without having the particulars:

• Move – 4 : connect the disk

Through the Acropolis Image created in step three into the VM.

This is often done from Prism > VM > Table > click vm EXAMPLE_VM > modify.

Under Disks click on “Add New Disk” and use the settings that are following

Procedure = “Clone from Image Service”

Coach Type = as required

IMAGE = find the image that people recently cloned (SCSI1_EXAMPLE_VM as our instance)

Go through the Add switch.

• Move – 5 : getting rid of the source disk that is original

Take away the VM disk that is hosted regarding the container that is original

This is done from Prism > VM > Table > click vm EXAMPLE_VM > modify.

Under Disks click in the “X” next to the disk hosted regarding the non-desired container.

• Move – 6 : (Optional) eliminate the vmdisk that is cloned image services

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 good explanation you can’t look at “X” beside the image, you will get surrounding 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 for A ahv that is single group.

For e.g. : we might desire to go this VM Disk on a container with De-Dupliction Disabled. To relocate a machine’s that is virtual to another container for a passing fancy AHV group, after actions are expected:

Demands for the Move:

• Supply Container ID (where in actuality the vmdisk is found initially)
• Destination Container ID (our target container in the exact same group)
• VM Disk(s) UUID (UUID of each and every disk we have to go “acli vm.get ”)
• Power-off the VM

Overview of procedures:

• Determine the vmdisk_uuid of every disk that is virtual the VM.
• Make certain the VM for which the VMdisk we have been migrating is driven down.
• Make use of the Acropolis Image provider to clone the supply digital Disk(s) into Image(s) from the target container.
• Connect the disk through the Acropolis Image(s) which created in step three to your VM.
• Take away the VM disk this is certainly hosted regarding the initial container
• Optional: eliminate the cloned VMdisk from image solutions

Detailed Procedures:

Why don’t we simply take the exemplory case of a VM named “EXAMPLE_VM”

we have to login up to a cvm and perform the command that is following have more information about “EXAMPLE_VM” :

Because of the above demand we shall 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.2 and scsi.0 are hosted on container with ID 8118 whilst the disk on scsi.1 is on

container ID 1795364.

Tip : You can drop regarding the acli demand shell whenever logged on to your cvm and it also offers tab conclusion.

• Step -1 : Power 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 > Power off

latin dating sites
• 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

• Move – 3 : Clone the vmdisk from initial container to the preferred one:

Above command with no particulars:

• Step – 4 : Attach the disk

Through the Acropolis Image created in step three into the VM.

This is often done from Prism > VM > Table > click vm EXAMPLE_VM > modify.

Under Disks click on “Add New Disk” and employ the settings that are following

Procedure = “Clone from Image provider”

Bus Type = as required

IMAGE = find the image that people recently cloned (SCSI1_EXAMPLE_VM as our instance)

Click the Add button.

• Move – 5 : Removing the initial supply disk

Get rid of the VM disk this is certainly hosted in the container that is original

This is often done from Prism > VM > Table > click vm EXAMPLE_VM > modify.

Under Disks click regarding the “X” beside the disk hosted regarding the non-desired container.

• Move – 6 : (Optional) eliminate the cloned vmdisk from image solutions

This could be done from Prism’s Image Configuration Window

Prism > Gear Icon > Image Configuration

Discover the image (SCSI1_EXAMPLE_VM as our example) and then click regarding the “X” to remove.

If for a few good explanation you cannot start to see the “X” beside the image, you may get surrounding this by detatching the image through the CVM demand line:

To record the pictures:

Image title Image type Image UUID

To delete the image:

nutanix@cvm$ acli image.delete 475106ad-9c2a-432a-afa8-f9073c76548c

This concludes disk moving for a solitary ahv group.