[Proposal] Remove qemu/libvirt stuff and replace it with the flatpak

[inffy]

Just notting this down.

So starting from F42 images we could take out the rpms for the qemu/libvirt stuff and put the flatpak for virt-manager and qemu extension.

[inffy]

Also just to make it clear to readers.

This is no way a decision that is done yet. More of a plalce for discussion about the "proposal" for the F42.

Would be happy to hear some comments from people who have had time to check in on the virt-manager+qemu extension flatpaks. Are there big shortcomings? Something that just doesn't work compared to the rpm "native" version.

[boredsquirrel]

I am currently testing this. A ujust command would be good to migrate to the flatpak

• installing org.virt_manager.virt_manager.Extension.Qemu org.virt_manager.virt_manager
• opening and closing it (to create the files, idk where the images are stored)
• checking wether a QEMU system or guest session was used
• moving the images over

Does the flatpak work with the default QEMU system session, idk user namespaces or something? It seems it still defaults to the system session, which fails because the libvirt daemon is not running. This preset could probably be patched on the flatpak side, for now the connection needs to be removed and a user session added, not great UX.

Aaaand I am getting errors creating a VM

"error: cannot limit core file size of process 157 to BIGNUMBER: Operation not permitted"

Not ready yet

[renner0e]

Would be happy to hear some comments from people who have had time to check in on the virt-manager+qemu extension flatpaks. Are there big shortcomings? Something that just doesn't work compared to the rpm "native" version.

Some issues I've experienced so far:

• GPU Passthrough shouldn't work, I have not tested that myself, but it makes sense to me

• user mode Networking is more limited, there is no default bridge networking device thus you can't ping/ssh into the VM from the host

• USB device Passthrough is not possible at the moment, maybe this will change in the future when the new USB device portal is being used

[RealVishy]

Another avenue we could take is a ujust to merge a sysext of libvirt, virt-manager and qemu, since we'd have systemd 257 in f42.

[dreamyukii]

Some stuff only works with system wide libvirt like advanced networking, gpu passthrough.

i think libvirt can stay on the dx image and then when bootc can do sysext we can remove it from image

[tulilirockz]

@renner0e

user mode Networking is more limited, there is no default bridge networking device thus you can't ping/ssh into the VM from the host

This should be fixed soon-ish, see flathub/org.virt_manager.virt_manager.Extension.Qemu#17

USB device Passthrough is not possible at the moment, maybe this will change in the future when the new USB device portal is being used

Hopefully this can be fixed via udev rules I believe. virt-manager itself would need to add support for the USB portal :(

GPU Passthrough shouldn't work, I have not tested that myself, but it makes sense to me

Yup that one is probably never going to work

[tulilirockz]

@boredsquirrel

"error: cannot limit core file size of process 157 to BIGNUMBER: Operation not permitted"

This happens because of something on the host, probably its something that secureblue does, since I personally have not had any issues with it at all

[tulilirockz]

@boredsquirrel

Does the flatpak work with the default QEMU system session

Yup, Bazzite has been using this for their virtualization needs since forever now