[Shahar: Let's discuss virt-v2v & oVirt integration on the public
mailing list from now on.]
New in 1.27.27:
* What we previously called `-o ovf' -- ie the ability to export just
the OVF metadata -- has been implemented but in a slightly different
way. You can now use:
virt-v2v [...] -o rhev --no-copy -os remote:/esd
^^^^^^^^^
This means do the conversion and produce the metadata, but don't
bother copying the disks. This flag is of course applicable to other
output methods.
* You can use the options --rhev-image-uuid, --rhev-vol-uuid and
--rhev-vm-uuid to control the UUIDs used when exporting to oVirt. As
previously discussed this lets the OVF produced by the --no-copy
option be relatively stable.
* There is now a fairly minimal test suite which is run on every
release (`make check-release'). See `v2v/test-*.sh'.
It tests that the virt-v2v command line flags all work, and that a
handful of real guests don't break virt-v2v.
However it does *not* test that conversion is successful or that the
guest will boot on the target. That will be done by a more
sophisticated test suite which I'm writing which unfortunately cannot
be fully released in public because it contains proprietary guests
eg Windows.
* The `-o libvirt' target has now been implemented.
* A lot of code clean ups, bug fixes etc.
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
This is a quick way to check that virt-v2v is working for you (using
libguestfs from git).
$ ./run virt-builder fedora-20
[ 1.0] Downloading: http://libguestfs.org/download/builder/fedora-20.xz
[ 2.0] Planning how to build this image
[ 2.0] Uncompressing
[ 42.0] Opening the new disk
[ 53.0] Setting a random seed
[ 53.0] Setting passwords
Setting random password of root to kKwqFUcYYTVXUHoJ
[ 53.0] Finishing off
Output file: fedora-20.img
Output size: 4.0G
Output format: raw
Total usable space: 5.2G
Free space: 4.5G (86%)
$ ./run virt-v2v -i disk fedora-20.img -o local -os /tmp
[ 0.0] Creating an overlay to protect the source from being modified
[ 0.0] Opening the overlay
[ 9.0] Initializing the target -o local -os /tmp
[ 9.0] Inspecting the overlay
[ 14.0] Converting Fedora release 20 (Heisenbug) to run on KVM
virt-v2v: warning: could not update grub2 console: aug_get: no matching
node (ignored)
[ 32.0] Trimming filesystems to reduce amount of data to copy
[ 32.0] Closing the overlay
[ 33.0] Copying disk 1/1 to /tmp/fedora-20-sda (raw)
[ 36.0] Creating output metadata
[ 36.0] Finishing off
It's not a very meaningful test because it "converts" a KVM image
to
run on KVM. However it's useful because it checks that everything is
working, and it only takes a few minutes.
Rich.
--
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
On 15.08.14 17:45, Richard W.M. Jones wrote:> [Shahar: Let's discuss virt-v2v & oVirt integration on the public > mailing list from now on.] > > New in 1.27.27: > > * What we previously called `-o ovf' -- ie the ability to export just > the OVF metadata -- has been implemented but in a slightly different > way. You can now use: > > virt-v2v [...] -o rhev --no-copy -os remote:/esd > ^^^^^^^^^ > > This means do the conversion and produce the metadata, but don't > bother copying the disks. This flag is of course applicable to other > output methods. > > * You can use the options --rhev-image-uuid, --rhev-vol-uuid andHow do we set multiple image-uuids?> --rhev-vm-uuid to control the UUIDs used when exporting to oVirt. As > previously discussed this lets the OVF produced by the --no-copy > option be relatively stable. > > * There is now a fairly minimal test suite which is run on every > release (`make check-release'). See `v2v/test-*.sh'. > > It tests that the virt-v2v command line flags all work, and that a > handful of real guests don't break virt-v2v. > > However it does *not* test that conversion is successful or that the > guest will boot on the target. That will be done by a more > sophisticated test suite which I'm writing which unfortunately cannot > be fully released in public because it contains proprietary guests > eg Windows. > > * The `-o libvirt' target has now been implemented. > > * A lot of code clean ups, bug fixes etc. > > 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 Sun, Aug 17, 2014 at 12:25:03PM +0300, Shahar Havivi wrote:> On 15.08.14 17:45, Richard W.M. Jones wrote: > > [Shahar: Let's discuss virt-v2v & oVirt integration on the public > > mailing list from now on.] > > > > New in 1.27.27: > > > > * What we previously called `-o ovf' -- ie the ability to export just > > the OVF metadata -- has been implemented but in a slightly different > > way. You can now use: > > > > virt-v2v [...] -o rhev --no-copy -os remote:/esd > > ^^^^^^^^^ > > > > This means do the conversion and produce the metadata, but don't > > bother copying the disks. This flag is of course applicable to other > > output methods. > > > > * You can use the options --rhev-image-uuid, --rhev-vol-uuid and > How do we set multiple image-uuids?You cannot. However you can set multiple --rhev-vol-uuid options (one per disk image) which I think is what you meant. You just pass them on the command line like this: virt-v2v --rhev-vol-uuid UUID1 --rhev-vol-uuid UUID2 [etc] Source: https://github.com/libguestfs/libguestfs/blob/master/v2v/types.ml#L33 https://github.com/libguestfs/libguestfs/blob/master/v2v/cmdline.ml#L87 https://github.com/libguestfs/libguestfs/blob/master/v2v/target_RHEV.ml#L260 Rich. -- 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