Displaying 3 results from an estimated 3 matches for "vmx_path".
Did you mean:
vm_path
2017 Dec 08
1
Re: [PATCH v2 2/2] v2v: -i vmx: Enhance VMX support with ability to use ‘-it ssh’ transport.
On Friday, 8 December 2017 17:02:30 CET Richard W.M. Jones wrote:
> This enhances the existing VMX input support allowing it to be
> used over SSH to the ESXi server.
>
> The original command (for local .vmx files) was:
>
> $ virt-v2v -i vmx guest.vmx -o local -os /var/tmp
>
> Adding ‘-it ssh’ and using an SSH remote path gives the new syntax:
>
> $ virt-v2v \
2017 Dec 08
0
[PATCH v2 2/2] v2v: -i vmx: Enhance VMX support with ability to use ‘-it ssh’ transport.
...rce filename =
+ match vmx_source with
+ | File vmx_filename ->
+ (* Always ensure this returns an absolute path to avoid
+ * any confusion with filenames containing colons.
+ *)
+ absolute_path_from_other_file vmx_filename filename, "vmdk"
+
+ | SSH (user, server, vmx_path) ->
+ let abs_path = absolute_path_from_other_file vmx_path filename in
+ let format = "vmdk" in
+
+ (* XXX This is a hack to work around qemu / VMDK limitation
+ * "Cannot use relative extent paths with VMDK descriptor file"
+ * We can remove this if...
2017 Dec 08
4
[PATCH v2 0/2] v2v: Add -it vddk and -it ssh flags.
The first patch was previously posted here:
https://www.redhat.com/archives/libguestfs/2017-December/msg00018.html
That patch hasn't changed except that I made the ‘input_transport’
variable type-safe.
The second patch adds a significant new mode for liberating data from
VMware: the ability to copy VMs over SSH directly from ESXi
hypervisors. Although this requires enabling SSH access (a