Displaying 20 results from an estimated 600 matches similar to: "[PATCH 0/3] v2v: Implement MAC address to network/bridge mapping."
2016 Feb 20
8
[PATCH v2 0/4] v2v: more control over device types
The decision on which device type to use for disks, network and video
cards on output used to be taken deep inside the converting functions.
This is not always desirable. In particular, there are scenarios when
this decision is made before the convertion takes place. E.g. in
in-place mode, the decisions are taken and the output VM configuration
is created outside of v2v tool.
This patchset
2016 Mar 11
6
[PATCH v3 0/5] v2v: more control over device types
The decision on which device type to use for disks, network and video
cards on output used to be taken deep inside the converting functions.
This is not always desirable. In particular, there are scenarios when
this decision is made before the convertion takes place. E.g. in
in-place mode, the decisions are taken and the output VM configuration
is created outside of v2v tool.
This patchset
2016 Feb 09
7
[PATCH 0/4] v2v: more control over device types
The decision on which device type to use for disks, network and video
cards on output used to be taken deep inside the converting functions.
This is not always desirable. In particular, there are scenarios when
this decision is made before the convertion takes place. E.g. in
in-place mode, the decisions are taken and the output VM configuration
is created outside of v2v tool.
This patchset
2015 Oct 20
1
[PATCH v3 01/13] v2v: factor out opening input VM
Opening the source VM and amending the properties in its internal
representation in accordance with command-line options fit nicely into
two isolated functions.
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---
v2v/v2v.ml | 124 ++++++++++++++++++++++++++++++++-----------------------------
1 file changed, 65 insertions(+), 59 deletions(-)
diff --git a/v2v/v2v.ml b/v2v/v2v.ml
index
2016 Mar 18
10
[PATCH v4 0/5] v2v: more control over device types
The decision on which device type to use for disks, network and video
cards on output used to be taken deep inside the converting functions.
This is not always desirable. In particular, there are scenarios when
this decision is made before the convertion takes place. E.g. in
in-place mode, the decisions are taken and the output VM configuration
is created outside of v2v tool.
This patchset
2015 Aug 28
7
v2v: -i libvirtxml: Map empty network or bridge name to a default (RHBZ#1257895).
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 what we do on the -i ova path, and map these to "eth0",
"eth1" etc.
This also includes a bunch
2015 Nov 10
3
[PATCH] v2v: Make the interface between cmdline.ml and v2v.ml
I'm interested to hear opinions on whether this makes the code
clearer, or not.
This is virt-v2v, but many other virt-* tools work the same way, and
analogous changes could be made.
Currently when command line argument parsing is done in 'cmdline.ml'
the list of parsed parameters is passed to the main program in a very
long tuple. Each parameter is strongly typed, but not named (so
2018 Mar 23
2
[PATCH] v2v: ova: convert E1000 network interfaces as such
So far v2v did not read the model of network interfaces, resulting in
"virtio" as the model for such interfaces.
Start reading the model, if available, mapping only E1000 for now.
There are also other models, e.g. PCNet32 or VmxNet3, but they are
ignored for now: reading them as Source_other_nic would result in v2v
rejecting OVAs previously converted.
---
v2v/parse_ovf_from_ova.ml
2016 Apr 11
0
[PATCH] v2v: Reject duplicate -b/-n parameters on the command line (RHBZ#1325825).
---
v2v/Makefile.am | 3 +-
v2v/cmdline.ml | 31 ++++++++++++++------
v2v/cmdline.mli | 16 ++++++++++-
v2v/test-v2v-bad-networks-and-bridges.sh | 49 ++++++++++++++++++++++++++++++++
v2v/v2v.ml | 4 +--
5 files changed, 91 insertions(+), 12 deletions(-)
create mode 100755
2015 Aug 11
41
[PATCH v2 00/17] v2v: add --in-place mode
This series is a second attempt to add a mode of virt-v2v operation
where it leaves the config and disk image conversion, rollback on
errors, registering with the destination hypervisor, etc. to a
third-party toolset, and performs only tuning of the guest OS to run in
the KVM-based hypervisor.
The first 14 patches are just refactoring and rearrangement of the code,
factoring the implementation
2018 Mar 16
7
[PATCH v2 0/5] Add --print-target with machine-readable version.
This adds --print-target. In addition, v2 provides a machine-readable
version (in JSON format).
All of the record -> JSON boilerplate in this patch could be
eliminated if we moved the baseline to OCaml 4.02.
Rich.
2016 Feb 09
0
[PATCH 1/4] v2v: collect source network and video adapter types
Those will be useful when making decisions about what configuration to
set on output.
The data is also included in --print-source so the tests are adjusted
accordingly.
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---
test-data/phony-guests/guests.xml.in | 8 ++++++++
v2v/input_disk.ml | 2 ++
v2v/input_libvirtxml.ml | 32
2016 Mar 18
0
[PATCH v4 1/5] v2v: collect source network and video adapter types
Those will be useful when making decisions about what configuration to
set on output.
The data is also included in --print-source so the tests are adjusted
accordingly.
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---
test-data/phony-guests/guests.xml.in | 8 ++++++++
v2v/input_disk.ml | 2 ++
v2v/input_libvirtxml.ml | 27
2016 Feb 20
0
[PATCH v2 1/4] v2v: collect source network and video adapter types
Those will be useful when making decisions about what configuration to
set on output.
The data is also included in --print-source so the tests are adjusted
accordingly.
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---
Notes:
v2:
- add catch-all string-valued variants for source network and video adapter
models
test-data/phony-guests/guests.xml.in | 8 ++++++++
2019 Apr 16
6
[PATCH v2v v2 2/2] v2v: Copy static IP address information.
Essentially identical to v1 except that it now uses (overloads?)
the --mac option to supply this data.
Rich.
2018 Mar 22
1
[PATCH] v2v: Fix parsing of OVA files and documentation for --network and --bridge (RHBZ#1559027).
When parsing OVA files we have to work backwards to whether the
original VMware object was a network or a bridge. It seems as if the
presence of <rasd:Connection> is sufficient. I dropped the use of
<rasd:ElementName> since it is literally just an internal name for the
network element, and is not significant in how the network is used.
Also update documentation because you must use
2019 Jul 11
2
[PATCH v3 0/2] v2v: Copy static IP address information over for Windows guests
Patch v2 was here:
https://www.redhat.com/archives/libguestfs/2019-April/thread.html#00114
There's no change here except that I've rebased it against the latest
master branch and retested. There was a comment by Pino
(https://www.redhat.com/archives/libguestfs/2019-April/msg00117.html)
which isn't incorporated into this patch.
Rich.
2015 Aug 11
0
[PATCH v2 02/17] v2v: factor out opening input VM
Opening the source VM and amending the properties in its internal
representation in accordance with command-line options fit nicely into
two isolated functions.
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---
v2v/v2v.ml | 71 +++++++++++++++++++++++++++++++++-----------------------------
1 file changed, 38 insertions(+), 33 deletions(-)
diff --git a/v2v/v2v.ml b/v2v/v2v.ml
index
2016 Apr 26
4
v2v: Remove --no-trim, --vmtype options and other fixes.
The first two patches implement the change discussed here:
https://www.redhat.com/archives/libguestfs/2016-April/msg00178.html
The third patch fixes the mapping of inspection data to OVF VmType
which was inherited directly from old virt-v2v and had never been
changed. It had a number of problems.
The fourth patch is only slightly related to the others. It adds an
extra slow test to ensure that
2017 Mar 13
4
[PATCH 0/2] v2v: -i ova: A couple of cleanup patches.
A couple of patches cleaning up the -i ova code. These are
both just refactoring (or should be at any rate).
The second patch is best viewed with 'git show -w' to exclude
whitespace changes.
Rich.