Hi,
On Mon, Apr 01, 2019 at 10:40:12AM +0200, intrigeri wrote:
> Control: tag -1 + patch
>
> Guido Günther:
> > I had going through the open apparmor issues and especially the OpenGL
> > ones on my TODO list for buster
>
> I've triaged the AppArmor issues last week-end :)
>
> > but if you'd
Control: tag -1 + patch
Guido Günther:
> I had going through the open apparmor issues and especially the OpenGL
> ones on my TODO list for buster
I've triaged the AppArmor issues last week-end :)
> but if you'd pick that up that would be totally awesome.
Done:
Hi,
On Sat, Mar 30, 2019 at 05:18:01PM +0100, intrigeri wrote:
> Control: severity -1 important
> Control: tag -1 + fixed-upstream
>
> Hi,
>
> bumping severity as this totally breaks an option offered to users via
> virt-manager.
>
> Now, I've verified that virt-manager in current sid still
Control: severity -1 important
Control: tag -1 + fixed-upstream
Hi,
bumping severity as this totally breaks an option offered to users via
virt-manager.
Now, I've verified that virt-manager in current sid still creates new
VMs with QXL graphics by default, so this bug only affects users who
opt
I got the virto-gpu + Virgl configuration to work with the configuration
file I posted.
When I edited the file I fumbled a bit so I suspect what happened is
that at some point I broke the AppArmor state in some subtle way. Then
it all got fixed a bit later when I rebooted.
So the important
How exactly do you see these logs?
I'm trying to start a Linux guest on Debian testing host, using virt-manager
and user session.
I enabled OpenGL and 3D acceleration and it fails like this:
Error starting domain: internal error: qemu unexpectedly closed the monitor
Traceback (most recent call
Thanks for posting this to the Debian bug list. It did indeed make
finding it easier!
Unfortunately I'm still getting the same error after modifying
/etc/apparmor.d/libvirt/TEMPLATE.qemu. Maybe I missed something.
Here's my file:
-
#include
profile LIBVIRT_TEMPLATE
7 matches
Mail list logo
