Bazzite 44: Should I now Disable Virtualization?

Bazzite
1

Prior to Bazzite 44, I had enabled virtualization with ujust setup-virtualization. I had set up only two VMs and had already deleted them by the time Bazzite 44 rolled around and removed QEMU/KVM. Should I run ujust setup-virtualization again and disable virtualization? Or, just leave things as they are?

Semi-relatedly, if, on rare occasions, I want to set up and test a VM of something, how do I do that in Bazzite now without rebasing to Bazzite-DX?

2

Virt-manager/Qemu is available on Flathub. You first need to install the virt-manager flatpak and then install the Qemu extension (both from Bazaar). Then when you open virt-manager you need to switch to the user-session for Qemu.

Just notice that the Flatpak doesn’t support some more advanced stuff, like device passthrough and advanced networking stuff. But if you just want to test something quickly it handles it fine.

3

Thanks for the info. The Virtual Machine Manager flatpak was still installed from the ujust setup-virtualization command. But, I didn’t know about adding the QEMU extension. So, in Bazaar, I went to Virtual Machine Manager and hit that Manage Add-Ons button just under the description and downloaded it.

I’m not sure what you mean by switching to the user-session for QEMU. I suppose that’s why, when I double-click on the “Not Connected” QEMU/KVM connection in Virtual Machine Manager that’s already there, I get:

Unable to connect to libvirt qemu:///system.

Verify that an appropriate libvirt daemon is running.

Libvirt URI is: qemu:///system

Traceback (most recent call last):
File “/app/share/virt-manager/virtManager/connection.py”, line 940, in _do_open
self._backend.open(cb, data)
~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File “/app/share/virt-manager/virtinst/connection.py”, line 173, in open
conn = libvirt.openAuth(self._open_uri, [valid_auth_options, authcb, cbdata], open_flags)
File “/app/lib/python3.13/site-packages/libvirt.py”, line 147, in openAuth
raise libvirtError(‘virConnectOpenAuth() failed’)
libvirt.libvirtError: Failed to connect socket to ‘/var/run/libvirt/virtqemud-sock’: No such file or directory

If I click on File > Add Connection, I can pick a Hypervisor of QEMU/KVM User Session, that seems to work. Is that what you mean? After I do that, is there any reason to leave the default “system” QEMU/KVM connection? Should I delete it?

4

Yes that is the setting to change. You can then remove the system qemu session from virt-manager