search for: libvirtxml

...I just had an exit in there). The meat is really in the 4th patch. The rename of MetadataReader->Connection was because the Connection is now really providing the whole guest, rather than just its metadata. I intend to add more transfer methods once ESX conversion is working. A copy method for LibVirtXML is required at least. _storage_iterate in Sys::VirtV2V::Connection does interesting things with the domain's storage devices. I'd especially appreciate a close look there. Matt

If a user accidentally passed a valid XML document to the LibvirtXML which wasn't actually a libvirt domain XML document, they would end up getting obtuse errors from a libguestfs library. This change does 2 sanity checks: 1. After parsing a the XML document, check /domain/name exists. 2. Check that the domain defines some storage The second check is generally...

With this patchset I have successfully[1] imported a RHEL 5 guest directly from ESX with the following command line: virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64 Login details are stored in ~/.netrc Note that this is the only guest I've tested against. I haven't for example, checked that I haven't broken Xen imports. Matt [1] With the exception of

...uire a pool to be specified when using libvirt output, meaning storage will always be copied. --- MANIFEST | 1 + lib/Sys/VirtV2V/Connection.pm | 74 +++++++++--------- lib/Sys/VirtV2V/Connection/LibVirt.pm | 18 +++-- lib/Sys/VirtV2V/Connection/LibVirtXML.pm | 11 ++- lib/Sys/VirtV2V/Target/LibVirt.pm | 18 ++--- lib/Sys/VirtV2V/Transfer/ESX.pm | 7 +- lib/Sys/VirtV2V/Transfer/LocalCopy.pm | 121 ++++++++++++++++++++++++++++++ v2v/virt-v2v.pl | 7 ++- 8 files changed, 193 insertions(+), 64 delet...

Unless you're lucky, the target volumes won't be in a storage pool, so libvirt will return an error. For libvirtxml we know that the storage is local, so we can inspect it directly. We use qemu-img to determine format and file size. --- lib/Sys/VirtV2V/Connection/LibVirtXMLSource.pm | 48 ++++++++++++++++++++--- 1 files changed, 41 insertions(+), 7 deletions(-) diff --git a/lib/Sys/VirtV2V/Connection/LibVirt...

In data venerdì 28 agosto 2015 14:19:05, Richard W.M. Jones ha scritto: > When importing from VMware via the libvirt driver, the libvirt driver > can add an empty source bridge name: > > <interface type='bridge'> > <mac address='00:01:02:03:04:05:06'/> > <source bridge=''/> > </interface> > > Replicate

When reading a libvirt XML which has: <graphics ...> <listen type='none'/> </graphics> then just ignore it, as it is (roughly) the same as no <listen> child elements at all. This avoids a warning about an unknown listen type. --- v2v/input_libvirtxml.ml | 1 + 1 file changed, 1 insertion(+) diff --git a/v2v/input_libvirtxml.ml b/v2v/input_libvirtxml.ml index 33e878e..1540798 100644 --- a/v2v/input_libvirtxml.ml +++ b/v2v/input_libvirtxml.ml @@ -101,6 +101,7 @@ let parse_libvirt_xml ?conn xml = (* Use only the first <listen> co...

Previously, only the LibVirtXML connection translated network and bridge names in imported metadata. This change moves this functionality in Converter, making it available to LibVirt connections as well. At the same time, the format of the config file is switched to XML. The primary driver for this is that the allowable syntax o...

Currently -i libvirtxml mode only works for local files or NBD disks. The purpose of NBD is to support virt-p2v. This change adds support for network disks over http or https, ie: <disk type='network' device='disk'> <driver name='qemu' type='raw'/> <source p...

...--------------- 1 files changed, 34 insertions(+), 22 deletions(-) diff --git a/v2v/virt-v2v.pl b/v2v/virt-v2v.pl index adaa9a9..29716d2 100755 --- a/v2v/virt-v2v.pl +++ b/v2v/virt-v2v.pl @@ -49,12 +49,13 @@ virt-v2v - Convert a guest to use KVM =head1 SYNOPSIS - virt-v2v -f virt-v2v.conf -i libvirtxml -op transfer guest-domain.xml + virt-v2v -i libvirtxml -op imported --network default guest-domain.xml - virt-v2v -f virt-v2v.conf -ic esx://esx.server/ -op transfer esx_guest + virt-v2v -ic esx://esx.server/ -op imported --network default esx_guest - virt-v2v -f virt-v2v.conf -ic esx://esx.ser...

...2v.pod b/docs/virt-v2v.pod index 4d2f241ad723..ac15108ae332 100644 --- a/docs/virt-v2v.pod +++ b/docs/virt-v2v.pod @@ -250,24 +250,26 @@ metadata. virt-v2v tries to guess the best default metadata. This is usually adequate but you can get finer control (eg. of memory and vCPUs) by using I<-i libvirtxml> instead. Only guests that use a single disk can be imported this way. =item B<-i> B<libvirt> Set the input method to I<libvirt>. This is the default. In this mode you have to specify a libvirt guest name or UUID on the command line. You may also specify a libvirt...

...2v.pod b/docs/virt-v2v.pod index 4d2f241ad723..2bd0b4425d80 100644 --- a/docs/virt-v2v.pod +++ b/docs/virt-v2v.pod @@ -250,24 +250,26 @@ metadata. virt-v2v tries to guess the best default metadata. This is usually adequate but you can get finer control (eg. of memory and vCPUs) by using I<-i libvirtxml> instead. Only guests that use a single disk can be imported this way. =item B<-i> B<libvirt> Set the input method to I<libvirt>. This is the default. In this mode you have to specify a libvirt guest name or UUID on the command line. You may also specify a libvirt...

...and set the VIRTIO_WIN environment variable to point to it: > >   http://libguestfs.org/virt-v2v.1.html#environment-variables > The above is done (easy). > Do you have metadata from VirtualBox (number of CPUs, RAM, etc) in > some format? If not, then you should probably use the ‘-i libvirtxml’ > input method. You will have to write or modify the metadata, as > documented here: > >   http://libguestfs.org/virt-v2v.1.html#minimal-xml-for--i-libvirtxml-option > Please bear with me but I really don't have enough info as to HOW to modify the xml template., beyond the obvi...

...--------------------------------------------- *-v and -x options are not working in my case.* *[root@kvm16 ~]#* virt-v2v -v -ic esx://10.16.32.13/?no_verify=1 yardqakvm -o rhev -os 10.16.32.16:/vm-images/export_domain --network rhevm Option v is ambiguous (version, vmtype) Usage: virt-v2v -i libvirtxml -os imported --network default guest-domain.xml virt-v2v -ic esx://esx.server/ -os imported --network default esx_guest virt-v2v -ic esx://esx.server/ \ -o rhev -os rhev.nfs.storage:/export_domain --network rhevm \ esx_guest *[root@kvm16 ~]#* virt-v2v -x -ic...

Hi, I am new to v2v/libguestfs. I need to convert a 30 GB virtual machine running Windows7 64 bit (a guest on a Linux system) from Virtualbox vdi format to qcow2 (or raw/img--another debate in itself) so I can use libvirt/qemu/kvm to run it and completely migrate away from Virtualbox. The vdi machine is a mission critical production environment and I cannot afford to mess it up, etc. Will keep

...; index 4d2f241ad723..2bd0b4425d80 100644 > --- a/docs/virt-v2v.pod > +++ b/docs/virt-v2v.pod > @@ -250,24 +250,26 @@ metadata. virt-v2v tries to guess the best default metadata. This is > usually adequate but you can get finer control (eg. of memory and > vCPUs) by using I<-i libvirtxml> instead. Only guests that use a single > disk can be imported this way. > > =item B<-i> B<libvirt> > > Set the input method to I<libvirt>. This is the default. > > In this mode you have to specify a libvirt guest name or UUID on the > comma...

Previously, only the LibVirtXML connection translated network and bridge names in imported metadata. This change moves this functionality in Converter, making it available to LibVirt connections as well. At the same time, the format of the config file is switched to XML. The primary driver for this is that the allowable syntax o...

.....2bd0b4425d80 100644 >> --- a/docs/virt-v2v.pod >> +++ b/docs/virt-v2v.pod >> @@ -250,24 +250,26 @@ metadata. virt-v2v tries to guess the best default metadata. This is >> usually adequate but you can get finer control (eg. of memory and >> vCPUs) by using I<-i libvirtxml> instead. Only guests that use a single >> disk can be imported this way. >> >> =item B<-i> B<libvirt> >> >> Set the input method to I<libvirt>. This is the default. >> >> In this mode you have to specify a libvirt guest nam...

...a4728..3559738 100755 --- a/v2v/virt-v2v.pl +++ b/v2v/virt-v2v.pl @@ -21,7 +21,6 @@ use strict; use Pod::Usage; use Getopt::Long; -#use Data::Dumper; use File::Spec; use File::stat; @@ -50,16 +49,19 @@ virt-v2v - Convert a guest to use KVM =head1 SYNOPSIS - virt-v2v -f virt-v2v.conf -i libvirtxml guest-domain.xml + virt-v2v -f virt-v2v.conf -i libvirtxml -op transfer guest-domain.xml - virt-v2v -f virt-v2v.conf -ic esx://esx.server/ -op transfer guest-domain + virt-v2v -f virt-v2v.conf -ic esx://esx.server/ -op transfer esx_guest + + virt-v2v -f virt-v2v.conf -ic esx://esx.server/ \ +...

...; >> --- a/docs/virt-v2v.pod > >> +++ b/docs/virt-v2v.pod > >> @@ -250,24 +250,26 @@ metadata. virt-v2v tries to guess the best default metadata. This is > >> usually adequate but you can get finer control (eg. of memory and > >> vCPUs) by using I<-i libvirtxml> instead. Only guests that use a single > >> disk can be imported this way. > >> > >> =item B<-i> B<libvirt> > >> > >> Set the input method to I<libvirt>. This is the default. > >> > >> In this mode you...