On Fri, Jan 24, 2020 at 10:39:20AM -0500, Laine Stump wrote: > Aside from itinerant error (actually warning) messages due to an > unrecognized response from qemu, this isn't even necessary - the > migration proceeds successfully to completion anyway. > > (I'm not sure where to see this status reported in the API though - do > we need to add an extra state, or recognition of a new event somewhere?) > > Signed-off-by: Laine Stump <laine@xxxxxxxxxx> > --- > src/qemu/qemu_migration.c | 1 + > src/qemu/qemu_monitor.c | 1 + > src/qemu/qemu_monitor.h | 1 + > src/qemu/qemu_monitor_json.c | 1 + > 4 files changed, 4 insertions(+) Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
