10 Nov
2014
10 Nov
'14
5:05 p.m.
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 remain turned on with no way to turn them off. To fix that, migration capabilities have to be turned on if requested but explicitly turned off in case they were not requested but QEMU supports them.
Oops, wrong bug number, I'll provide a new one once I found it... Jirka