[libvirt] [PATCH v2 19/22] qemu: Work around weired migration status changes

Peter Krempa pkrempa at redhat.com
Wed Jun 10 11:06:03 UTC 2015


On Tue, Jun 02, 2015 at 14:34:24 +0200, Jiri Denemark wrote:
> When cancelling migration we can see the following conversation on QMP
> monitor:
> 
> {"execute":"migrate_cancel","id":"libvirt-33"}
> {"timestamp": {"seconds": 1432899178, "microseconds": 844907}, "event":
> "MIGRATION", "data": {"status": "cancelling"}}
> {"return": {}, "id": "libvirt-33"}
> {"timestamp": {"seconds": 1432899178, "microseconds": 845625}, "event":
> "MIGRATION", "data": {"status": "failed"}}
> {"timestamp": {"seconds": 1432899178, "microseconds": 846432}, "event":
> "MIGRATION", "data": {"status": "cancelled"}}
> 
> That is, migration status first changes to "failed" just to change to
> the correct "cancelled" state in a few moments later. However, this is
> enough to let libvirt report migration failed for unknown reason instead
> of having been cancelled by a user.
> 
> This should really be fixed in QEMU but I'm not sure how easy it is.

Is qemu going to fix it? I'd rather see it done that way rather than
fixing it up in libvirt.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20150610/e4a21195/attachment-0001.sig>


More information about the libvir-list mailing list