On Wed, Jun 10, 2015 at 13:06:03 +0200, Peter Krempa wrote:
> 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.
Yeah, Juan said he would fix it in the next version of his series.
Jirka
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list