Migrating VM Disk to a various container on ahv

Migrating VM Disk to a various container on ahv

Migrating VM Disk to a various container on ahv

There are occasions, as soon as we have to go a vm disk up to a container that is different exactly the 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 machine’s that is virtual to another container on a single AHV group, after actions are expected:

Demands for the Move:

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

Summary of procedures:

  • Determine the vmdisk_uuid of each and every digital disk on the VM.
  • Ensure that 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 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.
  • Eliminate the VM disk this is certainly hosted regarding the container that is original
  • Optional: eliminate the VMdisk that is cloned image solutions

Detailed Procedures:

Why don’t we make the exemplory case of a VM named «EXAMPLE_VM»

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

Utilizing the above demand we shall have 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 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 plus 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 on VM > energy off

  • Move – 2 : Clone the vmdisk

First confirm the container names and particular ids:

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 details:

  • Move – 4 : connect the disk

Through the Acropolis Image created in step three to your VM.

This could be 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»

Coach Type = as required

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

Click the Add switch.

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

Take away the VM disk this is certainly hosted in 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 regarding the container that is non-desired.

  • Move – 6 : (Optional) Remove the vmdisk that is cloned 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 instance) and then click in the «X» to eliminate.

If for many good explanation you can not start to see the «X» beside the image, you will get surrounding this by detatching the image through the CVM demand line:

To record the pictures:

Image name 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 cluster.

For e.g. : we possibly may wish to go 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 expected:

Demands for the Move:

  • Supply Container ID (where in fact the vmdisk is based initially)
  • pornhub

  • Destination Container ID (our target container regarding the cluster that is same
  • VM Disk(s) UUID (UUID of each and 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 digital disk on the VM.
  • Make certain the VM which is why the VMdisk we have been migrating is driven down.
  • Utilize the Acropolis Image Service 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 into the VM.
  • Eliminate the VM disk that is hosted regarding the container that is original
  • Optional: get rid of the VMdisk that is cloned image solutions

Detailed Procedures:

Why don’t we use 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” :

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

From the above mentioned 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 on the acli demand shell whenever logged on to the cvm and it also 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$ ncli ctr ls >

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 details:

  • Step – 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 = find the image that people recently cloned (SCSI1_EXAMPLE_VM as our instance)

Click on the Add switch.

  • Step – 5 : eliminating the initial supply disk

Take away the VM disk that is hosted regarding 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 from the non-desired container.

  • 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 instance) and then click regarding the «X» to eliminate.

If for a few explanation you simply can’t look at «X» beside the image, you will 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 relocation on A ahv that is single group.

Share this post

Deja una respuesta

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *