On Mon, May 22, 2023 at 11:55:15AM +0200, Cornelia Huck wrote:
> On Wed, May 17 2023, Andrea Bolognani <abologna@xxxxxxxxxx> wrote:
> > Migration is of course the most obvious failure scenario, but one of
> > the critical features offered by libvirt is guest ABI compatibility.
> >
> > If the user needs MTE3 specifically, rather than any MTE version, to
> > be available to the guest OS, they'll configure the domain with
> > something like
> >
> > <mte version='3'/>
> >
> > and we need to be able to prevent such a VM from running on a host
> > that doesn't have MTE3 support.
> >
> > So the fundamental question is, does the current libvirt interface
> > paint us into a corner when it comes to implementing a more granular
> > one later?
>
> Given that an interface allowing to actually control the exposed version
> is not likely to pop up in the next days, does it make sense to even try
> to wire it up in libvirt right now?
I believe it does not.
Until the situation has cleared up
<qemu:commandline>
<qemu:arg value='-machine'/>
<qemu:arg value='virt,mte=on'/>
</qemu:commandline>
while far from an optimal solution, will work in a pinch.
--
Andrea Bolognani / Red Hat / Virtualization
