[libvirt-users] Why cannot block copy local storage to network disk

[Martin Kletzander]

On Tue, Jul 18, 2017 at 06:06:45PM +0800, wyang wrote:
>Hi, guys
>
>I was executing the following command to lively migrate local storage to
>network storage,
>
>    [root at 192-168-152-51 ~]# virsh blockcopy
>    a75056a4-44e0-4b97-bc77-78142ee17038 vda —xml rbd.xml —wait —verbose
>    —pivot
>    error: argument unsupported: non-file destination not supported yet
>
>but I get the following error:
>
>    error: argument unsupported: non-file destination not supported yet
>
>I check my libvirt source code, and find the following code sniff in
>/qemuDomainBlockCopyCommon/ function
>
>|if (!virStorageSourceIsLocalStorage(mirror)) {
>virReportError(VIR_ERR_ARGUMENT_UNSUPPORTED, "%s", _("non-file
>destination not supported yet")); } |
>
>it was introduced by Eric.
>
>    commit e53ee6c123321a1775ef3b36e15a5fa351d10fe4
>    Author: Eric Blake eblake at redhat.com <http://mailto:eblake@redhat.com>
>    Date: Fri Aug 29 16:30:46 2014 -0600
>
>    blockcopy: tweak how rebase calls into copy
>
>So my question is that why we cannot block copy to network storage?
>

The answer is in the commit message.  It was not supported even before
the commit, it's just that now it needs to be explicitly checked.  IIUC,
before that commit the stat() call would just fail. It's just that
nobody implemented it yet.  Having said that, I'm unaware of the actual
limitations that there are.

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20170718/c975639f/attachment.sig>