When running Windows on top of macOS through virtualization you can use developer tools like Visual Studio, Windows Terminal, and others on macOS! However, using Windows Hyper-V to be able to run Windows VMs within your Windows VM requires the Intel VT-x virtualization support of the Intel CPU in the macOS computer to be enabled.
Doing this allows you to run both macOS and Windows, or even Linux, operating systems and software on a single computer at the same time.
No Parallels for now.Many Developers and other IT Professionals use macOS (via a Macbook Pro or other Apple computer) and do need to run Windows on their machine under virtualization using Parallels or VMWare. This was resolved after uninstallation of the Parallels Tools. But right after the startup (again) docker crashed.ĭocker also crashed when native booted into Windows. The machine creation took some time while installing the Parallels Tools. In the trial version all options are available, so I used the nested virtualisation option. By installing a trial version of Parallels Desktop I was able to start the Boot Camp Windows installation from within macOS. The option of running Windows in Parallels still interested me.
The command above will return True this way and everything works. For now I’ll be booting into macOS and then booting into Windows. There seems to be a virtualisation bug that disables hyper-v on a cold boot. (gcim Win32_ComputerSystem).HypervisorPresent Google suggested to run this command to check if Hypervisor was activated/present. Resetting the physical computer is not sufficient.)ģ) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
(If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. The following actions may help you resolve the problem:ġ) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.Ģ) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running (Virtual machine ID ~some GUID~). The next day I started my MacBook into Windows and docker crashed… Another reboot and Visual Studio, Docker, … all installed without issues.
Boot Camp installed the drivers after the first login.
InstallationĪfter a reboot I was presented the Windows 10 installation setup.
To remove these I used Disk Util as described here.Īfter downloading the supported ISO file and rebooting (have you tried turning it off and on again) the Boot Camp assistant did the job. Now I have a corrupted Boot Camp partition. Looks like only the commercial version of the ISO is supported. The ISO file I downloaded from the msdn subscriptions page was incompatible and resulted in an error. The assistant now lets me create the partition of 80Gb. Luckily there is a way of removing these hidden files. What is going on? Seems that local time machine backups secretly eat into your available disk space. My disk reports 105Gb of free space so that’s okay. I want to assign 80Gb since I’m installing Windows, Visual Studio, Docker and some other development stuff. The first step in the Boot Camp Assistant is setting up the Boot Camp partition. My only option is setting up Boot Camp and boot native into Windows. This means I cannot use nested virtualisation. For this you’ll need a Pro subscription, which I don’t have. Parallels has an option called “nested virtualisation” where the guest OS can do virtualisation. To use docker on Windows I need to enable Hyper-V. For development I’m using Windows in a Parallels VM on my MacBook Pro.