Practical thing is not having to recompile 3rd party drivers (vbox ko) every time kernel gets upgraded. Tho DKMS tries to take care of that without admin intervention, it's not always bug free.
On the other side VirtualBox the software application is designed to integrate with the desktop well, VNCing into the guest is not an alternative to this.
I hope efforts will be made in FreeBSD world too against its bhyve hypervisor.
The terminology issue is curious but it has been already covered here lately in a topic about Linux direct rendering manager, DRM. The acronym was used in a narrow circle of people compared to "the whole ICT", as were keyboard-video-mouse devices. Less than 1% of professionals deal with Linux internals on that level, and less than 1% of professionals are server room on-site engineers. There wasn't collective consciousness about these terms so they got reused.
Also LVM is taken by something else (storage) and LKVM would be confusing.
I cannot even imagine using a distro that can't manage to get DKMS/kernel module updates to be reliable. I don't think I've ever had a problem with DKMS in NixOS ever; not a single time.
edit: downvoting me won't make your distro any more competent.
On the other side VirtualBox the software application is designed to integrate with the desktop well, VNCing into the guest is not an alternative to this.
I hope efforts will be made in FreeBSD world too against its bhyve hypervisor.
The terminology issue is curious but it has been already covered here lately in a topic about Linux direct rendering manager, DRM. The acronym was used in a narrow circle of people compared to "the whole ICT", as were keyboard-video-mouse devices. Less than 1% of professionals deal with Linux internals on that level, and less than 1% of professionals are server room on-site engineers. There wasn't collective consciousness about these terms so they got reused.
Also LVM is taken by something else (storage) and LKVM would be confusing.