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.
> 
> suspicion£º
> ```
>        if shell_command cmd <> 0 then
>          error (f_"ssh copy command failed, see earlier errors");
> ```
> 
> detail£º
> ```
> shell > virt-v2v-copy-to-local -v -ic xen+ssh://myxen_server guest
> [   0.0] Fetching the remote libvirt XML metadata ...
> [   1.6] Parsing the remote libvirt XML metadata ...
> [   1.6] Copying remote disk 1/2 to guest-disk1
> dd: invalid status flag: ¡®progress¡¯
> Try 'dd --help' for more information.
> 40960+0 records in
> 40960+0 records out
> 42949672960 bytes (43 GB) copied, 876.05 seconds, 49.0 MB/s
> virt-v2v-copy-to-local: error: ssh copy command failed, see earlier errors
> 
> ```

This feature was added to the dd command in coreutils in Sept 2014,
nearly 4 years ago.

Which Linux distribution are you using?

Rich.

-----------------------------------------------------------------