On Fri, Oct 18, 2019 at 15:00:19 +0800, Luyao Zhong wrote: I'm assuming you are not asking about post-copy migration, since it is a bit more complicated as the current state if split between the source and destination hosts and none of them can keep running without the other until migration finishes. No, the domain will keep running on the source host and disappear from the destination host. You can use this combination, but it most likely doesn't make sense. Usually you would do live migration to minimize downtime. But VIR_MIGRATE_PAUSED would cause the domain not to be automatically resumed after migration so the downtime will likely be even longer than with non-live migration (until the user manually resumes the domain on destination). That said, the live and non-live migration when VIR_MIGRATE_PAUSED is used (for both of them) differ only in the moment the domain is paused. With non-live migration the domain is paused at the beginning of migration, while with live migration the domain keeps running during migration and it is paused once migration is almost done. No. It means that if migration succeeds, the domain will remain paused on the destination (while normally it would be running at that point). The flag has no effect if the migration fails. Jirka