PCA : How To Migrate a VMWare Guest Having Vdisk in VMDK Format To PCA / OVM Environment And Deal With VERR_VD_VMDK_INVALID

Asset ID:	1-71-2143737.1
Update Date:	2017-04-19
Keywords:

Solution Type Technical Instruction Sure

Solution 2143737.1 : PCA : How To Migrate a VMWare Guest Having Vdisk in VMDK Format To PCA / OVM Environment And Deal With VERR_VD_VMDK_INVALID_FORMAT

Applies to:

Private Cloud Appliance - Version 2.1.1 to 2.1.1 [Release 2.0]
Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle VM - Version 3.2.9 and later
Information in this document applies to any platform.

Goal

This document describes a workaround on how you can migrate your VMWare guests having vdisks in VMDK format to PCA or OVM environment because as of now vbox-img doesn't support the conversion of VMDK to .img format and it gives below error:

(05/25/2016 09:14:29:147 AM) Async operation failed on server: ovcacn08r1. Object: cfgFile_0004fb00001400001d8575c9b5758c53, PID: 14414, Server error message: Command failed: cmds ([['cat', u'/OVS/Repositories/0004fb0000030000880a099f15faaf45/Assemblies/111f6bc041/unpacked/APLSEPLAN01.dsiaf.rn.gov.br-disk1.vmdk'], ['vbox-img', 'convert', '--stdin', '--srcformat', 'vmdk', '--dstfilename', '/OVS/Repositories/0004fb0000030000880a099f15faaf45/VirtualDisks/23cd58d183a4441f8f725d6755620fb9.img', '--dstformat', 'raw']]) output file (None) success_return_codes (0,)) rc (1) stdout () stderr (Converting image "stdin" with size 137303707648 bytes (130944MB)... vbox-img: error: Error while copying the image: VERR_VD_VMDK_INVALID_FORMAT )

And even manual conversion ends with the same error:

[Root @ ovcamn06r1 APLSEPLAN01.dsiaf.rn.gov.br] # vbox-img convert --srcfilename APLSEPLAN01.dsiaf.rn.gov.br-disk1.vmdk --srcformat VMDK --dstfilename APLSEPLAN01.dsiaf.rn.gov. br-disk1.img --dstformat RAW
Converting image "APLSEPLAN01.dsiaf.rn.gov.br-disk1.vmdk" with size 137 303 707 648 bytes (130944MB) ...
vbox-img: error: Error while copying the image: VERR_VD_VMDK_INVALID_FORMAT

Solution

Thus, as a workaround you can follow below steps:

The QEMU /usr/sbin/qemu-img utility is required to convert VMware disks into raw image form for use by Oracle VM. The qemu-img utility is provided by the xen-tools package but on ODA VM the qemu-img is not available. There is the qemu-img-xen but unfortunately it's not working properly with recent vmdk files.

So, you can install the qemu-img utility on any of your spare Oracle Linux machine which is registered with ULN directly by using "yum install" command as shown below:

1) #yum install qemu-img

Now, you need to copy your VMDK disk to the server where you have installed qemu-img utility from above step and use below command to convert the vdisk to .img format:

2) #qemu-img convert -f vmdk OL6_64-bit-xen.vmdk -O raw OL6_64-bit-xen.img

# qemu-img convert OL6_64-bit-xen.vmdk -O img OL6_64-bit-xen.img

# ls -l *.img
-rw------- 1 root root 10737418240 Jan 31 16:37 OL6_64-bit-xen.img

Once the conversion is successful then you can copy the .img format vdisk to the repository where you wanted to create a VM:

3) #scp OL6_64-bit-xen.img <user>@<hostname>:/OVS/Repositories/<repouuid>/VirtualDisks/OL6_64

eg:#scp OL6_64-bit-xen.img root@x.x.x.x:/OVS/Repositories/0004fb0000030000afa1a77b545115bc/VirtualDisks

Once you have copied the vdisk, then you can try to refresh the repository via OVMM GUI and then create a VM as usual. When you reach to the disks section, there you need to use the 'search' button and select the vidsks which you have just copied and finish the VM creation task. After this you should be good to start your guest VM.

Attachments

This solution has no attachment