search for: b2face339

Updates commit 1d38216d20141cef9ce83ca4ddbe9c79f5da4f39. --- v2v/virt-v2v.pod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index d39609cf8..b2face339 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -126,7 +126,7 @@ a local file. virt-v2v \ -i vmx -it ssh \ - "root@esxi.example.com/vmfs/volumes/datastore1/guest/guest.vmx" \ + "ssh://root@esxi.example.com/vmfs/volumes/datastore1/guest/guest.vmx" \ -o loc...

...f-output $d/12345678-1234-1234-1234-123456789abc/master/vms/VM \ - --vdsm-compat=1.1 + --vdsm-compat=1.1 \ + --vdsm-fixed-ovf # Test the OVF metadata was created. test -f $d/12345678-1234-1234-1234-123456789abc/master/vms/VM/VM.ovf diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index b2face339..9a047d390 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -759,6 +759,13 @@ hex digit can be C<0-9> or C<a-f>), conforming to S<OSF DCE 1.1>. These options can only be used with I<-o vdsm>. +=item B<--vdsm-fixed-ovf> + +OVF generated for RHV contains some...

...") (Printexc.to_string exn) in if uri.Xml.uri_scheme <> None && uri.Xml.uri_scheme <> Some "ssh" then error (f_"vmx URI start with ‘ssh://...’"); if uri.Xml.uri_server = None then diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index b2face339..4179245d6 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1438,10 +1438,7 @@ authorized_keys. When using the SSH input transport you must specify a remote C<ssh://...> URI pointing to the VMX file. A typical URI looks like: - ssh://root@esxi.example.com/vmfs/volumes/datastore1/...

The main reason for creating different OVF is that it can be used to create VM by oVirt REST API. The RHV export domain flavor cannot be used that way. Tomáš Golembiovský (3): v2v: tests: check generated OVF v2v: ovf: Create OVF more aligned with the standard v2v: vdsm: add --vdsm-fixed-ovf option v2v/cmdline.ml | 5 ++ v2v/create_ovf.ml

The main reason for creating different OVF is that it can be used to create VM by oVirt REST API. The RHV export domain flavor cannot be used that way. v1 -> v2: - introduced flavour types instead of booleans - instead of referring to the new flavour as "standard OVF" or "fixed OVF" I refer to it as oVirt flavour. While it is more conforming than the one used in export