Exporting to RHEV data domain (similar to export domain), Expected something like: v2v ... -o rhev -os rhev.nfs:/data_domain --rhev-image-uuid <GUID> --rhev-vol-uuid <GUID> --rhev-vm-uuid <GUID> Unlike export domain, data domain is not needed to create the volume structure since the caller (RHEVM) will be responsible for that.
Not quite sure I understand the bug. Is there something virt-v2v should be doing which it doesn't do already?
Its a general RFE bug, Two main issues that v2v need to address: 1. not create any dir on data domain (in export domain it does create the directory structure) - maybe a new flag to indicate export/domain... 2. add estimated size to each disk when calling v2v with --no-copy
Just a note that in 1.27.43, there is a new -o vdsm mode, and all the --rhev* flags have been renamed to --vdsm* (but otherwise are unchanged). This is a development release so we're allowed to make significant changes to unreleased code like this.
In 1.27.45, the ovf:actual_size field is an estimate when --no-copy is used. https://github.com/libguestfs/libguestfs/commit/88dea548031db0eaccc08b63c4ee1e3644cd0e83
(In reply to Richard W.M. Jones from comment #3) > Just a note that in 1.27.43, there is a new -o vdsm mode, and > all the --rhev* flags have been renamed to --vdsm* (but otherwise > are unchanged). > > This is a development release so we're allowed to make significant > changes to unreleased code like this. I think --ovirt* would make more sense?
Pretty sure --vdsm* makes more sense, since these flags are only used when under the control of VDSM.