On Tue, Nov 11, 2014 at 16:16:22 +0100, Jano Tomko wrote:
On 11/10/2014 04:41 PM, Jiri Denemark wrote:
We used to set migration capabilities only when a user asked for them in
flags. This is fine when migration succeeds since the QEMU process is
killed in the end but in case migration fails
On 11/10/2014 04:41 PM, Jiri Denemark wrote:
We used to set migration capabilities only when a user asked for them in
flags. This is fine when migration succeeds since the QEMU process is
killed in the end but in case migration fails or if it's cancelled, some
capabilities may remain turned on
We used to set migration capabilities only when a user asked for them in
flags. This is fine when migration succeeds since the QEMU process is
killed in the end but in case migration fails or if it's cancelled, some
capabilities may remain turned on with no way to turn them off. To fix
that,
On Mon, Nov 10, 2014 at 16:41:23 +0100, Jiri Denemark wrote:
We used to set migration capabilities only when a user asked for them in
flags. This is fine when migration succeeds since the QEMU process is
killed in the end but in case migration fails or if it's cancelled, some
capabilities may
