search for: vm_snapshot_id

...| RHVExportStorageDomain -> vol_uuid); "ovf:size", Int64.to_string size_gb; + "ovf:capacity", Int64.to_string ov.ov_virtual_size; "ovf:fileRef", fileref; "ovf:parentRef", ""; "ovf:vm_snapshot_id", uuidgen (); diff --git a/v2v/test-v2v-o-rhv.ovf.expected b/v2v/test-v2v-o-rhv.ovf.expected index 342eb99d3..1deec9c9d 100644 --- a/v2v/test-v2v-o-rhv.ovf.expected +++ b/v2v/test-v2v-o-rhv.ovf.expected @@ -10,7 +10,7 @@ </Section> <Section xsi:type='ovf:DiskSection_Type'...

...k ovf:name='default'/> + </Section> + <Section xsi:type='ovf:DiskSection_Type'> + <Info>List of Virtual Disks</Info> + <Disk ovf:diskId='#VOL_ID#' ovf:size='1' ovf:fileRef='#DISK_ID#/#VOL_ID#' ovf:parentRef='' ovf:vm_snapshot_id='#UUID#' ovf:volume-format='RAW' ovf:volume-type='Sparse' ovf:format='http://en.wikipedia.org/wiki/Byte' ovf:disk-interface='IDE' ovf:disk-type='System' ovf:boot='True' ovf:actual_size='1'/> + </Section> + <Content ovf:id...

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 way. Tomáš Golembiovský (3): v2v: tests: check generated OVF v2v: ovf: Create OVF more aligned with the standard v2v: vdsm: add --vdsm-fixed-ovf option v2v/cmdline.ml | 5 ++ v2v/create_ovf.ml

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 way. v1 -> v2: - introduced flavour types instead of booleans - instead of referring to the new flavour as "standard OVF" or "fixed OVF" I refer to it as oVirt flavour. While it is more conforming than the one used in export

...s below,the second one shows ovf:boot='False'. <Disk ovf:actual_size='1' ovf:diskId='0be98db1-86cc-4da2-9ecb-aae5f700d569' ovf:size='8' ovf:fileRef='b59d8629-38f4-4443-baf0-07462e75bb91/0be98db1-86cc-4da2-9ecb-aae5f700d569' ovf:parentRef='' ovf:vm_snapshot_id='ad886fef-1ca0-4c69-a6d9-52f9a053bd08' ovf:volume-format='COW' ovf:volume-type='Sparse' ovf:format='http://en.wikipedia.org/wiki/Byte' ovf:disk-interface='VirtIO' ovf:disk-type='System' ovf:boot='True'/> <Disk ovf:actual_size='1&...

...</Section> - <Section xsi:type='ovf:DiskSection_Type'> + </NetworkSection> + <DiskSection> <Info>List of Virtual Disks</Info> - <Disk ovf:diskId='VOL' ovf:size='1' ovf:fileRef='IMAGE/VOL' ovf:parentRef='' ovf:vm_snapshot_id='#UUID#' ovf:volume-format='COW' ovf:volume-type='Sparse' ovf:format='http://en.wikipedia.org/wiki/Byte' ovf:disk-interface='IDE' ovf:disk-type='System' ovf:boot='True' ovf:actual_size='1'/> - </Section> - <Content ovf:id...

On Wed, Oct 08, 2014 at 08:11:16AM +0000, VONDRA Alain wrote: > Hi, > I meet an amazing issue, when I convert a raw file to the oVirt environment using virt-v2v. > All seems to work fine, my VM is composed of 9 disks, the processes > finishes without any trouble, the files are well present in the > right import volume, but only the first system disk appear un my > oVirt Import

Fix one dist issue, and almost all the builddir!=srcdir issues. (For the record, only 3 tests still fail in that setup.) Pino Toscano (3): libvirt-ocaml: add libvirt_c.h as source tests: fix path to sources of fake-virtio-win.iso tests: fix srcdir references bundled/libvirt-ocaml/Makefile.am | 1 + test-data/fake-virtio-win/Makefile.am | 2 +- tests/rhbz1232192.sh

...gt; "Sparse" | Preallocated -> "Preallocated" in @@ -456,8 +456,8 @@ and add_disks targets guestcaps output_alloc sd_uuid image_uuids vol_uuids ovf = "ovf:fileRef", fileref; "ovf:parentRef", ""; "ovf:vm_snapshot_id", uuidgen (); - "ovf:volume-format", format_for_rhev; - "ovf:volume-type", output_alloc_for_rhev; + "ovf:volume-format", format_for_rhv; + "ovf:volume-type", output_alloc_for_rhv; "ovf:format", &qu...

...gt; "Sparse" | Preallocated -> "Preallocated" in @@ -456,8 +456,8 @@ and add_disks targets guestcaps output_alloc sd_uuid image_uuids vol_uuids ovf = "ovf:fileRef", fileref; "ovf:parentRef", ""; "ovf:vm_snapshot_id", uuidgen (); - "ovf:volume-format", format_for_rhev; - "ovf:volume-type", output_alloc_for_rhev; + "ovf:volume-format", format_for_rhv; + "ovf:volume-type", output_alloc_for_rhv; "ovf:format", &qu...

v2: - Fix virt-p2v messages too. Rich.

Move all target-specific functionality into its own module in preparation for output to RHEV. --- MANIFEST | 1 + lib/Sys/VirtV2V/Connection.pm | 46 ++--- lib/Sys/VirtV2V/Converter.pm | 138 +------------ lib/Sys/VirtV2V/Target/LibVirt.pm | 419 +++++++++++++++++++++++++++++++++++++ lib/Sys/VirtV2V/Transfer/ESX.pm | 91 +++------ po/POTFILES.in

.. and a lot of refactoring. https://bugzilla.redhat.com/show_bug.cgi?id=1167623 Rich.

https://bugzilla.redhat.com/show_bug.cgi?id=1167623

...9;, $vol->get_size()); $file->setAttribute('ovf:description', 'imported by virt-v2v'); # Add disk to DiskSection @@ -986,8 +1062,8 @@ sub _disks $diske->setAttribute('ovf:parentRef', ''); $diske->setAttribute('ovf:vm_snapshot_id', '00000000-0000-0000-0000-000000000000'); - $diske->setAttribute('ovf:volume-format', 'RAW'); - $diske->setAttribute('ovf:volume-type', 'Sparse'); + $diske->setAttribute('ovf:volume-format...