Hi Everyone, Any thoughts on these ? Thank you, Leo
On Sat, Sep 22, 2018, 09:09 Leo David <[email protected]> wrote: > Thank you Nathanaël, > I just think that virt-p2v.iso image once booted, will directly see the > vm attached devices that are passed by Proxmox layer (as clonezilla would > see them ), without worring about what virtualisation type is the source > machine. > ie: treating the vm as a physical machine. > If so, this tool should work on any source machine ( vmware, hyperv, > proxmox, bare metal ) right ? > The problem is that im getting that error... > > On Sep 21, 2018 11:08, "Nathanaël Blanchet" <[email protected]> wrote: > > afaik, Proxmox doesn't use the libvirt api, so you can't use the virt-p2v > tool to import proxmox into ovirt, the only way in our case is to manually > import your qcow2 disks and then attach them to a predefinated vm. > > Le 18/09/2018 à 14:31, Leo David a écrit : > > Hi, > I have succesfully used the import-to-ovirt.pl script to migrate a qcow > local disk to oVirt export domain. > Thanks a lot for that ! > The problem is that most of the vms are having their disk on ceph as rbd's. > Thist is why i think the bootable virt-p2p would be more appropiate... > but it seems is still not working. > Any thoughts ? > > Thanks, > > Leo > > On Tue, Sep 18, 2018 at 12:18 PM, Leo David <[email protected]> wrote: > >> Hi, >> I have tried already first option - not working.. >> Maybe the second would work, but i'm in the middle of figuring out why >> it does not work with virt-p2v iso, since it seems that it should do the >> job. >> 1. I have booted one vm with the iso >> 2. tested the connection against an ovirt node >> 3. selected: >> - Output: rhv >> - Output storage: 10.10.6.13://ovirt-export ( exact path as i have it >> configured on the engine, as an export domain ) >> - the rest of fields blank >> >> Then it hangs, it seems is trying to connect to libvrt although i have >> specified "rhv". >> Below, a tail on virt-v2v-conversion-log.txt: >> >> [ 0.4] Initializing the target -o rhv -os 10.10.6.13:/ovirt-export >> mount '10.10.6.13:/ovirt-export' '/tmp/v2v.IGj2A4' >> RHV: ESD mountpoint: /tmp/v2v.IGj2A4 >> RHV: ESD UUID: d6cd5efe-15eb-4e22-8caf-5ab5d267f4dd >> RHV: actual UID:GID of new files is 36:36 >> uuidgen -r >> uuidgen -r >> uuidgen -r >> RHV: will export sda to >> /tmp/v2v.IGj2A4/d6cd5efe-15eb-4e22-8caf-5ab5d267f4dd/images/25d94cfd-8277-469b-ab98-24d790d422bb/058ed849-2fb6-456c-825e-819b8920f696 >> libguestfs: [ 0.4] Opening the overlay >> trace: set_verbose true >> libguestfs: trace: set_verbose = 0 >> libguestfs: trace: set_identifier "v2v" >> libguestfs: trace: v2v: set_identifier = 0 >> libguestfs: trace: v2v: get_memsize >> libguestfs: trace: v2v: get_memsize = 500 >> libguestfs: trace: v2v: set_memsize 2000 >> libguestfs: trace: v2v: set_memsize = 0 >> libguestfs: trace: v2v: set_network true >> libguestfs: trace: v2v: set_network = 0 >> libguestfs: trace: v2v: add_drive "/var/tmp/v2vovla5ca02.qcow2" >> "format:qcow2" "cachemode:unsafe" "discard:besteffort" "copyonread:true" >> libguestfs: trace: v2v: add_drive = 0 >> libguestfs: trace: v2v: launch >> libguestfs: trace: v2v: get_tmpdir >> libguestfs: trace: v2v: get_tmpdir = "/tmp" >> libguestfs: trace: v2v: version >> libguestfs: trace: v2v: version = <struct guestfs_version = major: 1, >> minor: 36, release: 10, extra: rhel=7,release=6.el7_5.2,libvirt, > >> libguestfs: trace: v2v: get_backend >> libguestfs: trace: v2v: get_backend = "libvirt" >> libguestfs: launch: program=virt-v2v >> libguestfs: launch: identifier=v2v >> libguestfs: launch: version=1.36.10rhel=7,release=6.el7_5.2,libvirt >> libguestfs: launch: backend registered: unix >> libguestfs: launch: backend registered: uml >> libguestfs: launch: backend registered: libvirt >> libguestfs: launch: backend registered: direct >> libguestfs: launch: backend=libvirt >> libguestfs: launch: tmpdir=/tmp/libguestfsBeXgdP >> libguestfs: launch: umask=0022 >> libguestfs: launch: euid=0 >> libguestfs: libvirt version = 3009000 (3.9.0) >> libguestfs: guest random name = guestfs-28va44m6dlfp13q0 >> libguestfs: connect to libvirt >> libguestfs: opening libvirt handle: URI = qemu:///system, auth = >> default+wrapper, flags = 0 >> libvirt needs authentication to connect to libvirt URI qemu:///system >> (see also: http://libvirt.org/auth.html http://libvirt.org/uri.html) >> Please enter your authentication name: Please enter your password: >> >> >> >> Any thoughts, am I doing something wrong in the virt-p2p configuration ? >> Thank you ! >> >> >> >> >> >> >> >> On Tue, Sep 18, 2018 at 11:34 AM, Andrei Verovski <[email protected]> >> wrote: >> >>> Hi, >>> >>> Try to upload qcow into import domain via SSH, may be it will work, but >>> I’m not sure. >>> >>> Another way is to hack oVirt - create VM with qcow2 image, rename yours, >>> replace via ssh, fix permissions. >>> >>> >>> On 18 Sep 2018, at 08:00, Leo David <[email protected]> wrote: >>> >>> Thank you Andrei, >>> This would be fine in case of a few vms, but not so practical for many >>> of them to import. >>> I will try by using virt-p2v.iso to boot on source vm, and get it >>> converted to an existing oVirt nfs export domain. From where to import them >>> in the oVirt cluster. >>> Will let you know about results.. >>> If any other procedure available, please let me know. >>> Thanks a lot, >>> >>> Leo >>> >>> >>> On Tue, Sep 18, 2018, 00:21 Andrei Verovski <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Try this: >>>> >>>> 1) Storage -> Disks -> Upload -> Start >>>> select your existing qcow image >>>> >>>> 2) Create new VM, and then General -> Instance Images, clock "+" and >>>> "Attach", select imported disk image. >>>> >>>> I think it should work. >>>> >>>> PS Someone from oVirt dev team please confirm, I didn't tried import >>>> existing qcow2. >>>> >>>> >>>> On 9/17/18 3:30 PM, Leo David wrote: >>>> > Hello everyone, >>>> > I have this situation where I need to migrate about 20 vms from >>>> > Proxmox to oVirt. >>>> > In this case, its about qcow2 images running on Proxmox. >>>> > I there a recomended way and procedure for doing this ? >>>> > Thank you very much ! >>>> > >>>> > -- >>>> > Best regards, Leo David >>>> > >>>> > _______________________________________________ >>>> > Users mailing list -- [email protected] >>>> > To unsubscribe send an email to [email protected] >>>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> > oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> > List Archives: >>>> https://lists.ovirt.org/archives/list/[email protected]/message/YV5CMHDZSXJ5FQ3QRYNL2QKGXGKYHS7L/ >>>> _______________________________________________ >>>> Users mailing list -- [email protected] >>>> To unsubscribe send an email to [email protected] >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/[email protected]/message/SBW46XILAAVZIPN7Q6SP7ARJCFYO5GPG/ >>>> >>> >>> >>> _______________________________________________ >>> Users mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/[email protected]/message/A2GETEROWCXZ3NPON7OX3X6V7O5BVT7T/ >>> >>> >> >> >> -- >> Best regards, Leo David >> > > > > -- > Best regards, Leo David > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/3GLWGY7CI5K6SEEZMVH2DUE3Y246XWHO/ > > > -- > Nathanaël Blanchet > > Supervision réseau > Pôle Infrastrutures Informatiques > 227 avenue Professeur-Jean-Louis-Viala > 34193 MONTPELLIER CEDEX 5 > Tél. 33 (0)4 67 54 84 55 > Fax 33 (0)4 67 54 84 [email protected] > > >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/5UK6OGHOGYSG62EK4W7SSNFLFXTNE6KZ/
