Hyper-V server is the free virtualization OS from Microsoftto compete head to head with the free ESXi OS. When running in large farms ordomain joined, Hyper-V seems to work pretty decently. But when you just want asingle host that you manage with Windows 10, or let alone MacOS, Hyper-V canbecome a nightmare.
So why would you go the Hyper-V route and not the ESXi routein that case? Well. ESXi has a very specific taste for hardware. Only certainraid controllers, certain NIC's etc are supported. While Hyper-V based on theWindows 2016/2019 OS usually gives you more freedom to play around with, and itsupports RAID straight from the software. So essentially, you can run it onalmost any white box,.
Mar 28, 2020 Hyper-V for Windows Servers is an add-on to the Windows Server OS. Hyper-V Servers, on the other hand, is a standalone solution that can be used to manage virtual and dedicated server instances. The Hyper-V server itself (just Hyper-V role, not the rest of the server box) and; the Hyper-V VMs (like connecting into them) via Mac OS? I'm on Mac OS 10.8 on my main laptop. From what I've been seeing the Hyper-V management tools are all Windows based. I am considering a Mac as my main development machine, and will most of the time be required to use Windows for my development work. According to the Apple support article Turn off Hyper-V to use Windows 10 on your Mac it is not possible to use Hyper-V in Windows 10 on a Mac in Boot Camp. Oct 28, 2017 I'm relatively new to Hyper-V and virtualization. What I would like to know, is the best way to create a Mac OS X VM running in Windows Hyper-V host. I'm currently using a Windows 10 based desktop running Hyper-V to create a test lab. I'd like to run a Mac OS X VM in Hyper-V in my test lab.
In this post I'll be installing Hyper-V server on my DellT710 as a single-stand-alone machine, while configuring it solely from a MacOSbased laptop.
First things first, download Hyper-V 2016. You could opt for the 2019 version, but there are some quirks on that one with regards to RDP, which we will need when we are configuring it. (so much for the good start). I installed the 2016 version on Disk 0, an SSD that is attached to a standard SAS/SATA controller. After the installation, set the password for the administrator account on the console.
And after logging in, enable RDP by typing 7 ,E , 1 on the pop-up.
Next we need to know the IP of the server so we can connectto it: Type: 8 and note the IP listed:
Then on your Mac, download the latest Microsoft RemoteDesktop application and create a connection to the server.
On the application, select the + and then select Desktop. On the PC Name field enter the IP address and click save. Your connection will be saved under Saved Desktops. Double click and login with administrator/. On the pop-up regarding a certificate validation, click continue.
You will now have the remote desktop loaded on your Mac.First things first, lets get the updates by issuing 5 , D(download only) . Then 6 (download updates), A (all updates) andhave the system update itself.
In my server I have a custom NIC for which the drivers arenot loaded by default. I've been working on the on-board QLogic NIC for now,but I wanted to enable my 2x 10Gb SFP (HP HC523SFP) NIC as well. So, in caseyour NIC did not load either, through the console (as RDP would not work if youdon't have any connection), follow the next steps.
NIC Drivers
In my case, the NIC driver is actually an executable thatextracts itself and starts the installer, but in my system, the drivers are for2012R2, not 2016 and thus the auto installer doesn't work. We have to go theold-school route of installing the drivers.
First, the extraction. The extract only of the softwaredoesn't work and as I promised I'd only use MacOS we can't extract them onthere either. So, we run the installer, but leave the error message in thebackground while we grab the extracted files:
The temporary files location can actually be found in thelog file under c:cpqsystemlog
Once we grabbed all the required files, we can now dopnputil. Autocad 2016 keygen for mac os 10.13.
And let's see if we have additional NIC's by doing an ipconfig/all (or even better, issue PowerShell and then type Get-NetAdapter)
Remote Control of theserver
In order to create and manage VM's we could opt for a full PowerShellbased management. But given we'd have to RDP constantly into the server (from MacOS),it's probably easier to install the Windows Admin Center.
For this, download the admin center toolkit: https://www.microsoft.com/en-us/cloud-platform/windows-admin-centerput it on a USB drive to copy it to the server (or open a share or any othermeans of copying it to the server) and from a command prompt in the server run:
This will install the Admin Center on port 443 on the serverquietly. Wait for a few moments and then using the browser on the Mac go to https://server and login using the servercredentials.
Once the admin center is loaded, you can go to the Hyper-V section and create / manage VM's. On the file-services tab you can also upload/download files straight into/from the server
Hyper V For Virtual Machine
Disks
The next part is getting the disks into a storage pool. Thisis required when you have multiple disks and no hardware raid controller (oryou want to have the freedom to change the disk pool quickly). You can do thisvia the admin center (Storage) or through PowerShell as I do in this example:
In order to get all our disks into the pool, we create an array of all the disks that are available for the pool:
Then we create the storage pool:
Once we have the pool, we create a new volume on that andset the volume to a stripe level. You can select Simple (no redundancy, max performance), Mirror, and Parity (raid5 or 6).
In my case, I'm just setting up a mirror, using maximum size
And that created and formatted our V: drive for storage ofVM's. Let's create a VM folder and Virtual HardDisk Folder and set the defaultsto those folders:
Networking
So now that the storage is done, let's create the VirtualSwitch. Again, you can do this via the Admin Center, but through PowerShell it'sjust as easy…
In my case I want to enable the switch with my 2x 10Gb NIC's, using Get-Netadapter I' able to retrieve my Ethernet friendly names and I can create the switch using the following command:
If you have dedicated NIC's for just the VM's you can set the AllowManagementOS to $false
Remoting into the VM's
Given we set the challenge to only work on a Mac, you willnotice that connecting to VM's is not directly possible. Even with the officialMicrosoft Remote Desktop software available for OSX. But fear not, anothercompany has released an application that does work. It is called RoyalTSX andits available for Windows and Mac. While the suite itself can do much more, weonly need the free version of the software.
Os X In Hyper V
There are 2 ways to connecting to a VM. The Console (the usually screen+keyboard of a machine) or remote access (either RDP, PowerShell,etc for Windows, or SSH for Linux). In this case, we want to get to the console. And RDP for Hyper-V allows us to do so by connecting to the host with an InstanceID. In order to get the instance ID, go to your VM in the Admin Center console and select More to download the RDP file:
If you open the RDP file, you will notice a GUID if you open the downloaded file with a text editor. Nvidia geforce gts 250 driver update. You can also find the GUID quickly on the Summary view of the Virtual Machines (which lists changed/started/created VM's). Copy the GUID and open Royal TSX. Under Remote Desktop create a new entry with the name of the VM. For the Remote Desktop entries, put the name/ip of the server and port 3389.
Install Mac On Hyper V
Then scroll down to Hyper-V and put in Hyper-V host, connect to a specific instance. Put in the port 2179 and put in the InstanceID:
How To Use Hyper V
Then apply and close and connect.
Mac For Hyper V
And done!
