> On 9 Mar 2026, at 12:44 PM, Mohamed Mediouni <[email protected]> wrote: > >> And having a custom flag not turned on by default for a long time for this >> comes with the risk that almost nobody will enable it instead of it being >> eventually phased in as the default configuration…
Yes, I agree with this :/. This is something that concerns me too. Although, for majority of guest, either they do not use directed eoi or the spurious eoi exits from KVM just works. But, users will end up using the quirked setup. Maybe this is fine with a printed warning? If they see something breaking(apparently not alot, as the bug has been around since 2019) they can move to respected/not-advertised. Definitely not happy with this tho. Hmmm, machine-type gating looks the way forward, > On 9 Mar 2026, at 12:44 PM, Mohamed Mediouni <[email protected]> wrote: > > But I might be wrong on this one, with machine type being potentially better > in practice - although it’s way too late to define this as part of q35-10.2 > baseline as that has been long released, so it could be a slower rollout with > the default tied to a new QEMU release. And an error message to use a newer > kernel in that case if using the newer machine model explicitly or implicitly. I like this idea, by default we have it on, on error hint to use quirked mode explicitly. This also fixes the live migration state issue. So basically: For the latest (or next) qemu machine type version: - seoib can be on/off by default based on the IOAPIC version. - user can explicitly set it to quirked using the command line. Thanks, Khushit.
