[virt-tools-list] Docs on getting VirGL working with virt-manager?

[Erik Skultety]

On Mon, Feb 18, 2019 at 08:44:00AM -0500, Cole Robinson wrote:
> On 2/18/19 8:38 AM, Cole Robinson wrote:
> > On 2/17/19 10:57 AM, Daniel Kasak wrote:
> >> On Sat, Feb 9, 2019 at 2:05 AM Cole Robinson <crobinso at redhat.com
> >> <mailto:crobinso at redhat.com>> wrote:
> >>
> >>     On 2/8/19 7:49 PM, Daniel Kasak wrote:
> >>     > I've changed the following from the default:
> >>     >
> >>     > Display Spice:
> >>     >  - Listen type
> >>     >     - Default ( Address ) - no matter what other options I choose with
> >>     > this, I get "SPICE GL support is local-only ..."
> >>     >     - None - I get "Error starting domain: internal error: qemu
> >>     > unexpectedly closed the monitor"
> >>     >
> >>
> >>     This last bit should be the working config, but that error means
> >>     something went wrong launching qemu. pastebin your
> >>     /var/log/libvirt/qemu/$vmname.log and I will check
> >>
> >>
> >> It's taken a while to figure out exactly what's going on here ... there
> >> are *no* logs in that directory. But I caught systemd logging:
> >>   Process 15334 (qemu-system-x86) of user 1000 dumped core.
> >>  ... each time I tried to start the VM.
> >>
> >> I've tried with qemu-3.1.0 and qemu built from git.
> >>
> >> Is there a way to get virt-manager to spit out the exact command line
> >> it's using to invoke qemu?
> >
> > Are you using qemu:///session maybe? Then the logs will be in
> > ~/.cache/libvirt/qemu/log/ . The log file is the the canonical location
> > to find the qemu command line that libvirt is generating
> >
>
> FWIW there's a bug here about spice GL failing recently, not sure if
> it's your issue though:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1659484

Doubt it, so far it looks like it's tied to the VGA HW used, more specifically
AMD (I need to give NVIDIA a try with that). In any case, the error would IMHO
read "Permission denied" instead of "Unexpectedly closed the monitor".

Erik