similar to: few things I found about virt-p2v

On Sat, Mar 30, 2019 at 4:23 PM Richard W.M. Jones <rjones@redhat.com> wrote: > [Please keep replies on the list] > I wasn't approved yet by moderator ;) > > > > 4. Looks like there is no way to type a pool name to export to > (if I > > > > select libvirt) or am I missing something? (let's say I have a > pool > > > called >

> > > > I did, and I'm enclosing gzipped copy of the file. Line 4197 clearly > shows > > it got the correct parameter: > > Initializing the target -o libvirt -os NAS-10G > > Ah I see. This is a limitation: > > > https://github.com/libguestfs/libguestfs/blob/f79129b8dc92470e3a5597daf53c84038bd6859e/v2v/output_libvirt.ml#L107 > > I see. This

On Sat, Mar 30, 2019 at 05:19:55PM +0300, Hetz Ben Hamo wrote: > > > > > > > I did, and I'm enclosing gzipped copy of the file. Line 4197 clearly > > shows > > > it got the correct parameter: > > > Initializing the target -o libvirt -os NAS-10G > > > > Ah I see. This is a limitation: > > > > > >

On Sat, Mar 30, 2019 at 04:32:31PM +0300, Hetz Ben Hamo wrote: > On Sat, Mar 30, 2019 at 4:23 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > > It could well be a bug, but take a look at the virt-p2v logs which are > > saved under /tmp/virt-p2v-* on the conversion server. That will tell > > you what exact command line was used. > > > > I did, and

[Please keep replies on the list] On Sat, Mar 30, 2019 at 02:24:36PM +0300, Hetz Ben Hamo wrote: > > > I spent the last few hours playing with virt-p2v, and here are few things > > > that I found, please tell me on which to submit a bug report: > > > > > > 1. I created a boot image (without any parameters) and tested it using > > > virt-manager.

Hi, Small questoin: when running the P2v hard disk image, and I want to convert a phyical machine to oVirt, to which machine do I connect when the GUI starts? one of the nodes or the hosted engine? (i'm not talking about the URL). Thanks

v1 was here: https://www.redhat.com/archives/libguestfs/2018-June/msg00047.html v1 -> v2: - Add a regular expression in the virt-v2v modules code too. - - - I was planning a much more ambitious second version of this patch (half written too) which had: virt-v2v --describe-modules that listed a big chunk of XML which virt-p2v would parse. These would include the names of the

The new ‘-o rhv-upload’ output mode contains a '-' character in the name, but the regular expression which matched the output of the virt-v2v command did not recognize '-' as a valid character. It ended up mapping this to just "rhv" meaning two "rhv" entries would appear in the list of output drivers. Thanks: Ming Xie. --- p2v/ssh.c | 4 ++-- 1 file changed,

On Tue, Jun 12, 2018 at 12:13:32PM +0200, Pino Toscano wrote: > On Tuesday, 12 June 2018 11:27:56 CEST Richard W.M. Jones wrote: > > The new ‘-o rhv-upload’ output mode contains a '-' character in the > > name, but the regular expression which matched the output of the > > virt-v2v command did not recognize '-' as a valid character. It ended > > up

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1792141 Let the user pass "-oo" options from the kernel cmdline and from the GUI to virt-v2v. This is primarily useful with the OpenStack output mode, so reenable that mode. Cc: Alban Lecorps <alban.lecorps at ubisoft.com> Laszlo Alban Lecorps (1): Introduce "p2v.output.misc" for passing "-oo" options

The 'rhv-upload' output mode requires few options, and virt-p2v does not have the GUI bits for specifying them. --- ssh.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/ssh.c b/ssh.c index 7d85b40..99eefbd 100644 --- a/ssh.c +++ b/ssh.c @@ -1022,8 +1022,12 @@ add_input_driver (const char *name, size_t len) static void add_output_driver (const char *name,

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

Add a minimal release note text for the first standalone version, virt-p2v 1.41.0; in addition, add the first items for the future 1.42.0. --- docs/p2v-release-notes.pod | 32 ++++++++++++++++++++++++++------ 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/docs/p2v-release-notes.pod b/docs/p2v-release-notes.pod index ee0dd98..21d736d 100644 --- a/docs/p2v-release-notes.pod +++

This patch is incomplete, but early feedback would be welcome. Rich.

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 +++

Hi Jiffin, I looked at the document, and there are 2 things: 1. In Gluster 3.8 it seems you don't need to do that at all, it creates this automatically, so why not in 3.10? 2. The step by step guide, in the last item, doesn't say where exactly do I need to create the nfs-ganesha directory. The copy/paste seems irrelevant as enabling nfs-ganesha creates automatically the ganesha.conf and

Hi, I'm setting up gluster on a 2 node system. The setup is working, I configured pcsd and it's working, and I added the virtual_IP resource. However, on many examples on the net (for example: the output in this thread: https://www.centos.org/forums/viewtopic.php?t=60001 ) I see few resources in the pcs. Is this something which is being created automatically? or is it something that I

Both BaseOS and AppStream are needed. --- virt-p2v-make-kickstart.in | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/virt-p2v-make-kickstart.in b/virt-p2v-make-kickstart.in index 779ba62..cbbfb8a 100644 --- a/virt-p2v-make-kickstart.in +++ b/virt-p2v-make-kickstart.in @@ -176,6 +176,16 @@ repo --name=rhel6_${minor}_server_optional --baseurl=$baseurl/Server/optional/$a

Hello, Answers below : Le 13/11/2014 16:06, Richard W.M. Jones a écrit : >>>> This is the last thing it does before unwinding: >>>> >>>> libguestfs: trace: cp "/transferxdTiHj/windows/rhev-apt.exe" "/Program >>>> Files/RedHat/V2V Firstboot" >>>> libguestfs: trace: cp = 0 >>>> >>>> So, maybe

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.