I didn’t realize that was a thing! Neat. Do you know what all that includes? On Aurora DX I only had to layer virt-top (virtio-win can be installed as a local package). My use case: I run a Windows VM that uses the discrete graphics card.
Edit: I did an rpm-ostree reset this week and found virtio-win was baked into the deployment. Long story but this started as a Bazzite machine, then I mistakenly rebased to the Silverblue source image that they used to make all the ublue OSes (which is a thing you can do, but obviously not supported or desired) before I eventually rebased again to Aurora DX. Learning is fun. At no point did the system fail to work, though. Kinda badass.
I think all it does is install the virt-manager Flatpak and then set a bunch of kernel arguments with rpm-ostree kargs ... depending on various hardware detections.
I didn’t realize that was a thing! Neat. Do you know what all that includes? On Aurora DX I only had to layer virt-top (virtio-win can be installed as a local package). My use case: I run a Windows VM that uses the discrete graphics card.
Edit: I did an rpm-ostree reset this week and found virtio-win was baked into the deployment. Long story but this started as a Bazzite machine, then I mistakenly rebased to the Silverblue source image that they used to make all the ublue OSes (which is a thing you can do, but obviously not supported or desired) before I eventually rebased again to Aurora DX. Learning is fun. At no point did the system fail to work, though. Kinda badass.
I think all it does is install the virt-manager Flatpak and then set a bunch of kernel arguments with
rpm-ostree kargs ...depending on various hardware detections.