Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-30 Thread Peter Xu
On Tue, Jan 30, 2024 at 10:58:24AM -0300, Fabiano Rosas wrote: > Peter Xu writes: > > > On Mon, Jan 29, 2024 at 10:44:46AM -0300, Fabiano Rosas wrote: > >> > Since we're at it, I would also like to know how you think about whether > >> > we > >> > should still suggest people using VMSD versionin

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-30 Thread Fabiano Rosas
Peter Xu writes: > On Mon, Jan 29, 2024 at 10:44:46AM -0300, Fabiano Rosas wrote: >> > Since we're at it, I would also like to know how you think about whether we >> > should still suggest people using VMSD versioning, as we know that it won't >> > work for backward migrations. >> > >> > My curre

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-29 Thread Peter Xu
On Mon, Jan 29, 2024 at 03:51:07PM +, Peter Maydell wrote: > On Mon, 29 Jan 2024 at 15:18, Fabiano Rosas wrote: > > > > Peter Maydell writes: > > > > > On Mon, 29 Jan 2024 at 13:45, Fabiano Rosas wrote: > > >> > > >> Peter Xu writes: > > >> > Fundamentally, IMHO it's because QEMU as a proje

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-29 Thread Peter Xu
On Mon, Jan 29, 2024 at 10:44:46AM -0300, Fabiano Rosas wrote: > > Since we're at it, I would also like to know how you think about whether we > > should still suggest people using VMSD versioning, as we know that it won't > > work for backward migrations. > > > > My current thoughts is it is still

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-29 Thread Peter Maydell
On Mon, 29 Jan 2024 at 15:18, Fabiano Rosas wrote: > > Peter Maydell writes: > > > On Mon, 29 Jan 2024 at 13:45, Fabiano Rosas wrote: > >> > >> Peter Xu writes: > >> > Fundamentally, IMHO it's because QEMU as a project is used both in > >> > enterprise and personal emulations. I think it might

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-29 Thread Fabiano Rosas
Peter Maydell writes: > On Mon, 29 Jan 2024 at 13:45, Fabiano Rosas wrote: >> >> Peter Xu writes: >> > Fundamentally, IMHO it's because QEMU as a project is used both in >> > enterprise and personal emulations. I think it might be too strict to >> > always request backward migration capability

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-29 Thread Peter Maydell
On Mon, 29 Jan 2024 at 13:45, Fabiano Rosas wrote: > > Peter Xu writes: > > Fundamentally, IMHO it's because QEMU as a project is used both in > > enterprise and personal emulations. I think it might be too strict to > > always request backward migration capability if we know some device / arch

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-29 Thread Fabiano Rosas
Peter Xu writes: > On Mon, Jan 22, 2024 at 12:39:06PM -0300, Fabiano Rosas wrote: >> pet...@redhat.com writes: >> >> > From: Peter Xu >> > >> > The current article is not extremely easy to follow, and may contain too >> > much information for someone looking for solutions on VMSD compatibility

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-22 Thread Peter Xu
On Mon, Jan 22, 2024 at 12:39:06PM -0300, Fabiano Rosas wrote: > pet...@redhat.com writes: > > > From: Peter Xu > > > > The current article is not extremely easy to follow, and may contain too > > much information for someone looking for solutions on VMSD compatibility > > issues. Meanwhile, VMS

Re: [PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-22 Thread Fabiano Rosas
pet...@redhat.com writes: > From: Peter Xu > > The current article is not extremely easy to follow, and may contain too > much information for someone looking for solutions on VMSD compatibility > issues. Meanwhile, VMSD versioning is not discussed. > > I'm not yet sure whether we should just ob

[PATCH] migration/docs: Explain two solutions for VMSD compatibility

2024-01-21 Thread peterx
From: Peter Xu The current article is not extremely easy to follow, and may contain too much information for someone looking for solutions on VMSD compatibility issues. Meanwhile, VMSD versioning is not discussed. I'm not yet sure whether we should just obsolete VMSD versioning; it's still used