On Tue, Sep 16, 2014 at 04:04:02PM +0300, Shahar Havivi wrote: > Hi, > > I am trying to convert from esx server to local directory a VM names CSB, > Its build from source 77b371b18b6a7ad37105a595931514f542a04396 > > When running: > LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic "esx://root@10.35.5.45/?no_verify=1" -o local -of raw -os /tmp/v2v CSB > > I get the following: > --------------------------------------------------------------------------- > [ 0.0] Opening the source -i libvirt -ic esx://root@10.35.5.45/?no_verify=1 CSB > Enter root's password for 10.35.5.45: > Enter host password for user 'root': > [ 4.0] Creating an overlay to protect the source from being modified > qemu-img: /tmp/v2vovl2305ba.qcow2: Could not open 'json: { "file.cookie" : "vmware_soap_session=\"52d44642-3451-51db-dc36-7621bbc387bd\"", "file.sslverify" : "off", "file.driver" : "https", "file.url" : "https://10.35.5.45/folder/CSB/CSB-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1", "file.timeout" : 60 }': Unknown driver 'https': No such file or directory > virt-v2v: error: qemu-img command failed, see earlier errors This error happens because you need to patch qemu-kvm-rhev. The patches aren't in our qemu-kvm-rhev yet (see rhvirt-patches for current status), but I have a patched version of qemu here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html

> If reporting bugs, run virt-v2v with debugging enabled and include the > complete output: > > virt-v2v -v -x [...] > --------------------------------------------------------------------------- > > > As you can see first I am propmt twice for roots password, Yes, known bug, of sorts. It's documented in the manual that it will ask for the password twice. We can't really fix it because libvirt doesn't talk to everyone else. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v

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.

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

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

[ 0.0] Opening the source -i libvirt -ic esx://10.35.5.45/?no_verify=1 RHEL Enter username for 10.35.5.45 [root]: Enter root's password for 10.35.5.45: curl -s --insecure -I 'https://10.35.5.45/folder/RHEL/RHEL-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1' ||: HTTP/1.1 401 Unauthorized Date: Wed, 17 Sep 2014 07:55:29 GMT Set-Cookie: vmware_soap_session="5257f480-c060-3dcb-0ed5-fa58236bb0e5"; Path=/; HttpOnly; Secure; Connection: close WWW-Authenticate: Basic realm="VMware HTTP server" Content-Length: 0 virt-v2v: error: esx: incorrect username or password. You might need to specify the username in the URI like this: esx://USERNAME@[etc] If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [... --------------------------------------------------------------------------------------------- Shahar. > > 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

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

Hello, I am trying to compile the latest libguestfs on debian wheezy and I am stuck at configuring which does require augeas 1.0.0 or higher which is only available on debian sid. I have tried back ports but no luck. Can anyone give me a suggestion how to do that?

Debian wheezy which is the stable version does not have that version of package in the repository only Sid has which is the unstable version. We are working here on production servers so how would I use an unstable version of OS in production?