sudo systemctl enable --now libvirtdsudo systemctl enable --now libvirtd I need to update that script today, sadly that command above has to run after the reboot...
So, I updated my testing image on OLED and moonlight still has crackling noise issues over Ethernet and wifi. This issue doesn't happen on my Android phone. There's no crackling when running games natively (I tried Celeste)
Ok, how exactly do I get a shared folder to work in the guest OS in boxes? For a test I set Public as the share folder in the config, but when I put a file in the host public folder or in the guest public folder, it does not show up in the other OS?
no idea how to do it in gnome boxes but on virt-manager i have a single folder that i pass through using virtiofs (due to limitations it only supports passing through 1 folder per VM last time i checked, but it works for my use) https://virtio-fs.gitlab.io/
not sure how supported virtio-9p is as i never used it personally since i needed something that worked on multiple OSes and back when i looked into it, it didnt work on i think windows. that might have changed ages ago though, but at that point i already had samba set up on my host or i moved on to virtiofs
Just installed bazzite-deck with the testing branch on my OLED deck, and it's mostly working well. There's two bugs I've noticed so far:
1) In the mangohud display that's built into Steam game mode, overlay 2 doesn't show any frametime graph next to FPS. It appears in overlays 3 and 4. In addition, overlay is missing information on CPU power usage and temperature.
2) This is a bit more serious - when using the frame limiter in game mode, limiting the framerate to any number that doesn't divide into 90hz results in a very choppy frametime presentation, with the frametime fluctuating rapidly between a few ms (you can observe this using mangohud overlay level 3). You notice this in-game as microstutters during gameplay. This disappears if I set the refresh rate to anything that sets the panel to 90hz. This is a problem given 60 and 40 FPS values are a common target to hit for the deck.
2b) As an addendum to the above, setting the frame limiter to more unorthodox limits (such as 80hz) means the frame target fails to reach the target at all, and hovers at different values (in 80hz's case for instance, it tries to stick to 60 FPS for some reason).
virtiofs is literally a filesystem passthrough, no networking involved. the slowdown is either from the driver itself, the implementation or the disk the passed through folder is on