From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Bernhard Beschow" <shentey@gmail.com>,
pbonzini@redhat.com, devel@lists.libvirt.org,
richard.henderson@linaro.org, mst@redhat.com,
qemu-trivial@nongnu.org
Subject: Re: [PATCH for-9.0] docs/about: Mark the iaspc machine type as deprecated
Date: Wed, 27 Mar 2024 13:29:22 +0000 [thread overview]
Message-ID: <ZgQfMq2gJuWurl3K@redhat.com> (raw)
In-Reply-To: <CAFEAcA-K30KZndNK-sfUKjsE7ATMNpNUgpPZY-5YEpxL3BoeLA@mail.gmail.com>
On Wed, Mar 27, 2024 at 01:27:58PM +0000, Peter Maydell wrote:
> On Wed, 27 Mar 2024 at 13:23, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Wed, Mar 27, 2024 at 02:09:17PM +0100, Igor Mammedov wrote:
> > > On Wed, 27 Mar 2024 10:49:43 +0000
> > > Daniel P. Berrangé <berrange@redhat.com> wrote:
> > > It's question of whether we are willing to do unthinkable,
> > > i.e. to break QEMU <-> guest ABI for isapc case by removing
> > > corresponding fwcfg entries.
> >
> > There has never been any ABI stability requirement for 'isapc'
> > as it is not a versioned machine type.
> >
> > > With migration ignored it shouldn't be a problem.
> > > Question is: does anyone care about migration with isapc?
> > > If not, I'd gladly axe smbios legacy parts in 9.1
> >
> > Migration is irrelevant unless someone steps forward to
> > commit to long term versioning of the machine type.
>
> But migration is also how we implement savevm/loadvm,
> which are useful even when the machine type is not versioned.
> So please don't put in migration blockers or similar that would
> break that.
Yep, that's valid use case within the scope of a single QEMU release.
We just can't guarantee it across versions. Often it'll probably work
but it is liable to break at times.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-03-27 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 12:51 [PATCH for-9.0] docs/about: Mark the iaspc machine type as deprecated Igor Mammedov
2024-03-26 13:03 ` Ani Sinha
2024-03-26 13:08 ` Thomas Huth
2024-03-26 13:29 ` Philippe Mathieu-Daudé
2024-03-26 13:37 ` Thomas Huth
2024-03-26 14:00 ` Philippe Mathieu-Daudé
2024-03-26 16:16 ` Igor Mammedov
2024-03-27 10:49 ` Daniel P. Berrangé
2024-03-27 13:09 ` Igor Mammedov
2024-03-27 13:14 ` Thomas Huth
2024-03-27 13:22 ` Daniel P. Berrangé
2024-03-27 13:27 ` Peter Maydell
2024-03-27 13:29 ` Daniel P. Berrangé [this message]
2024-03-27 13:26 ` Philippe Mathieu-Daudé
2024-03-27 20:39 ` Paolo Bonzini
2024-03-27 13:51 ` Daniel P. Berrangé
2024-03-27 20:47 ` Bernhard Beschow
2024-03-26 13:30 ` Mark Cave-Ayland
2024-03-26 16:20 ` Igor Mammedov
2024-03-26 16:22 ` Igor Mammedov
2024-03-27 7:09 ` Gerd Hoffmann
2024-03-28 14:09 ` Mark Cave-Ayland
2024-03-29 10:19 ` Bernhard Beschow
2024-04-02 8:53 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgQfMq2gJuWurl3K@redhat.com \
--to=berrange@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@gmail.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.