VBoxManage setextradata "macos" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "macos" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" The commands you are required to run using VBoxManage (which is found in C:\Program Files\Oracle\VirtualBox) are.
When you create your new VM from the downloaded image select MacOS as type, and El Captain 64bit as the Version. Basically the guide boils down to download a base image, then setup a VM in virtual box and do a few tweaks to it, to trick MacOS into thinking it is running on a Mac, and the boot the machine. Luckily, some more Apple Savy people have described how to do, the guide I followed are. As I promised I’m going to install MacOS Sierra. With VirtualBox installed it is time, to install the operation system of your choice on your nested virtual machine. For some reason it downloaded super slow from Azure, so I downloaded i on my local machine and uploaded it through remote desktop. Once the machine is provisioned, you need VirtualBox. I just picked Windows Data Center 2016 and installed everything from the azure portal. You need 1 Azure VM based on Ev3 or Dv3, for my testing I used a Standard_E2_v3 hosted in West Europe (Currently the new machine are only in West US2, East US2, Southeast Asia and West Europe). (Beware that Apple licensing is probably not going to approve of this, but let’s save that concern for another day). Furthermore, as I’m going to show in this blog post, I can also install an open source Hypervisor like VirtualBox and use that to emulate a Mac, of course that can also be done on a local machine, but the benefit of running it in the cloud is that it can be online 24×7 which is great if you need a build or test server. 
To me as a developer that is pretty cool, because now I can actually create a development machine in the cloud, install hyper-v on it and run my mobile emulators or even use docker for Windows, which is dependent on Hyper-V. Why is that interesting you might ask? Well, it is interesting because now it is possible to run hyper visors inside an Azure VM. Last week Microsoft finally released their new Azure Virtual Machine series Dv3 and Ev3, besides being based on the latest Intel hardware, these machine are also running Windows Server 2016 as the host OS which supports nested virtualization.
Interesting articles about Azure, Docker and Office 365
0 kommentar(er)
