[libvirt] [RFC] Introduce virDomainBlockCopy API

Daniel P. Berrange berrange at redhat.com
Tue Jun 21 09:48:38 UTC 2011

On Mon, Jun 20, 2011 at 08:15:24PM +0200, Jiri Denemark wrote:
> This API starts asynchronous live copy of a block device (specified by
> target element of the xml argument) into a new source (which must
> already exist). The process can be controlled in the same way as
> migration: monitored with virDomainJobInfo() and canceled using
> virDomainAbortJob().
> I don't particularly like the name (but I wasn't able to come up with a
> better one) since it doesn't reflect the fact that once a block device
> is switched to use the new source once copying finishes. In other words,
> the goal of this API is to update the device to use new source (just
> like virDomainUpdateDeviceFlags) but before doing so all data is copied
> from the old source into the new one (unlike the UpdateDevice API).

How is this functionality different from the virDomainBlockPull
APIs we just added from Adam. From this description, it sounds
practically identical, except it only allows one job to be run
at a time, instead of allowing many.

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

More information about the libvir-list mailing list