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.

To find out if the new options are supported, use this command and check if the new options are present in the output:

$ virt-v2v -o kubevirt -oo '?'
Output options that can be used with -o kubevirt:

  -oo compressed      Compress the output file (used only with -of qcow2)
  -oo create=false    Do not create the output disks
  -oo disk=disk1      Specify filename of output disk (if used, must be
                        given once for each disk, else -os path is used)

The -os parameter is still required (as the location for the yaml file).