Re: [Libguestfs] [PATCH] p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).

2018-06-12 Thread Pino Toscano
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 mapping this to

[Libguestfs] Fwd: virt-v2v-copy-to-local failed if dd does not support status=progress

2018-06-12 Thread Richard W.M. Jones
On Tue, Jun 12, 2018 at 04:51:57AM -0700, zhujinhe wrote: > If dd does not support status=progress, copy process will abort at the > end. This is totally misguided. > We can use -q as a workaround in this circumstance, but it is frightening to > newbee like me. Maybe we should improve this. >

Re: [Libguestfs] Fwd: virt-v2v-copy-to-local failed if dd does not support status=progress

2018-06-12 Thread Richard W.M. Jones
On Tue, Jun 12, 2018 at 04:51:57AM -0700, zhujinhe wrote: > If dd does not support status=progress, copy process will abort at the > end. This is totally misguided. > We can use -q as a workaround in this circumstance, but it is frightening to > newbee like me. Maybe we should improve this. >

Re: [Libguestfs] [PATCH] p2v: Allow virt-v2v input and output drivers containing '-' (RHBZ#1590220).

2018-06-12 Thread Richard W.M. Jones
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