I'm in the process of migrating a series of VM's from KVM environment, to an OVirt environment. I've used virt-v2v to convert quite a few M$ and Linux machines with great success. Coming up I've got to convert a Linux VM that has 3 virtual disks. Inside that VM, the three disks are part of an LVM volume. 1. How will virt-v2v handle these three virtual disks ? 2. On which disk image will I run virt-v2v ? 3. Will virt-v2v "follow" the three images and convert the machine or will I have to somehow tell it to include all three disks ? 4. Shall I have all three images together in the same directory when I run the tool ? 5. Is this the appropriate forum for this question ? As of the writing of this question I'll be using OVirt 3.6 updated on a 4 node cluster running CentOS 7 , and the most recent version of virt-v2v as is available on Fedora 23. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Feb 29, 2016, at 6:24 AM, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote: > On Mon, Feb 29, 2016 at 01:44:19PM +0200, Moran Goldboim wrote: > +Richard, v2v maintainer. > >> On Sat, Feb 27, 2016 at 8:45 PM, Clint Boggio <clint(a)theboggios.com&gt; wrote: >> >> I'm in the process of migrating a series of VM's from KVM environment, to >> an OVirt environment. I've used virt-v2v to convert quite a few M$ and >> Linux machines with great success. You don't really need to use virt-v2v when the guest already runs on KVM. The latest oVirt supports direct import of disk images, and there is also my import script for older versions of oVirt which didn't have this feature: http://git.annexia.org/?p=import-to-ovirt.git;a=summary ---------------------------------------------------------------------- Nevertheless I'll answer the rest of these questions because it's an interesting topic for people importing from other hypervisors ... >> Coming up I've got to convert a Linux VM that has 3 virtual disks. Inside >> that VM, the three disks are part of an LVM volume. >> >> 1. How will virt-v2v handle these three virtual disks ? Should just work. >> 2. On which disk image will I run virt-v2v ? On all 3 :-) Are you using `-i disk' input mode? That only supports a single disk, but you can use `-i libvirtxml' mode instead, and then you can specify as many input disks as you want: http://libguestfs.org/virt-v2v.1.html#minimal-xml-for--i-libvirtxml-option >> 3. Will virt-v2v "follow" the three images and convert the machine or will >> I have to somehow tell it to include all three disks ? You always have to tell virt-v2v. >> 4. Shall I have all three images together in the same directory when I run >> the tool ? With `-i libvirtxml' it doesn't matter. You specify the XML file, and that contains references to the disks. >> 5. Is this the appropriate forum for this question ? Yup. Rich. >> As of the writing of this question I'll be using OVirt 3.6 updated on a 4 >> node cluster running CentOS 7 , and the most recent version of virt-v2v as >> is available on Fedora 23. >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top