[libvirt] [PATCH/RFC] Introduce VIR_MIGRATE_FORCE flag to allow for risky migration

Guido Günther agx at sigxcpu.org
Fri Oct 21 18:16:24 UTC 2011


Hi,
Migration will be disallowed when the vm uses host devices or has
snapshots (qemuMigrationIsAllowed)[1]. Would it make sense to introduce
a VIR_MIGRATE_FORCE similar to VIR_REVERT_FORCE here?  We could then
introduce error codes similar to the snapshot case
(VIR_ERR_MIGRATE_RISKY).

This path is just to illustrate the idea not to be applied as is.
Cheers,
 -- Guido

[1] Hopefully we can make migration with snapshots safe in the future by
transfering the metadata. A current hack around is to put this onto
shared storage and reread it on the destination side after migration.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Introduce-VIR_MIGRATE_FORCE-flag-to-allow-for-risky-.patch
Type: text/x-diff
Size: 12129 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20111021/629280c2/attachment-0001.bin>


More information about the libvir-list mailing list