-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-10.1
-
None
-
virt-v2v-2.8.1-8.el10
-
No
-
Moderate
-
rhel-virt-tools
-
None
-
False
-
False
-
-
None
-
None
-
Pass
-
Automated
-
Unspecified
-
Unspecified
-
Unspecified
-
None
The current -o kubevirt mode is quite inflexible. You can only specify where to put the disks using -os dir parameter, and it creates disks called name-sda, name-sdb etc. To use this MTV needs to create a directory with symlinks to the actual output disks.
Refer to the kubevirt section of https://libguestfs.org/virt-v2v.1.html
What would be more useful to MTV would be to allow the locations of the disks to be specified. A rough outline of this feature would be to use:
virt-v2v ... -o kubevirt \
-oo create=false \
-oo disk=/path/to/first/disk.img \
-oo disk=/path/to/second/disk.img
with one parameter required for each disk.
Importantly virt-v2v would assume these disks are precreated and not try to recreate them (as it does at the moment).
We'd keep the old -os method for compatibility in case no disk parameters were specified.
- is depended on by
-
MTV-2850 Allow -o kubevirt disks to be specified
-
- New
-
- links to
-
RHBA-2025:149949
virt-v2v bug fix and enhancement update