diff --git a/source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst b/source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst index 655b8e0629..f6f0d79939 100644 --- a/source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst +++ b/source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst @@ -19,19 +19,22 @@ Requirements on the KVM hosts ----------------------------- The CloudStack agent does not install the virt-v2v binary as a dependency. The virt-v2v binary must be installed manually on KVM hosts, or the migration will fail. +Newer versions of virt-v2v - v2.7.x on EL9, v2.4.x on Ubuntu 24.04 - are strongly advised. Older version of virt-v2v - e.g. v1.4.x should be avoided. The virt-v2v output (progress) is logged in the CloudStack agent logs, to help administrators track the progress on the Instance conversion processes. The verbose mode for virt-v2v can be enabled by adding the following line to /etc/cloudstack/agent/agent.properties and restart cloudstack-agent: +EL variants: + :: - dnf install virt-v2v + dnf install virt-v2v / apt install virt-v2v echo "virtv2v.verbose.enabled=true" >> /etc/cloudstack/agent/agent.properties systemctl restart cloudstack-agent -Installing virt-v2v on Ubuntu KVM hosts does not install nbdkit which is required in the conversion of VMware VCenter guests. To install it, please execute: +Installing virt-v2v on Ubuntu KVM hosts does not install nbdkit, which is required in the conversion of VMware VCenter guests. To install it, please execute: :: @@ -54,45 +57,45 @@ Ubuntu 22.04 LTS, 24.04 LTS Importing Windows VMs from VMware requires installing the virtio drivers for Windows on the hypervisor hosts for the virt-v2v conversion. +The Fedora-provided ``virtio-win`` RPM installs the drivers under ``/usr/share/virtio-win``, which is one of virt-v2v's +default search paths. -On (RH)EL hosts: +On EL-based hosts, including RHEL, Oracle Linux, Rocky Linux and Alma Linux, install the Fedora-provided RPM directly. :: - yum install virtio-win - -You can also install the RPM manually from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.noarch.rpm + dnf install -y https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.noarch.rpm + rpm -qa | grep -i virtio-win + ls -l /usr/share/virtio-win -For Debian-based distributions: -Ubuntu don’t seem to ship the virtio-win package with drivers, which causes virt-v2v not to convert the VMWare Windows guests to virtio profiles. This could result in slow IDE drives and Intel E1000 NICs. As a workaround, we can follow the below steps to install the package from the RPM on all KVM hosts running the virt-v2v: +For Debian-based distributions (alien is needed for conversion of .rpm to .deb pavckage: :: - apt install virtio-win (if the package is not available, then manual steps will be required to install the virtio drivers for windows) - - wget https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.noarch.rpm - - # install “alien” which can convert rpms to debs + wget -O virtio-win.noarch.rpm https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.noarch.rpm apt -y install alien - - # the conversion, can take a while alien -d virtio-win.noarch.rpm - # install the resulting deb dpkg -i virtio-win*.deb + ls -l /usr/share/virtio-win -In addition to this, we need to install the below package as well to avoid the error “virt-v2v: error: One of rhsrvany.exe or pvvxsvc.exe is missing in /usr/share/virt-tools“. - +On some distros, the Windows helper binary "rhsrvany.exe" which is used for Windows firstboot scripts and some other actions might be missing. +To avoid virt-v2v error like ``virt-v2v: error: One of rhsrvany.exe or pvvxsvc.exe is missing in /usr/share/virt-tools`` - check if the file exists (it's actually a symbolic link): +``ls -la /usr/share/virt-tools/rhsrvany.exe`` +If the file does not exist - proceed with the commands below (EL8 and EL9 hosts usually already have this in place, so are not affected) :: - - wget -nd -O srvany.rpm https://kojipkgs.fedoraproject.org//packages/mingw-srvany/1.1/4.fc38/noarch/mingw32-srvany-1.1-4.fc38.noarch.rpm - + + Ubuntu-based distros + wget -nd -O srvany.rpm https://kojipkgs.fedoraproject.org/packages/mingw-srvany/1.1/4.fc38/noarch/mingw32-srvany-1.1-4.fc38.noarch.rpm + [ -f /usr/bin/alien ] || apt -y install alien alien -d srvany.rpm - dpkg -i *srvany*.deb - + mkdir -p /usr/share/virt-tools + ln -sf /usr/i686-w64-mingw32/sys-root/mingw/bin/rhsrvany.exe /usr/share/virt-tools/rhsrvany.exe + ln -sf /usr/i686-w64-mingw32/sys-root/mingw/bin/pnp_wait.exe /usr/share/virt-tools/pnp_wait.exe + ls -la /usr/share/virt-tools/rhsrvany.exe The OVF tool (ovftool) must be installed on the destination KVM hosts if the hosts should export VM files (OVF) from vCenter. If not, the management server exports them (the management server doesn't require ovftool installed). @@ -146,6 +149,7 @@ This reduces disk I/O amplification, eliminates temporary staging storage, and s CloudStack does not distribute VDDK, operators must download it separately. Along with the new VDDK-based conversion method the traditional OVF-based method remains supported for environments. Operators can choose the conversion method on a per-migration basis in the UI import wizard. + Host Prerequisites for VDDK-based Conversion ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -181,14 +185,26 @@ Ubuntu: **Step 2: Download and install VDDK** -Download the VDDK tarball and extract it on the KVM host. The CloudStack agent will detect the VDDK library -directory from the extracted package layout or it can also be configured explicitly via the ``vddk.lib.dir`` -property in ``/etc/cloudstack/agent/agent.properties``. +Download the VDDK Linux tarball from Broadcom's VMware Virtual Disk Development Kit page: +https://developer.broadcom.com/sdks/vmware-virtual-disk-development-kit-vddk/ + +Use the latest available VDDK 8.x Linux tarball for all supported KVM conversion hosts, including EL8, EL9, +Ubuntu 22.04, and Ubuntu 24.04 hosts. VDDK 8.x covers vSphere 7 and vSphere 8 environments and is the recommended +stable choice for most deployments. Do not use VDDK 9.x unless the source environment is vSphere 9 and the +``virt-v2v`` and ``nbdkit`` package combination has been explicitly validated, because VDDK 9.x is targeted at +vSphere 9 and is not the expected default for vSphere 7 or vSphere 8 environments. + +Extract the tarball under a consistent location such as the example below. The CloudStack agent auto-detects a valid +``vmware-vix-disklib-distrib`` directory when it can find one on the host. If VDDK is extracted elsewhere, or if the +host has more than one VDDK installation and a specific one should be used, configure the directory explicitly with the +``vddk.lib.dir`` property in ``/etc/cloudstack/agent/agent.properties``. :: mkdir -p /opt/vmware-vddk - tar -xf VMware-vix-disklib-9*.tar.gz -C /opt/vmware-vddk + + # VDDK 8.x example for EL8, EL9, Ubuntu 22.04, and Ubuntu 24.04 hosts + tar -xf VMware-vix-disklib-8*.tar.gz -C /opt/vmware-vddk Expected layout after extraction:: @@ -197,18 +213,7 @@ Expected layout after extraction:: include/ bin64/ -**Step 3: Add EL9 compatibility symlink (when using VDDK 9)** - -On EL9 distributions, virt-v2v may expect ``libvixDiskLib.so.8``. Create this compatibility symlink: - -:: - - cd /opt/vmware-vddk/vmware-vix-disklib-distrib/lib64 - ln -s libvixDiskLib.so.9 libvixDiskLib.so.8 - -.. note:: This compatibility symlink is commonly required on RHEL 9, Rocky Linux 9, and Alma Linux 9. - -**Step 4: Verify host setup** +**Step 3: Verify host setup** :: @@ -216,7 +221,7 @@ On EL9 distributions, virt-v2v may expect ``libvixDiskLib.so.8``. Create this co virt-v2v --version nbdkit --version -**Step 5: Restart the CloudStack agent** +**Step 4: Restart the CloudStack agent** Restart the CloudStack agent service so it detects the installed VDDK library and makes it available in the UI: @@ -226,7 +231,7 @@ Restart the CloudStack agent service so it detects the installed VDDK library an After the agent restarts, verify that VDDK installation was detected by checking the host details in the CloudStack UI. -**Step 6: Verify required network and firewall access** +**Step 5: Verify required network and firewall access** Allow the following ports through any firewall or network security controls between the KVM conversion host and the VMware endpoints: