Anexado: 2 imagens
Update on VirtualBox flatpak with KVM patches: Windows Guest 3D acceleration works really good!
#virtualbox #flatpak #kvm #vm #linux
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.
TIL there’s a KVM backend for VirtualBox. Thank you. Does everything “get saved” in VirtualBox format?
I’m using libvirt on my workstation and Proxmox on my servers, it’s effort but possible to transfer the VMs back and forth when I need to, not sure if I could do that if I switched.
VirtualBox KVM uses the same format as VirtualBox proper.
The virtual machine description is not compatible with Proxmox. That said, you can import a VirtualBox environment into Proxmox and vice versa. I have done it.
What you actually import is the “drive” of the VM. You create a new VM in Proxmox (or VirtualBox if going the other way). Then you attach the imported disk to it.
The devices may differ between environments. So they are not exactly the same. But as long as the OS you are visualizing can support both, it works well.
I’ll have to give it a spin. My biggest concern is for one of my VMs that occasionally moves, it has ‘disk’ for both an efi and a tpm.
In any case, I’ve read enough in this thread that I’m going to see for myself. :)
Thanks for the feedback!
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.
TIL there’s a KVM backend for VirtualBox. Thank you. Does everything “get saved” in VirtualBox format?
I’m using libvirt on my workstation and Proxmox on my servers, it’s effort but possible to transfer the VMs back and forth when I need to, not sure if I could do that if I switched.
VirtualBox KVM uses the same format as VirtualBox proper.
The virtual machine description is not compatible with Proxmox. That said, you can import a VirtualBox environment into Proxmox and vice versa. I have done it.
What you actually import is the “drive” of the VM. You create a new VM in Proxmox (or VirtualBox if going the other way). Then you attach the imported disk to it.
The devices may differ between environments. So they are not exactly the same. But as long as the OS you are visualizing can support both, it works well.
I’ll have to give it a spin. My biggest concern is for one of my VMs that occasionally moves, it has ‘disk’ for both an efi and a tpm.
In any case, I’ve read enough in this thread that I’m going to see for myself. :)
Thanks for the feedback!