similar to: OVF => XML?

Hi, On Friday, 24 April 2020 14:57:38 CEST Andrew Thurber (anthurbe) wrote: > This multi-disk ovf generates “no href in ovf:File (id=)” > Other single-disk ovfs on the same system work. I don’t have another multi-disk ova to try. > I’ve compared the syntax with the test file on github and it appears to be essentially the same: > virt-v2v/tests/test-v2v-i-ova-two-disks.ovf > Any

Mixing the XML parsing with the other functions of this module made it very hard to understand. Splitting the XML parsing into another module simplifies the flow considerably. This is just code refactoring and should not affect the semantics. --- v2v/Makefile.am | 2 + v2v/input_ova.ml | 323 +++++++++++---------------------------------- v2v/parse_ovf_from_ova.ml | 226

No need to read the whole OVF file in memory and parse that -- let libxml2 parse it directly. --- v2v/parse_ovf_from_ova.ml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/v2v/parse_ovf_from_ova.ml b/v2v/parse_ovf_from_ova.ml index 27761d23..5acf7070 100644 --- a/v2v/parse_ovf_from_ova.ml +++ b/v2v/parse_ovf_from_ova.ml @@ -36,8 +36,7 @@ type ovf_disk = { } let

On Thu, Oct 22, 2015 at 08:47:36AM +0100, Richard W.M. Jones wrote: > On Wed, Oct 21, 2015 at 03:19:15PM -0700, Don Marti wrote: > > I got the "IE10 on Win 8" VM download from here: > > https://dev.modern.ie/tools/vms/linux/ > > > > and am trying to convert the .ova file to a format that > > will work with virt-manager and KVM on Fedora 21. > >

On Wed, Oct 21, 2015 at 03:19:15PM -0700, Don Marti wrote: > I got the "IE10 on Win 8" VM download from here: > https://dev.modern.ie/tools/vms/linux/ > > and am trying to convert the .ova file to a format that > will work with virt-manager and KVM on Fedora 21. > > I tried this: > > $ virt-v2v -v -x -i ova -o libvirt IE10\ -\ Win8.ova > > and got

Check the generated OVF for -o rhv and -o vdsm outputs. Variable UUIDs and date/times are filtered out. Make sure the the important UUIDs (disk, volume, VM) are where we think they should be. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/test-v2v-o-rhv.ovf.expected | 92 ++++++++++++++++++++++++++++++++ v2v/test-v2v-o-rhv.sh | 20 +++++++

I try do use one of the images available from [1] These images comes in two flavors, one vmx, one ovf. I do not know how to convert one of these to centos6-libvirt-kvm virt-convert gives me an error $ virt-convert -i ovf -o virt-image path_to_image.ovf ERROR Couldn't convert disks: Disk conversion failed with exit status 1: qemu-img: Could not open 'path_to_image.vmdk' The vmdk

For historical reasons the OVF used in RHV export domain contains some deviations from the OVF standard. The format used in -o rhv has to remain fixed but for -o vdsm and we could produce much nicer OVF. This patch serves as a preparatory step to this. The main reason for creating different OVF is that it can be used to create VM by oVirt REST API. The RHV export domain flavor cannot be used that

I got the "IE10 on Win 8" VM download from here: https://dev.modern.ie/tools/vms/linux/ and am trying to convert the .ova file to a format that will work with virt-manager and KVM on Fedora 21. I tried this: $ virt-v2v -v -x -i ova -o libvirt IE10\ -\ Win8.ova and got this output: virt-v2v: libguestfs 1.28.12 (x86_64) [ 0.0] Opening the source -i ova IE10 - Win8.ova tar -xf

Where supported, pass the source CPU vendor, model and topology to the target hypervisor. For -i ova, we can get just cores per socket via a proprietary VMware extension to OVF. For -i libvirt and from virt-p2v, we can get all of these fields from the libvirt XML. For -o libvirt/local, we can preserve all of the information in the target XML. For -o glance, as far as I can tell from the

Announcing the open-ovf project and source code availibility. Hi folks, we are announcing the availibility of source code for the open-ovf project. OVF is a standard packaging format for virtual machines and software appliances. The open-ovf project is seeking contributors and users to help establish OVF as a transparent and platform-nuetral method for packaing virtual machine images. We

Instead of using ‘xpath_(string|int|int64)_default’ we can write the equivalent code using ‘Option.default’. This is not quite so concise, but may be easier to understand. eg: xpath_int_default xctx "xpath_expr" 10 -> Option.default 10 (xpath_int xctx "xpath_expr") --- common/mltools/xpath_helpers.ml | 12 ------------ common/mltools/xpath_helpers.mli | 6 ------

You can now use -o rhv (-o rhev is supported for compatibility). --- p2v/gui.c | 5 +- p2v/virt-p2v.pod | 13 ++- v2v/Makefile.am | 8 +- v2v/OVF.ml | 30 +++---- v2v/OVF.mli | 2 +- v2v/changeuid.mli

Some ova files have their ovf and other files inside a folder rather than at the root of the tarball. Consider the paths relative to the ovf file to cover this case too. --- v2v/Makefile.am | 1 + v2v/input_ova.ml | 3 +- v2v/test-v2v-i-ova-subfolders.sh | 88 ++++++++++++++++++++++++++++++++++++++++ 3 files changed, 91 insertions(+), 1 deletion(-) create mode

You can now use -o rhv (-o rhev is supported for compatibility). --- v2v/Makefile.am | 8 +- v2v/OVF.ml | 30 +++---- v2v/OVF.mli | 2 +- v2v/changeuid.mli | 4 +- v2v/cmdline.ml | 12 +-- v2v/convert_windows.ml

This patch refactors the data transfer code with several goals: * Have a common read(source)/write(target) loop so that common processing can happen in the middle of it, e.g. format change/progress bar * Provide volume metadata to transfers to allow smarter reading/writing, e.g. of sparse files * Simplify the data transfer code The patch *isn't* NFC because there are some minor behaviour

The information whether the disk is gzip compressed or not is stored in the OVF. There is no reason to do the detection. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 28 +++++++++++++++++----------- v2v/test-v2v-i-ova-gz.ovf | 2 +- 2 files changed, 18 insertions(+), 12 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index

The information whether the disk is gzip compressed or not is stored in the OVF. There is no reason to do the detection. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 36 ++++++++++++++++++++---------------- v2v/test-v2v-i-ova-gz.ovf | 2 +- 2 files changed, 21 insertions(+), 17 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index

Don't pass these flags to dozens of functions. --- builder/builder.ml | 47 +++++++++-------- builder/cache.ml | 4 +- builder/cache.mli | 2 +- builder/cmdline.ml | 13 ++--- builder/downloader.ml | 14 +++-- builder/downloader.mli

Where are the configuration files for libvirt and/or virsh actually stored? It seems that most of them are in /etc/libvirt but identical copies are also found in /var/lib/libvirt. In my case I am having issues with the network/default.xml file being different. Is there a reason why the config seems to be in two places at once? And which one is the 'correct' one? -David Mitchell