4 ms·
Anyone have a practical case for this? Not complaining just wondering.
by nailer 2y ago
Anyone have a practical case for this? Not complaining just wondering.
- tonymet 2y agoInception
- deleted 2y ago[deleted]
- jborean93 2y agoNested virtualization would be needed if you want to test out a Windows VM with the various Hyper-V integrations like WSL2, credential guard, etc.
- nailer 2y agoOh, that’s an excellent point. Things like WSL2 are very seamless so I don’t normally think of them as being virtualisation even though they obviously are. I might even use this myself as I need to document software development tools for Windows users.
- gilgoomesh 2y agoRunning an older version of macOS, which supports older versions of Xcode and then using that to run older iOS simulators.
- ajmurmann 2y agoCould I run an older version of macOS that still ran 32bit apps?
- jamesy0ung 2y agomacOS Mojave is the last version to support 32-bit applications. It only runs on x86_64, so you'd be emulating it, not virtualising.
- kuon 2y agoIsn't the simulator not a VM? I thought it was more something like wine.
- plorkyeran 2y agoCorrect, the simulators run regular macOS processes that are linked against a different set of userland libraries than usual. No virtualization involved.
- saurik 2y agoCI systems often run their workloads in virtualization (for both security and ease of uniform deployment), but sometimes the jobs themselves use a VM to either run part of the build process (such as depending on a tool distributed using Docker, which relies on such due to the host kernel not being Linux) or run some of the unit/integration tests (whether to create a clean environment or to take advantage of the hypervisor to get fast emulation of a target device, such as an Android phone or whatever). Without nested virtualization, services such as GitHub Actions (or locally hosted options; FWIW, GitHub also lets you bring your own "runners") have thereby been somewhat crippled on Apple Silicon.
- justinclift 2y agoDocker containers (ie Docker Desktop) running inside macOS VMs. That would fix a current blocking problem, as the lack of nested virtualisation means Docker Desktop (which runs its containers inside a Linux VM) has to run on the host and can't run inside a VM.