Phub

Migrating VM Disk to A container that is different on

Migrating VM Disk to A container that is different on

There are occasions, whenever we need certainly to move a vm disk 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 some other container on a single AHV group, following actions are needed:

Needs for the Move:

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

Overview of procedures:

  • Determine the vmdisk_uuid of each and every disk that is virtual the VM.
  • Verify 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) in the target container.
  • Connect the disk through the Acropolis Image(s) which created in step three into the VM.
  • Eliminate the VM disk this is certainly hosted in the initial container
  • Optional: eliminate the VMdisk that is cloned image services

Detailed Procedures:

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

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

Utilizing the above demand we’ll obtain the after 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 although 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 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 > Power off

  • Step – 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 in to the preferred one:

Above command with no particulars:

  • Step – 4 : connect the disk

From the Acropolis Image created in step three towards 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 following settings:

Operation = “Clone from Image provider”

Bus Type = as required

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

Go through the Add key.

  • Move – 5 : getting rid of the original supply disk

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

This could be 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 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 in the “X” to get rid of.

If for a few explanation you simply cannot begin to see the “X” beside the image, you could get surrounding this by detatching 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 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 actions are needed:

Needs for the Move:

  • Supply Container ID (where in actuality the vmdisk is found initially)
  • Destination Container ID (our target pornhub container regarding the cluster that is same
  • VM Disk(s) UUID (UUID of each and every disk we must move that is“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 driven 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 to your VM.
  • Take away the VM disk that is hosted regarding the initial container
  • Optional: get rid of the cloned VMdisk from image solutions

Detailed Procedures:

Why don’t we just take the exemplory case 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 shall obtain the after output:

From the above mentioned 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 acli demand shell whenever logged on to your cvm plus it provides 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 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 in to the preferred one:

Above command without having the particulars:

  • Move – 4 : connect the disk

Through the Acropolis Image created in step three to your 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 provider”

Bus Type = as required

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

Click the Add switch.

  • Move – 5 : getting rid of the initial supply disk

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

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

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

  • Move – 6 : (Optional) get rid of the cloned vmdisk from image services

This is often done from Prism’s Image Configuration Window

Prism > Gear Icon > Image Configuration

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

If for a few good explanation you simply cannot begin 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 kind Image UUID

To delete the image:

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

This concludes disk moving on a solitary ahv group.