One small downside…
This is not in FlatHub and it is not an official part of the VirtualBox KVM project from Cyberos Technology (the folks that make VirtualBox KVM).
This is a project from GitHub user tulilirockz
This is awesome. I use the KVM version of VirtualBox all the time. Not only is it a great UI with good driver support but VirtualBox itself is cross platform while KVM and its various front-ends are not.
I do demos and create documentation that shows VirtualBox in screenshots. The audience are people who will almost all be using Windows and macOS. With VirtualBox, we can all use the same UI with me enjoying better performance from KVM on my Linux boxes.
VirtualBox KVM does not need kernel modules so kernel upgrades are not a hassle. Before now though, I have been having to compile VirtualBox KVM itself which is a bit of a beast.
I cannot wait to try this.
This isn’t just VirtualBox. It’s VirtualBox with a KVM back end. So you get the performance of KVM, but with a much better GUI than virt-manager.
I found virtual box so much more confusing than virt manager TBH. Also there is GNOME boxes which is just a pleasure for spinning up quick uncomplicated VMs
You’re a different kind of VM enjoyer than me, and that’s okay 😎 I’m glad GNOME Boxes and virt-manager are getting the job done for you. I’m okay with the latter, but I think it needs some love, which is why I’m eager to see alternative frontend options.
Thats cool actually, thanks for this comment.
That’s pretty cool. Also, TIL there’s a virtualbox kvm backend.
Doesn’t Virtualbox require kernel modules to run? How does that work in a flatpak?
The backend is not virtualbox stuff but KVM stuff. Only the frontend is virtualbox. so one can claim that it’s more apt to say this is “virtualbox-ui”
Ohhhh right, completely forgot they have support for KVM now. Thanks!
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.
