Displaying 8 results from an estimated 8 matches for "networksection_typ".
Did you mean:
networksection_type
2018 Feb 18
0
[PATCH 2/3] v2v: ovf: Create OVF more aligned with the standard
...s = List.length vol_uuids);
let memsize_mb = source.s_memory /^ 1024L /^ 1024L in
@@ -288,12 +288,22 @@ let rec create_ovf source targets guestcaps inspect
] [
Comment generated_by;
e "References" [] [];
- e "Section" ["xsi:type", "ovf:NetworkSection_Type"] [
- e "Info" [] [PCData "List of networks"]
- ];
- e "Section" ["xsi:type", "ovf:DiskSection_Type"] [
- e "Info" [] [PCData "List of Virtual Disks"]
- ];
+ if rhv_export_flavor then
+...
2018 Feb 18
6
[PATCH 0/3] Make generated OVF more conforming to standard
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
2018 Feb 22
5
[PATCH v2 0/3] Make generated OVF more conforming to standard
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
2018 Feb 18
0
[PATCH 1/3] v2v: tests: check generated OVF
...39;>
+ <!-- generated by virt-v2v 1.38.0 -->
+ <References>
+ <File ovf:href='#DISK_ID#/#VOL_ID#' ovf:id='#VOL_ID#' ovf:size='536870912' ovf:description='generated by virt-v2v 1.38.0'/>
+ </References>
+ <Section xsi:type='ovf:NetworkSection_Type'>
+ <Info>List of networks</Info>
+ <Network ovf:name='default'/>
+ </Section>
+ <Section xsi:type='ovf:DiskSection_Type'>
+ <Info>List of Virtual Disks</Info>
+ <Disk ovf:diskId='#VOL_ID#' ovf:size='1...
2018 Jun 18
1
[PATCH] v2v: <File ovf:size> changed to the actual size (if known).
...#39; ovf:size='536870912' ovf:description='generated by virt-v2v'/>
+ <File ovf:href='#DISK_ID#/#VOL_ID#' ovf:id='#VOL_ID#' ovf:description='generated by virt-v2v' ovf:size='#SIZE#'/>
</References>
<Section xsi:type='ovf:NetworkSection_Type'>
<Info>List of networks</Info>
diff --git a/v2v/test-v2v-o-rhv.sh b/v2v/test-v2v-o-rhv.sh
index c9ec0dbce..eb22ed95b 100755
--- a/v2v/test-v2v-o-rhv.sh
+++ b/v2v/test-v2v-o-rhv.sh
@@ -74,6 +74,7 @@ sed -i \
-e "s/$DISK_ID/#DISK_ID#/g" \
-e "s/$VM_ID/#V...
2018 Feb 18
0
[PATCH 3/3] v2v: vdsm: add --vdsm-fixed-ovf option
...OL' ovf:size='536870912' ovf:description='generated by virt-v2v 1.38.0'/>
+ <File ovf:href='VOL' ovf:id='VOL' ovf:size='536870912' ovf:description='generated by virt-v2v 1.38.0'/>
</References>
- <Section xsi:type='ovf:NetworkSection_Type'>
+ <NetworkSection>
<Info>List of networks</Info>
<Network ovf:name='default'/>
- </Section>
- <Section xsi:type='ovf:DiskSection_Type'>
+ </NetworkSection>
+ <DiskSection>
<Info>List of Virtual Disks...
2010 Mar 30
3
[PATCH 1/2] Refactor guest and volume creation into Sys::VirtV2V::Target::LibVirt
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
2011 Mar 11
2
[PATCH 1/2] Allow reading more data than the reported size of a volume
If a volume is not an exact multiple of 512 bytes, qemu-img will report its size
rounded down to a 512 byte boundary. However, when copying, the file is still
read until EOF, which will return more data than was expected. This change
prevents that causing a failure in itself.
The situation is still not resolved, however, as there are still situations
where this will cause a failure. For example,