@ cyber.spirit - VirtualBox absolutely has bridged, too.

@ sternone - Note, I said nothing, specifically, about bridging.  Bridging works fine for me, in VirtualBox.  

What VirtualBox blows up is that, every time it 'reinstalls' it's adapters, after updating to a new version, it either gives them new IP ranges, or whacks them entirely (if I have NAT NIC 1 and an extra NAT NIC 2 defined, it almost always deletes NAT NIC 2 entirely, as well as assigning a new subnet to NAT NIC 1.)

And I can assure you, it does this, regularly (as someone who uses it a LOT for work, all day, every day.)  VMWare NEVER did that to me, regardless of circumstance.  

And yes, again, I was discussing NAT, not bridged.

I'm not slamming VirtualBox. I use it all day.  Just that it definitely DOES have some quirks, which VMWare has long since put behind their offering, in Workstation.

Had the feeling it wasn't, but wanted to be very clear.  I was unaware of said setting to maintain the IP, so I'll check that, too, thanks.

(Will also have to see why it whacks the extra created NAT NIC's, too.)

Gonna have to look some more.  Didn't see any settings for a persistence after updating.  I'm sure if you say it's there, it'll turn up, though.

https://www.virtualbox.org/ticket/660

What I read is that people just note the MAC address before the upate and after the update they re-enter that old MAC address. That seems to work.