Re: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-09 Thread Juan Quintela
Vladimir Sementsov-Ogievskiy wrote: > We generally require same set of capabilities on source and target. > Let's require x-colo capability to use COLO on target. > > Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Juan Quintela I will update the docs as said by lukas. > --- > migra

RE: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-05 Thread Zhang, Chen
> -Original Message- > From: Lukas Straub > Sent: Friday, May 5, 2023 6:46 AM > To: Vladimir Sementsov-Ogievskiy > Cc: qemu-devel@nongnu.org; quint...@redhat.com; Zhang, Chen > ; Peter Xu ; Leonardo Bras > > Subject: Re: [PATCH v4 10/10] migration: block incom

Re: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-04 Thread Lukas Straub
On Fri, 5 May 2023 01:30:34 +0300 Vladimir Sementsov-Ogievskiy wrote: > On 05.05.23 01:10, Lukas Straub wrote: > > On Fri, 28 Apr 2023 22:49:28 +0300 > > Vladimir Sementsov-Ogievskiy wrote: > > > >> We generally require same set of capabilities on source and target. > >> Let's require x-colo

Re: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-04 Thread Vladimir Sementsov-Ogievskiy
On 05.05.23 01:10, Lukas Straub wrote: On Fri, 28 Apr 2023 22:49:28 +0300 Vladimir Sementsov-Ogievskiy wrote: We generally require same set of capabilities on source and target. Let's require x-colo capability to use COLO on target. Signed-off-by: Vladimir Sementsov-Ogievskiy Good patch, t

Re: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-04 Thread Lukas Straub
On Fri, 28 Apr 2023 22:49:28 +0300 Vladimir Sementsov-Ogievskiy wrote: > We generally require same set of capabilities on source and target. > Let's require x-colo capability to use COLO on target. > > Signed-off-by: Vladimir Sementsov-Ogievskiy Good patch, this is needed anyway for COLO with

RE: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-04 Thread Zhang, Chen
ATCH v4 10/10] migration: block incoming colo when capability is > disabled > > We generally require same set of capabilities on source and target. > Let's require x-colo capability to use COLO on target. > > Signed-off-by: Vladimir Sementsov-Ogievskiy > Reviewed-by: Zhang

Re: [PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-05-02 Thread Peter Xu
On Fri, Apr 28, 2023 at 10:49:28PM +0300, Vladimir Sementsov-Ogievskiy wrote: > We generally require same set of capabilities on source and target. > Let's require x-colo capability to use COLO on target. > > Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Peter Xu -- Peter Xu

[PATCH v4 10/10] migration: block incoming colo when capability is disabled

2023-04-28 Thread Vladimir Sementsov-Ogievskiy
We generally require same set of capabilities on source and target. Let's require x-colo capability to use COLO on target. Signed-off-by: Vladimir Sementsov-Ogievskiy --- migration/migration.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/migration/migration.c b/migration/migration.c