cm0002@lemmings.world to Linux@programming.dev · 7 days agoVirtualBox has been packaged as a Flatpakursal.zonevideomessage-square18fedilinkarrow-up1118arrow-down13file-text
arrow-up1115arrow-down1videoVirtualBox has been packaged as a Flatpakursal.zonecm0002@lemmings.world to Linux@programming.dev · 7 days agomessage-square18fedilinkfile-text
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up8arrow-down1·7 days agoCool that it is now a flatpak However, I would recommend gnome boxes or virtual manager.
minus-squaresomerandomperson@lemmy.dbzer0.comlinkfedilinkarrow-up1·7 days agoVia flatpak permissions. Flatpak permissions can give access to pretty much anything, in this case, /dev/kvm.
minus-squareLeFantome@programming.devlinkfedilinkarrow-up1arrow-down1·7 days agoAs this uses the KVM backend, they are all essentially alternative UI for the same hypervisor.
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up1·7 days agoKVM is only used for the CPU portions
minus-squareLeFantome@programming.devlinkfedilinkarrow-up2·6 days agoSurely it uses KVM for memory isolation as well. I guess what you are saying is that VirtualBox is still doing device emulation. If so, we agree.
Cool that it is now a flatpak
However, I would recommend gnome boxes or virtual manager.
Via flatpak permissions.
Flatpak permissions can give access to pretty much anything, in this case, /dev/kvm.
As this uses the KVM backend, they are all essentially alternative UI for the same hypervisor.
KVM is only used for the CPU portions
Surely it uses KVM for memory isolation as well.
I guess what you are saying is that VirtualBox is still doing device emulation. If so, we agree.