@jxself: You should be more accurate. The VBox team is not uninterested in
fixing this.
The reply from their VBox ticket:
...
We would be glad to fix this, but we lack the resources to do so as our BIOS
code has simply outgrown what bcc (which we were using before and which was
always very limiting) can do. We have failed to find another free 16-bit x86
C compiler up to the job, and OpenWatcom is free according to OSI, which
under the circumstances we considered sufficient.
...
VBox is owned by Oracle and thus the developers are payed for doing their
work. If one is able to fix the issue, they will happily add the fix.
Also IMO there is very little benefit in using VirtualBox instead of QEMU /
KVM unless you depend on special tools (e.g. Vagrant for automated deployment
of VMs). There are tons of free frontends for managing KVM machines. The only
benefit I can see for VBox is for very special use cases with complex network
environments (e.g. virtualized HA environments with multiple dedicated NICs /
networks for double heartbeat connections).
