[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Libguestfs] virt-v2v -ic question



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 local variables:
> > > > > export PATH=/home/shahar/git/qemu:$PATH
> > > > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64
> > > > > 
> > > > > Is that sufficient?
> > > > 
> > > > Yup, upstream qemu should work fine.  Or even the qemu in Fedora Rawhide.
> > > Build the latest qemu, set the PATH and LIBGUESTFS_HV variables and still got
> > > the error, any idea?
> > > 
> > > ---------------------------------------------------------------------------------------------
> > > shahar shaharh ~/git/libguestfs (master) LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic "esx://10.35.5.45/?no_verify=1" -o local -of raw -os /tmp/v2v RHEL
> > 
> > I see - the esx:// URL won't work (I guess virt-v2v should explicitly
> > reject these).
> > 
> > Anyway for new virt-v2v you have to have vCenter installed.  It's
> > available as an OVA that you can install on top of ESXi.  And then the
> > URL would be:
> > 
> >   vpx://user vcenter/Datacenter/10.35.5.45?no_verify=1
> > 
> > where 'user' is probably 'administrator' and 'vcenter' is the address
> > of the vCenter server, and 'Datacenter' is the name of the datacenter
> > which you had to choose when installing either ESXi or vCenter or you
> > can find it out from the UI.
> > 
> > Rich.
> We installed the vcenter, while the following virsh command is working fine:
> $ virsh -c "vpx://root 10 35 4 35/MyDatacenter/10.35.5.45?no_verify=1" list --all
> 
> When trying the same uri in v2v:
> $ LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic "vpx://root 10 35 4 35/MyDatacenter/10.35.5.45?no_verify=1" -o local -of raw -os /tmp/v2v CSB
> 
> We get the following error:
> ----------------------------------------------------------------------------
> [   0.0] Opening the source -i libvirt -ic vpx://root 10 35 4 35/MyDatacenter/10.35.5.45?no_verify=1 CSB
> Enter root's password for 10.35.4.35:
> Enter host password for user 'root':
> [  10.0] Creating an overlay to protect the source from being modified
> qemu-img: /tmp/v2vovl25ed85.qcow2: Could not open 'json: { "file.cookie" : "vmware_soap_session=\"52c0d622-226b-546e-0ec9-9ab8601a4dd8\"", "file.sslverify" : "off", "file.driver" : "https", "file.url" : "https://10.35.4.35/folder/CSB/CSB-flat.vmdk?dcPath=MyDatacenter&dsName=datastore1";, "file.timeout" : 60 }': Unknown driver 'https': No such file or directory
> virt-v2v: error: qemu-img command failed, see earlier errors
> ----------------------------------------------------------------------------

Yup - unfortunately you need the patched qemu-kvm-rhev at the moment,
until the patches go into RHEL 7 (see rhvirt-patches).

https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]