Btw, you may not be using GPU acceleration, if you want to use that then:

In the profile you installed the VM, make a directory in the home directory of the profile named 'linux' and a blank file named 'virglrenderer' to try it out. this will cause a toast to appear showing VirGL is enabled when launching the Terminal app AFTER force stopping it

run " chromium --ozone-platform=wayland "and then go to chrome://gpu to see you're using the GPU. Should have a performance boost?

The virgl server also likely isn't needed and that's just for running a server in the host OS.

Reply to this note

Please Login to reply.

Discussion

virglrenderer file should be in the Linux directory.

Any ETA for when we will have everything working out-of-the-box (+ not having to turn on developer options)?

None currently since this is brand new and some tasks and goals will be far more difficult to accomplish. Quality features take a lot of time.

You are correct.

I did as you suggested and I got the toast pop up.

Hm. Gnome doesn't seem to like this though.

GNOME itself doesn't work well with GPU acceleration. Individual apps like Chrome would do.

This is likely an issue with Debian freezing packages and not updating them. One of the reasons wanting to move to another distro is important to us.

Thanks for the response. Any recommendations on a graphical shell to install that would work?

Heard the included Weston setup works with GPU acceleration, but users won't be using that, it's reference software. You could disable the GPU acceleration to keep using GNOME. We haven't tried many different unique software setups yet before release.

That's understandable, this is all pretty new. I'll keep banging away on it and see what I can figure out.