On Fri, Nov 06, 2026 at 06:35:29PM +0400, Marc-André Lureau wrote:
> Hi
> 
> On Fri, Nov 6, 2026 at 3:53 PM Thomas Huth <[email protected]> wrote:
> >
> > On 29/10/2026 14.12, Daniel P. Berrangé wrote:
> > > These are all intended for use in a virtualization scenario and must
> > > provide a security boundary.
> > >
> > > Acked-by: Marc-André Lureau <[email protected]>
> > > Signed-off-by: Daniel P. Berrangé <[email protected]>
> > > ---
> > Reviewed-by: Thomas Huth <[email protected]>
> >
> 
> I have a second thought about this, I'd like to exclude all
> gpu-accelerated paths for now. virgl/mesa/rutabaga expose a very large
> attack surface, so I'd like to drop them from the secure boundary

Rather than repost, please see my response for patch 2:

  https://lists.gnu.org/archive/html/qemu-devel/2026-11/msg01530.html

TL;DR: we have already promised anything virtio related is in scope
for security handling for a long time, as they are all unambiguously
"virtualization use case".

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|


Reply via email to