VirtualBox 7.0.16 Released with Initial Support for Linux 6.8 and 6.9 Kernels
VirtualBox 7.0.16 Released with Initial Support for Linux 6.8 and 6.9 Kernels

VirtualBox 7.0.16 Released with Initial Support for Linux 6.8 and 6.9 Kernels - 9to5Linux

VirtualBox 7.0.16 Released with Initial Support for Linux 6.8 and 6.9 Kernels
VirtualBox 7.0.16 Released with Initial Support for Linux 6.8 and 6.9 Kernels - 9to5Linux
I'm genuinely curious, why does VB continue to somehow remain in use, when it's lacking in features, or behind in usability, in basically every way imaginable? If you're on a Linux host, you have plenty of 1-click solutions that are incomprehensibly better than this. On Windows, Hyper-V boxes aren't horribly difficult to get running either, although from my experience, they require the same janky and hacky patches as VB does
What are the other solutions?
Vm manager, gnome boxes
Boxes
How share folder host-guest without network access? Last time try need to use samba (did not get working) and then impossible to turn off vm network access. Used qemu for win 10 guest.
VB just install guest addition and disable network interface.
Hyper-V is not really better than Virtualbox on Windows. Virtualbox will run anywhere and that is its strength.
On Linux, you should use KVM. I assume that's what your advocating for.
Cool beans. KVM is one step away from fully replacing VirtualBox and VMware for desktop virtualisation - getting a Windows 3D driver for Virtio. For use cases that can get away without it, it's already there.
What happened to being able to use VirtualBox as a front-end to KVM? That seemed like the best of both worlds.
It's still being maintained. It's a third-party project btw, but it's just a patchset so you'll need to build it yourself: https://github.com/cyberus-technology/virtualbox-kvm
Arch users can also install the virtualbox-kvm package from AUR to get it all in one go, nice and easy.
Why would you do that when libvirt exists and is GTK themed?
I use KDE.
Virtual box is slow and buggy and it probably will always be that way. It is simply the nature of its design.
Quemu+KVM is the way to go.
Odd, since in my experience, it's the most consistently reliable, performant, and easy to setup / use desktop vm package I've used. It always seems to "just work" when others don't
Let me add one more voice to say, why oh why would you do that to yourself and suffer subpar virtualization when you have world class type 1 virtualization built straight into the kernel. And an incredibly capable UI, around since 2009, in the form of virt-manager?
Meh I can get a Win11 guest that interacts well and conveniently with the host and its peripherals and if all I'm doing is running tax software, office365 or compile my Rust app to test it cross platform - vbox is perfectly fine. I'm not running anything demanding.
I'm not taking a stance against KVM it's great, but rather saying that for some of us it's not that big of an issue which solution to use, it just needs to be convenient.
But like... why? It's not even more convenient, virt-manager is literally zero setup (in Debian at least) and you don't need to deal with DKMS.
The kvm-guest-agent tool and some virtio drivers even exist for winblows.