I don’t disagree with that assessment, especially with VirtualBox 5.x releases, on either Windows or macOS. I would update a guest Linux VM with a kernel update, then in that same VM go to update the guest extensions, only to have the extension build fail. Then I’d have to wait for a following VirtualBox 5.x release to see if that release fixed the VB guest brokenness. Most of the time it did, but sometimes it took two VB releases to make it all right. Then I’d continue on until the next time the guest Linux had a kernel update and go through this again. Until I learned to be picky what I updated. I got to the point where I blocked kernel updates unless it was a major update or critical security update, and make sure I had the latest VB. That usually kept me out of trouble.

If you mean Bridged Adapter, I have that working on my macOS and have had it for some time. As for what adapter to use, I use paravirtualized network (virtio-net), instead of the default Intel Pro/1000. That seems to have solved a lot of network issues for me. But again, this is on macOS Mojave (10.14.6) which I have yet to fully update due to my dependence on Adobe Lightroom 6.

Overall I find the VB 6.x release to be better managed and of better quality.

I have Windows 10 Pro (free from my Windows 8 Pro from a Samsung notebook I purchased in 2013, and which still works) and I installed WSL with Ubuntu 18.04. I like what they’ve done from a shell perspective. It beats the hell out of Cygwin and company. The problem there is enabling Hyper-V effectively disables VirtualBox and VMware Player. I should learn to import and exported VB appliance VM, but it’s not too high on my to-do list at the moment.

LikeLike

LikeLiked by 1 person