Re: [PATCH v3 1/3] migration: Add documentation for backwards compatiblity

2023-10-23 Thread Juan Quintela
Peter Xu wrote: > On Mon, May 15, 2023 at 10:31:59AM +0200, Juan Quintela wrote: [..] >> +When we do migration, we have to QEMU process: the source and the > > s/to/two/, s/process/processes/ done. >> +target. There are two cases, they are the same version or they are a >> +different version.

Re: [PATCH v3 1/3] migration: Add documentation for backwards compatiblity

2023-10-17 Thread Juan Quintela
Xiaoyao Li wrote: > On 5/17/2023 7:39 AM, Peter Xu wrote: >> On Mon, May 15, 2023 at 10:31:59AM +0200, Juan Quintela wrote: >>> +Now we start with the more interesting cases. Consider the case where >>> +we have the same QEMU version in both sides (qemu-5.2) but we are using > > s/we are using/we

Re: [PATCH v3 1/3] migration: Add documentation for backwards compatiblity

2023-05-17 Thread Xiaoyao Li
On 5/17/2023 7:39 AM, Peter Xu wrote: On Mon, May 15, 2023 at 10:31:59AM +0200, Juan Quintela wrote: State what are the requeriments to get migration working between qemu versions. And once there explain how one is supposed to implement a new feature/default value and not break migration. Revi

Re: [PATCH v3 1/3] migration: Add documentation for backwards compatiblity

2023-05-16 Thread Peter Xu
On Mon, May 15, 2023 at 10:31:59AM +0200, Juan Quintela wrote: > State what are the requeriments to get migration working between qemu > versions. And once there explain how one is supposed to implement a > new feature/default value and not break migration. > > Reviewed-by: Vladimir Sementsov-Ogi

[PATCH v3 1/3] migration: Add documentation for backwards compatiblity

2023-05-15 Thread Juan Quintela
State what are the requeriments to get migration working between qemu versions. And once there explain how one is supposed to implement a new feature/default value and not break migration. Reviewed-by: Vladimir Sementsov-Ogievskiy Message-Id: <20230511082701.12828-1-quint...@redhat.com> Signed-o