Skip to content

Commit 108a9a7

Browse files
committed
Clarify VDDK 8 recommendation for VMware imports
1 parent 41be3ba commit 108a9a7

1 file changed

Lines changed: 9 additions & 21 deletions

File tree

source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst

Lines changed: 9 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -186,9 +186,11 @@ Ubuntu:
186186
Download the VDDK Linux tarball from Broadcom's VMware Virtual Disk Development Kit page:
187187
https://developer.broadcom.com/sdks/vmware-virtual-disk-development-kit-vddk/
188188

189-
For EL-based KVM hosts, use the latest available VDDK 8.x Linux tarball on EL8 hosts and the latest available
190-
VDDK 9.x Linux tarball on EL9 hosts. Ubuntu hosts should use the Linux tarball compatible with the installed
191-
``virt-v2v`` and ``nbdkit`` packages; validate this combination before enabling VDDK-based migrations in production.
189+
Use the latest available VDDK 8.x Linux tarball for all supported KVM conversion hosts, including EL8, EL9,
190+
Ubuntu 22.04, and Ubuntu 24.04 hosts. VDDK 8.x covers vSphere 7 and vSphere 8 environments and is the recommended
191+
stable choice for most deployments. Do not use VDDK 9.x unless the source environment is vSphere 9 and the
192+
``virt-v2v`` and ``nbdkit`` package combination has been explicitly validated, because VDDK 9.x is targeted at
193+
vSphere 9 and is not the expected default for vSphere 7 or vSphere 8 environments.
192194

193195
Extract the tarball under a consistent location such as the example below. The CloudStack agent auto-detects a valid
194196
``vmware-vix-disklib-distrib`` directory when it can find one on the host. If VDDK is extracted elsewhere, or if the
@@ -199,39 +201,25 @@ host has more than one VDDK installation and a specific one should be used, conf
199201

200202
mkdir -p /opt/vmware-vddk
201203

202-
# EL8 example
204+
# VDDK 8.x example for EL8, EL9, Ubuntu 22.04, and Ubuntu 24.04 hosts
203205
tar -xf VMware-vix-disklib-8*.tar.gz -C /opt/vmware-vddk
204206

205-
# EL9 example
206-
tar -xf VMware-vix-disklib-9*.tar.gz -C /opt/vmware-vddk
207-
208207
Expected layout after extraction::
209208

210209
/opt/vmware-vddk/vmware-vix-disklib-distrib/
211210
lib64/
212211
include/
213212
bin64/
214213

215-
**Step 3: Add EL9 compatibility symlink (when using VDDK 9)**
216-
217-
On EL9 distributions, virt-v2v may expect ``libvixDiskLib.so.8``. Create this compatibility symlink:
218-
219-
::
220-
221-
cd /opt/vmware-vddk/vmware-vix-disklib-distrib/lib64
222-
ln -s libvixDiskLib.so.9 libvixDiskLib.so.8
223-
224-
.. note:: This compatibility symlink is commonly required on RHEL 9, Rocky Linux 9, and Alma Linux 9.
225-
226-
**Step 4: Verify host setup**
214+
**Step 3: Verify host setup**
227215

228216
::
229217

230218
ls /opt/vmware-vddk/vmware-vix-disklib-distrib/lib64/libvixDiskLib.so.8
231219
virt-v2v --version
232220
nbdkit --version
233221

234-
**Step 5: Restart the CloudStack agent**
222+
**Step 4: Restart the CloudStack agent**
235223

236224
Restart the CloudStack agent service so it detects the installed VDDK library and makes it available in the UI:
237225

@@ -241,7 +229,7 @@ Restart the CloudStack agent service so it detects the installed VDDK library an
241229

242230
After the agent restarts, verify that VDDK installation was detected by checking the host details in the CloudStack UI.
243231

244-
**Step 6: Verify required network and firewall access**
232+
**Step 5: Verify required network and firewall access**
245233

246234
Allow the following ports through any firewall or network security controls between the KVM conversion host and the
247235
VMware endpoints:

0 commit comments

Comments
 (0)