Displaying 20 results from an estimated 6000 matches similar to: "[PATCH] Documentation: Cleanup virt-v2v.conf references and mention --network"
2010 Mar 31
1
[PATCH] Documentation: Update virt-v2v pod for RHEV export and IDE default
---
v2v/virt-v2v.pl | 140 ++++++++++++++++++++++++++++++++++++++++---------------
1 files changed, 102 insertions(+), 38 deletions(-)
diff --git a/v2v/virt-v2v.pl b/v2v/virt-v2v.pl
index c1a4728..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
2016 Oct 05
2
Re: libvirt-v2v error
Hi Richard,
That didn't resolve the issue. Now I'm getting the following error. Please
advice.
*[root@kvm16 ~]#* virt-v2v -ic esx://10.16.32.13/?no_verify=1 yardqakvm -o
rhev -os 10.16.32.16:/vm-images/export_domain --network rhevm
libvirt error code: 42, message: Domain not found: No domain with name
'yardqakvm'
2016 Oct 05
0
Re: libvirt-v2v error
On Thu, Oct 06, 2016 at 12:58:25AM +0530, Saman Bandara wrote:
> Hi Richard,
>
> That didn't resolve the issue. Now I'm getting the following error. Please
> advice.
>
> *[root@kvm16 ~]#* virt-v2v -ic esx://10.16.32.13/?no_verify=1 yardqakvm -o
> rhev -os 10.16.32.16:/vm-images/export_domain --network rhevm
>
> libvirt error code: 42, message: Domain not
2016 Oct 05
3
libvirt-v2v error
Dear sir,
I'm getting following error while trying to convert a VMWare RHEL6 server
to kvm.
Please give any suggestion to resolve this.
[root@kvm16 ~]# virt-v2v ic esx://10.16.32.12/?no_verify=1 -o rhev -os
10.16.32.16:/vm-images/export_domain --network rhevm "10.16.32.36-db-
slcloudcontrol"
virt-v2v: Failed to connect to qemu:///system: libvirt error code: 45,
message:
2017 Mar 06
1
[PATCH] v2v, p2v: rename rhvm network to ovirtmgmt (RHBZ#1429491)
Since RHV 3.6.10, the default network name is 'ovirtmgmt' instead of
'rhvm'.
This is just a documentation change.
---
p2v/virt-p2v.pod | 10 +++++-----
v2v/cmdline.ml | 2 +-
v2v/virt-v2v.pod | 12 ++++++------
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/p2v/virt-p2v.pod b/p2v/virt-p2v.pod
index ea685be..4a5f587 100644
--- a/p2v/virt-p2v.pod
+++
2016 Dec 01
2
[PATCH] v2v: Rename RHEV to RHV throughout.
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
2016 Dec 07
0
[PATCH v2] v2v: Rename RHEV to RHV throughout.
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
2011 Nov 25
1
[virt-tools-list] virt-v2v rhev import error
On Tue, Nov 22, 2011 at 08:03:15PM +0000, Wandell, Doug wrote:
> Image is a prebuilt VMWare image from Layer7. Downloaded and converted under RHEL6 like this:
>
> virt-convert --arch=x86_64 SSG_64bit_VirtualAppliance_v6.1/ SSG_64bit_VirtualAppliance_v6.1.xml
> qemu-img convert -O qcow2 SSG_64bit_VirtualAppliance_v6.1.raw SSG_64bit_VirtualAppliance_v6.1.qcow2
>
> No problem. I
2010 Sep 21
1
[PREVIEW ONLY] Refactor data transfer code
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
2010 Mar 31
1
[PATCH] Add LocalCopy transfer method to transfer local files to a target
Also changes command line parsing to require 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
2013 Nov 15
2
Virtio: 32bit CentOS 6.4 on VirtualBox to oVirt on Fedora 19 64bit via virt-v2v
Hello,
I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on
Fedora 19 64bit via virt-v2v. The command I'm currently using is:
virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd
xxx.xxx.xxx.xxx:/usr/local/ovirt/exports --network
ovirtmgmt /usr1/home/williams/Downloads/OpenAthens/VMs/OpenAthensLARuntime2.2.xml
The exciting bit of the XML is:
<devices>
2016 Oct 05
0
Re: libvirt-v2v error
On Wed, Oct 05, 2016 at 04:11:20PM +0530, Saman Bandara wrote:
> Dear sir,
>
> I'm getting following error while trying to convert a VMWare RHEL6 server
> to kvm.
> Please give any suggestion to resolve this.
>
> [root@kvm16 ~]# virt-v2v ic esx://10.16.32.12/?no_verify=1 -o rhev -os
> 10.16.32.16:/vm-images/export_domain --network rhevm "10.16.32.36-db-
>
2013 Nov 15
1
Re: Virtio: 32bit CentOS 6.4 on VirtualBox to oVirt on Fedora 19 64bit via virt-v2v
Matt,
On Fri, 2013-11-15 at 14:05 +0000, Matthew Booth wrote:
> On Fri, 2013-11-15 at 10:47 +0000, Owen Williams wrote:
> > Hello,
> > I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on
> > Fedora 19 64bit via virt-v2v. The command I'm currently using is:
> >
> > virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd
> >
2018 Nov 01
0
[PATCH] v2v: copy-to-local: Remove references to using this tool for ESXi.
virt-v2v is capable of accessing ESXi hypervisors now. There is only
one remaining use of this tool - when converting from Xen hypervisors
over ssh which are using host block devices for storage.
---
v2v/virt-v2v-copy-to-local.pod | 27 ++-------------------------
1 file changed, 2 insertions(+), 25 deletions(-)
diff --git a/v2v/virt-v2v-copy-to-local.pod b/v2v/virt-v2v-copy-to-local.pod
index
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
2013 Nov 15
0
Re: Virtio: 32bit CentOS 6.4 on VirtualBox to oVirt on Fedora 19 64bit via virt-v2v
On Fri, 2013-11-15 at 10:47 +0000, Owen Williams wrote:
> Hello,
> I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on
> Fedora 19 64bit via virt-v2v. The command I'm currently using is:
>
> virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd
> xxx.xxx.xxx.xxx:/usr/local/ovirt/exports --network
> ovirtmgmt
2015 Jul 28
0
Re: [PATCH] v2v: add --in-place mode
On Mon, Jul 27, 2015 at 07:29:57PM +0300, Roman Kagan wrote:
> In this mode, converting of the VM configuration, setting up the
> rollback path for error cases, transforming the VM storage and so on is
> taken care of by a third-party toolset, and virt-v2v is only supposed to
> tune up the guest OS directly inside the source VM, to enable it to boot
> and run under the input
2016 Jul 19
0
[PATCH v2 2/2] v2v: use Getopt.Symbol for few options
Use Getopt.Symbol for options with a fixed list of choices, so there is
no need to check them on our own.
---
v2v/cmdline.ml | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/v2v/cmdline.ml b/v2v/cmdline.ml
index 2d0a10a..96e0509 100644
--- a/v2v/cmdline.ml
+++ b/v2v/cmdline.ml
@@ -83,8 +83,7 @@ let parse_cmdline () =
| "libvirt" -> input_mode
2014 Sep 16
2
Re: virt-v2v -ic question
On 16.09.14 14:21, Richard W.M. Jones wrote:
> On Tue, Sep 16, 2014 at 04:04:02PM +0300, Shahar Havivi wrote:
> > Hi,
> >
> > I am trying to convert from esx server to local directory a VM names CSB,
> > Its build from source 77b371b18b6a7ad37105a595931514f542a04396
> >
> > When running:
> > LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic
2015 Jul 27
4
[PATCH] v2v: add --in-place mode
In this mode, converting of the VM configuration, setting up the
rollback path for error cases, transforming the VM storage and so on is
taken care of by a third-party toolset, and virt-v2v is only supposed to
tune up the guest OS directly inside the source VM, to enable it to boot
and run under the input hypervisor.
Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
---