similar to: Re: Can virt-v2v-copy-to-local be used? (#41)

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 \ -i vmx -it ssh \ "root@esxi.example.com:/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local

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 \

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 \ -

2013/8/12 varun bhatnagar <varun292006@gmail.com>: > Hi, > > Today I was trying to start a node using libvirt on ESX (esxi-5.1) > hypervisor and I got the following error message: > > virsh # define /local/myNode/esxdomain.xml > Domain testNode defined from /local/myNode/esxdomain.xml > virsh # start testNode > error: Failed to start domain testNode > error:

Hi, Today I was trying to start a node using libvirt on ESX (esxi-5.1) hypervisor and I got the following error message: *virsh # define /local/myNode/esxdomain.xml* *Domain testNode defined from /local/myNode/esxdomain.xml* *virsh # start testNode* *error: Failed to start domain testNode* *error: internal error: Could not start domain: GenericVmConfigFault - Cannot open the disk

Thanks a ton for the reply Matthias. I am little confused here. How to add volume on my esx server using virsh? I did SCP and copied my vmdk image to [datastore1] testNode/cluster.vmdk and also modified my xml file as you suggested. Now when I tried starting the node it gave me an error message saying: "error: Failed to start testNode error: internal error: Could not start domain:

Hi, Is there a way to use a locally stored copy of an exsi created virtual machine to convert to libvirt via virt-v2v? I don't want to have to download the image from the esxi server each time I run virt-v2v as that copy takes a long time. Perhaps I'm just missing the command line option. What I would like to do is copy the image manually to the virt-v2v server and work on it locally

Hello, Richard. > -----Original Message----- > From: Richard W.M. Jones [mailto:rjones@redhat.com] > Sent: Monday, March 5, 2018 8:42 PM > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > Cc: libguestfs@redhat.com > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM: setfiles ... > Multiple same specifications for /.*. > > On Mon, Mar 05, 2018 at

Previously we placed large files in g#get_cachedir () (usually /var/tmp). However the problem is this ties the libguestfs appliance and the virt-v2v overlay files to the same location. When virt-v2v is run in a container, or any other situation where local storage is limited, it's helpful to be able to put the overlay files on an externally mounted PVC, which might be using NFS and shared

If you accidentally point -i vmx at a disk image, it will try to load the whole thing into memory and crash. Catch this narrow case and print an error. However don't fail if ‘file’ is not installed or if we don't know what the file is. --- v2v/parse_vmx.ml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/v2v/parse_vmx.ml b/v2v/parse_vmx.ml index 65d5a0edd..f6c34e2cf

On Wed, Oct 11, 2017 at 05:17:14PM +0200, Pino Toscano wrote: > On Wednesday, 11 October 2017 15:25:26 CEST Richard W.M. Jones wrote: > > If you accidentally point -i vmx at a disk image, it will try to load > > the whole thing into memory and crash. Catch this narrow case and > > print an error. > > > > However don't fail if ‘file’ is not installed or if we

On Wednesday, 11 October 2017 15:25:26 CEST Richard W.M. Jones wrote: > If you accidentally point -i vmx at a disk image, it will try to load > the whole thing into memory and crash. Catch this narrow case and > print an error. > > However don't fail if ‘file’ is not installed or if we don't know what > the file is. > --- > v2v/parse_vmx.ml | 12 ++++++++++++ >

We only use xmlParseURI to parse our own "homebrew" URIs, for example the ones used by guestfish --add or virt-v2v. Unfortunately xmlParseURI cannot handle URIs with spaces or other non-RFC-compliant characters so simple commands like these fail: $ guestfish -a 'ssh://example.com/virtual machine.img' guestfish: --add: could not parse URI 'ssh://example.com/virtual

> -----Original Message----- > From: Richard W.M. Jones [mailto:rjones@redhat.com] > Sent: Tuesday, March 6, 2018 11:49 AM > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > Cc: libguestfs@redhat.com > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM: setfiles ... > Multiple same specifications for /.*. > > On Tue, Mar 06, 2018 at 08:40:51AM

We only use xmlParseURI to parse our own "homebrew" URIs, for example the ones used by guestfish --add or virt-v2v. Unfortunately xmlParseURI cannot handle URIs with spaces or other non-RFC-compliant characters so simple commands like these fail: $ guestfish -a 'ssh://example.com/virtual machine.img' guestfish: --add: could not parse URI 'ssh://example.com/virtual

On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote: > On 16.09.14 15:09, Richard W.M. Jones wrote: > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > I am using upstream qemu while using this local variables: > > > export PATH=/home/shahar/git/qemu:$PATH > > > export

To Whom It May concern: I found that the following error is caused by adding a scsi disk to install the os, I remove the scsi disk and the error remove but still report 'out of memory': virsh # dumpxml win2003_122 internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' virsh # list --all Id Name

On Sun, Sep 21, 2014 at 04:16:59PM +0300, Shahar Havivi wrote: > On 17.09.14 10:02, Richard W.M. Jones wrote: > > On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote: > > > On 16.09.14 15:09, Richard W.M. Jones wrote: > > > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > > > I am using upstream qemu while using this

Starting from libguestfs/virt-v2v 1.39.12, virt-v2v attempts to uninstall the VMware tools from Windows guests, so there is no need to remove them manually before the conversion. Thanks to: Ming Xie. --- docs/virt-v2v-input-vmware.pod | 36 ---------------------------------- 1 file changed, 36 deletions(-) diff --git a/docs/virt-v2v-input-vmware.pod b/docs/virt-v2v-input-vmware.pod index

On 17.09.14 10:02, Richard W.M. Jones wrote: > On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote: > > On 16.09.14 15:09, Richard W.M. Jones wrote: > > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > > I am using upstream qemu while using this local variables: > > > > export PATH=/home/shahar/git/qemu:$PATH > > >