Migrating VM Disk to A container that is different on

Migrating VM Disk to A container that is different on

Solutions, once we have to move a vm disk up to a container that is different the exact same AHV Cluster.

For e.g. : we possibly may like to move this VM Disk on a container with De-Dupliction Disabled. To relocate a digital machine’s disk to a new container on a single AHV group, after actions are needed:

Demands for the Move:

  • Supply Container ID (where in fact the vmdisk is situated originally)
  • Destination Container ID (our target container in the cluster that is same
  • VM Disk(s) UUID (UUID of each disk we must go “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 powered down.
  • Utilize the Acropolis Image provider to clone the supply digital Disk(s) into Image(s) regarding the target container.
  • Connect the disk through the Acropolis Image(s) which created in step three into the VM.
  • Get rid of the VM disk that is hosted in the container that is original
  • Optional: eliminate the VMdisk that is cloned image solutions

Detailed Procedures:

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

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

With all the above demand we’ll have the after output:

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 although the disk on scsi.1 is on

container ID 1795364.

Tip : You can drop regarding the acli demand shell when 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 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 towards the VM.

This is 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”

Coach Type = as needed

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

Go through the Add key.

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

Eliminate the VM disk this is certainly hosted in the container that is original

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

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

  • Move – 6 : (Optional) get rid of the vmdisk that is cloned image solutions

This is done from Prism’s Image Configuration Window

Prism > Gear Icon > Image Configuration

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

If for some explanation you can’t start to see the “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 relocation on a solitary ahv group.

For e.g. : we might 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, after actions are needed:

Requirements for the Move:

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

Overview of procedures:

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

Detailed Procedures:

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

we must login up to a cvm and execute the after demand to have more information about “EXAMPLE_VM” :

Utilizing the above demand we are going to obtain the following output:

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 from the acli demand shell whenever logged on to your cvm also it provides tab conclusion.

  • Step -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 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 initial container 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 could be done from Prism > VM > Table > click vm EXAMPLE_VM > Update.

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

Procedure = “Clone from Image provider”

Coach Type = as required

IMAGE = choose the image we recently cloned (SCSI1_EXAMPLE_VM as our instance)

Go through the Add key.

  • Move – 5 : eliminating the source disk that is original

Eliminate the VM disk that is hosted regarding the initial container

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 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 explanation you simply cannot look at “X” beside the image, you will get for this by detatching the image through the CVM demand line:

To list 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.

Author: essem

Essem Engineers is a leading and fast growing world-class manufacturer and supplier of hydraulically powered machines. Maximizing our industry rich experience of many years, we have gained superiority in manufacturing and supplying wide range of hydraulically powered machineries including hydraulic cylinders, broaching machines, hydraulic presses, Hydraulic scissor lifts, AC/DC power packs, etc.

Leave a Reply

Your email address will not be published. Required fields are marked *