The equivalent on macOS would leverage Hypervisor.framework, like xhyve or Veertu.

https://github.com/machyve/xhyve

https://veertu.com/anka-technology/#hypervisor

I gather that Veertu has (had?) a product called Veertu Desktop and it was open sourced, but they've wiped any mention of it from their website in favor of Anka Flow/Device/Build (commercial license only).

This looks like the source, found in a github repo of someone who works for Cisco. Maybe a former Veertu employee, or just someone who happened to fork a copy before Veertu deleted it? At any rate, I can't find an official Veertu repo anymore. https://github.com/tithomas1/vdhh

Last updates were 2 years ago and the installation instructions say "To Install Veertu Desktop on Mac, please visit veertu.com" which has deleted everything related to Veertu Desktop down to the knowledge base articles with release notes https://twitter.com/veertu_labs/status/818584467954495488

Seems like a pretty thoroughly dead product. Haven't heard of xhyve before, but between the two that's the one worth looking at.

Not only open sourced, but GPLv2'd. Ripe for forking, if one felt so inclined.

Sure but GPLv2 doesn't help you if all copies of the source code are gone, so be sure to grab a copy of that vdhh repo now in case tithomas1 removes his.

I imagine it's not in a working state on current versions of macOS, what with the security changes that Apple makes pretty much every year. But if someone wanted to try to get it going again they certainly could.

Docker for Mac has moved from VirtualBox to the built-in hypervisor.

I have the impression that causes some pain when it starts eating away battery faster than the monitor can charge the laptop.

Hmm, never noticed that; to the contrary, in my practice, Docker's VM eats CPU less aggressively than VirtualBox's.

Indeed, it's called HyperKit[0][1], and it's based straight off xhyve[2].

Also, there's docker-machine-driver-xhyve for people that prefer using docker-machine (like I do) instead of DfM.

[0]: https://github.com/moby/hyperkit

[1]: https://blog.docker.com/2016/05/docker-unikernels-open-sourc...

[2]: https://github.com/moby/hyperkit/tree/master/src/

Last time I tried, reasonably recent kernels (like 4.15 or so) failed to boot under Veertu, for no apparent reason.

Have they improved?

Xhyve looks promising, but it’s really new and at this stage it lacks all but the most basic documentation.

Exactly, I'm upvoting this to prevent poor souls stuck on Windows from looking for these nice solutions...

But can't the poor souls stuck on windows use hyper-v and RDP into the vm?

I tried Hyper-V for a while but I found the network configuration really cumbersome. Therefore I went back to Virtualbox but I should probably request my employer to buy a license for Vmware.

Is it because you switched frequently from one adapter to another (like wifi to ethernet)? Otherwise I don't think I ever had any problem with the network configuration.

In Windows 10, we provide a NAT network option by default. This should work seamlessly even if you switch between WiFi and Ethernet. So even this problem should go away for most people now.

Didn't the NAT get pulled from hyper-V?

I don’t think so. It’s only there by default on client, not server, though.

You need Windows Pro as a guest to RDP.

Not if you use the Virtualbox extension pack to VNC (that's the free/GPL extension pack, not the Oracle one). That will work with anything. Hell, it'll work with a DOS 1.0 guest.

(and yes, it's VNC, not RDP, I believe the oracle extension pack actually allows for Virtualbox to do RDP as well. But you can stay GPL-only and still support headless VNC. I believe phpVirtualbox uses it with beautiful results)

https://forums.virtualbox.org/viewtopic.php?f=7&t=85886

Can't you only RDP (and here is the qualifier) out-of-the-box with an "Enhanced Guest" VM, like what comes with some of the later Windows 10 builds, like 1809?

Otherwise, don't you have to do everything by hand to configured xrdp on the Linux guest?

Well technically hyper-v comes with its own terminal, but granted it kind of sucks and I wouldn't use continuously.

I think Hyper-V is Windows 8+ (or similar generations of Windows Server), isn't it?

Much of the Windows world is still on Windows 7, and it would be rather ironic if they were updating because of concerns about software phoning home...

Hyper V requires a Windows Pro license last time I checked. That’s significantly more expensive that VirtualBox.

I use hyper-v and rdp every day, very happy with both. I even run Linux VMs in hyper-v.

I've had nothing but issues trying to run Ubuntu in Hyper-V. Even the Windows Ubuntu LTS image that comes with the quick-create didn't work for very long.

Not sure what I'm doing wrong, but I've never has success with non-windows OS's.

What host version? I'm running 18.04 on Server 2016, for reference, did absolutely nothing special or unique, downloaded the iso, built the machine and loaded it and it's up running dns & unifi controller 24/7 for my home network with no issues.

Can you run singularity-container or docker in your Linux guest?

I haven't had reason to try, but I can't imagine a good reason why one couldn't.

I would hope so, as that is what the Win10 version of Docker-for-Windows does.

Yes

Hyper-V only works on the Pro versions of Windows.

WSL has supplanted VirtualBox for actually all of my use cases.