Add VDDK support in VMware to KVM migration#640
Add VDDK support in VMware to KVM migration#640harikrishna-patnala wants to merge 1 commit intoapache:4.22from
Conversation
There was a problem hiding this comment.
Pull request overview
Adds administrator documentation for an optimized VMware-to-KVM migration path using virt-v2v “vpx” mode with VMware VDDK, explaining prerequisites and host/agent configuration needed to enable block-streaming conversions (avoiding OVF export).
Changes:
- Document VDDK-based streaming workflow vs. the existing OVF-based conversion flow.
- Add KVM host preparation steps (packages, libguestfs backend, VDDK install, EL9 symlink).
- Document relevant CloudStack agent properties for VDDK-based conversion and operational recommendations.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| .. note:: 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. | ||
|
|
There was a problem hiding this comment.
The .. note:: directive at line 144 is immediately followed by unindented text without a blank line. In reStructuredText this commonly triggers a docutils/Sphinx warning ("Explicit markup ends without a blank line") and the following sentences won't be part of the note. Add a blank line after the note (and indent the following lines if they’re intended to be included in the note block).
| .. note:: 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. | |
| .. note:: | |
| 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. |
| This reduces disk I/O amplification, eliminates temporary staging storage, and shortens end-to-end migration time. | ||
|
|
||
| .. note:: 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. |
There was a problem hiding this comment.
Sentence reads incomplete/awkward: “the traditional OVF-based method remains supported for environments.” Consider clarifying what environments this refers to (e.g., “...supported for environments where VDDK cannot be used/installed”).
| Along with the new VDDK-based conversion method the traditional OVF-based method remains supported for environments. | |
| Along with the new VDDK-based conversion method, the traditional OVF-based method remains supported for environments where VDDK cannot be used or installed. |
CloudStack supports an optimized VMware-to-KVM migration path using virt-v2v in vpx input mode combined with
VMware's Virtual Disk Development Kit (VDDK). This method eliminates the OVF export phase entirely and streams
disk blocks directly from the source hypervisor into the conversion pipeline, resulting in significantly faster
migration times.
Related PR apache/cloudstack#12970
📚 Documentation preview 📚: https://cloudstack-documentation--640.org.readthedocs.build/en/640/