On 11/03/2015 04:56 AM, zhanghailiang wrote: > Add a migrate state: MIGRATION_STATUS_COLO, enter this migration state > after the first live migration successfully finished. > > We reuse migration thread, so if colo is enabled by user, migration thread will > go into the process of colo. > > Signed-off-by: zhanghailiang > Signed-off-by: Li Zhijian > Signed-off-by: Gonglei > --- > v10: Simplify process by dropping colo thread and reusing migration thread. > (Dave's suggestion) > --- > +++ b/qapi-schema.json > @@ -439,7 +439,7 @@ > ## > { 'enum': 'MigrationStatus', > 'data': [ 'none', 'setup', 'cancelling', 'cancelled', > - 'active', 'completed', 'failed' ] } > + 'active', 'completed', 'failed', 'colo' ] } > Missing documentation of the new state, including a '(since 2.6)' tag. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org