I believe in Hyper-V!

Hyper-V nested virtualization made my life easier [Datacenter on my laptop]–Part I

Hi there,

I’d like to show you how I have been creating the small datacenter on my laptop. Thanks to Hyper-V nested virtualization, now I can run Hyper-V Cluster inside my laptop and can try all new features and the most important, I can troubleshoot without to affecting production environment.
I have three SSDs, 32GB of ram, i7 CPU and Windows 10 build 10586 installed.

The scenario is as follows:
1. Hyper-V hosts runs on Windows Server 2016 TP4
2. Set Hyper-V hosts in a separate network segment.
3. Install virtual machine with Remote Access role [Internet access for the VMs] I’ll write about this configuration in my next post…
2. Install of Hyper-V Cluster with four nodes. [for Storage Spaces Direct]
3. Create an Active Directory domain for the future lab

Setup environment on the laptop

After Hyper-V role installed I set virtual network adapters. On the pictures below you can see two of virtual networks, two External networks and one Internal network.

External network will use for internet access and internal network will use for the lab environment only, but still, virtual machines from the internal network will be able to go on the internet because of router between external and internal network. In the next blog post I’ll write about how to setup Remote Access role in Windows Server 2016 TP4

Create virtual machines and enable Nested virtualization

As you can see I created five virtual machines, one called Router and four Hyper-V nodes
Router virtual machine has a 2GB of ram (dynamic memory), 1CPU and small dynamically expanding virtual disk, but the Hyper-V nodes have 4-6GB of ram, 4CPUs and 100GB of virtual disk. Why I mentioned Hyper-V hardware resources? Because this is very important!
To enable Nested Virtualization in Hyper-V, Microsoft created a script you can use or you can do it manually following this steps:

  • Disable Dynamic Memory on every Virtual Machine on which you want run nested virtualization
  • Enable MAC Address Spoofing
  • Set minimum of 4GB RAM per virtual machine
  • Enable Virtualization Extensions on the vCPU

To set the Virtualization Extension for the vCPU use PowerShell command:
Set-VMProcessor -VMName “Hyper-V host name” -ExposeVirtualizationExtensions $true


Hyper-V nested virtualization has some limitations!
More about Hyper-V nested virtualization you can read on Thomas Maurer blog.


Now we are ready to install Hyper-V role on the Virtual Machines in the environment. You can install Hyper-V role through GUI or PowerShell, your choice. If you like GUI go to Server Manager –> Add Roles and Features and follow the wizard. If you prefer PowerShell, open PowerShell in elevated mode and run:

Install-WindowsFeature –Name Hyper-V -ComputerName <computer_name> -IncludeManagementTools -Restart

After server restart we have Hyper-V role installed and we are almost ready to go. I recommend setting default location for Virtual Machines configuration files and VHDXs as well. In this case I’ll put VMs in C:\\Hyper-V folder, than will setup virtual network.


I did the same on every virtual Hyper-V host in my environment!

Now we are initially prepared. The next step is “Router” installation. That will be virtual machine with Remote Access role installed as I mentioned above.

Until next post stay tuned Smile



Windows 10 Insider Preview–Build 10565 and Hyper-V virtual network adapters

Hi to all,

Few days ago I decided to update OS on my laptop to Windows 10 Enterprise Insider Preview Evaluation copy, Build 10565 from the previous version. To be clear, I have installed Hyper-V role, few of virtual machines and two of external virtual adapters as can you see on the picture below.


After installation finished and laptop restarted, virtual network adapters was broken and unusable.

Cannot use virtual network adapters anymore, cannot delete virtual network adapters and cannot do anything with virtual network adapter, but still… Winking smile

How to resolve:
Uninstall Hyper-V role, install again, create new virtual switches and go ahead.

Friend of mine Tomica asked me; Romeo, why you didn’t uninstall Hyper-V role before update? Smile
So, uninstall Hyper-V role before of Build 10565 installation and you will not have any problem.



Microsoft MVP for Hyper-V 4th time in a row

Four years in a row ;)

Every October 1st I have been waiting on one important e-mail from Microsoft and every year I’m excited like the first time when I became an MVP :)
This time was the same.. anticipation, nervousness, uncertainty but then, around 4PM (Central European Time)…

“Dear Romeo Mlinar,
Congratulations! We are pleased to present you with the 2015 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in Hyper-V technical communities during the past year.”

Microsoft MVP Banner

I’m honored and proud with this prestigious award. I would like to thank to Microsoft and to Sarah Cooley (Hyper-V PGI Lead) and Ben Armstrong (Virtual PC Guy) as well, to all my dear friends and MVP fellows from all around the world. Special thanks to my MVP Lead Marina, to the local Microsoft office here in Croatia and to my the first MVP Lead Alessandro Teglia.
Big, big, big thanks to my dear friends Marin Franković, Igor Pavleković, Adis Jugo, Nenad Trajkovski, Tomica Kaniški, Charbel Nemnom, Tomislav Lulić, Ognjen Bajic, Bernardin Katić, Tomislav Tipurić, Damir Dizdarević, Omar Kudović, Enis Šahinović, Ekobit’s management, big thanks to my family, my wife and my son for their support and many, many others (sorry guys if I forgot someone. Have no enough space here to mention all of you :) )