It is strongly recommended that {project-first} should be used with the VMware Virtual Disk Development Kit (VDDK) SDK when transferring virtual disks from VMware vSphere.
Note
|
Creating a VDDK image, although optional, is highly recommended. Using {project-short} without VDDK is not recommended and could result in significantly lower migration speeds. |
To make use of this feature, you download the VMware Virtual Disk Development Kit (VDDK), build a VDDK image, and push the VDDK image to your image registry.
The VDDK package contains symbolic links, therefore, the procedure of creating a VDDK image must be performed on a file system that preserves symbolic links (symlinks).
Note
|
Storing the VDDK image in a public registry might violate the VMware license terms. |
-
podman
installed. -
You are working on a file system that preserves symbolic links (symlinks).
-
If you are using an external registry, {virt} must be able to access it.
-
Create and navigate to a temporary directory:
$ mkdir /tmp/<dir_name> && cd /tmp/<dir_name>
-
In a browser, navigate to the VMware VDDK version 8 download page.
-
Select version 8.0.1 and click Download.
Note
|
In order to migrate to {virt} 4.12, download VDDK version 7.0.3.2 from the VMware VDDK version 7 download page. |
-
Save the VDDK archive file in the temporary directory.
-
Extract the VDDK archive:
$ tar -xzf VMware-vix-disklib-<version>.x86_64.tar.gz
-
Create a
Dockerfile
:$ cat > Dockerfile <<EOF FROM registry.access.redhat.com/ubi8/ubi-minimal USER 1001 COPY vmware-vix-disklib-distrib /vmware-vix-disklib-distrib RUN mkdir -p /opt ENTRYPOINT ["cp", "-r", "/vmware-vix-disklib-distrib", "/opt"] EOF
-
Build the VDDK image:
$ podman build . -t <registry_route_or_server_path>/vddk:<tag>
-
Push the VDDK image to the registry:
$ podman push <registry_route_or_server_path>/vddk:<tag>
-
Ensure that the image is accessible to your {virt} environment.