Re: Using virtio-gpu instead of virtwl

Thomas Leonard
2022-10-10T14:17:16Z

On Tue, 9 Aug 2022 at 12:01, Alyssa Ross <hi@alyssa.is> wrote:
>
> On Mon, Mar 21, 2022 at 04:05:34PM +0000, Alyssa Ross wrote:
> > On Mon, Mar 21, 2022 at 12:10:43PM +0000, Thomas Leonard wrote:
> > > I think perhaps that crosvm is compiled without the "virgl_renderer"
> > > feature (it's not in the default set), and this is causing it to crash
> > > because that's also "self.default_component". I don't know how to
> > > compile crosvm with virgl enabled, though.
> >
> > It wasn't easy, but I got it to build[1]. I hope that helps. It adds
> > both virgl_renderer and virgl_renderer_next. I think virgl_renderer
> > is on by default with --gpu, and virgl_renderer_next is used with the
> > --gpu-render-server argument. Hopefully at least one of those does the
> > right thing — let me know!
> >
> > [1]: https://github.com/NixOS/nixpkgs/pull/165128
>
> Small update: Nixpkgs unstable's crosvm package is now built with the
> virgl_renderer and virgl_renderer_next features.

I got this working eventually, but I had to apply a load of patches.
How are you getting it to run?

My patches are here: https://gitlab.com/talex5/crosvm/-/commits/main

In particular:
- It failed to start (when using virtio-gpu) because it doesn't have
access to /nix/store, and
- It failed to send Wayland keymaps because they need to be mapped read-only

--
talex5 (GitHub/Twitter)