Windows Server 2016 HyperV DEMO01: Hot Add/Remove Memory and Virtual Network Adapters

2 Min. Read

Hello folks,

In today’s demo, I would like to show you two big new features request in Windows Server 2016 Hyper-V for solving operational problems.

None of us would like to bring the workload offline in order to service the virtual machine.

1- Hot Add and Remove Memory for Static Virtual Machines:

As you know Microsoft introduced Dynamic memory back in Windows Server 2008 R2 SP1.
However we can’t use Dynamic memory on all our workloads like SQL or Exchange Server.
Microsoft is listening to us and they have added hot add and remove memory for Static Virtual Machines.
What is the requirements for static memory?
This is very specifically only if you’re running Windows 10 guests on Windows Server 2016 Hyper-V host, then you can go in with statically configured memory and change the memory both up and down while the virtual machine is running!

The interesting part is, If you go to the memory TAB in Hyper-V Manager console even though that this is static memory VM, we can actually see the memory on demand, thus you can size the memory effectively as well. This is fantastic!

2- Hot Add and Remove Virtual Network Adapters:

Hot add and remove virtual network adapters. This is for Generation TWO virtual machines only (WS2012 / W8, WS12R2 / W8.1 or WS2016 / W10 guests).
You can go in add or remove network adapters while the virtual machine is running!

The other interesting big feature is, the virtual network adapter identification or device naming, this one is actually very interesting.
When you add a virtual network adapter, you can give it a name which is then exposed inside the virtual machine.
You can enable Device naming through PowerShell or through the VM Settings under Network Adapter\Advanced Features, then from inside the virtual machine you can actually go and check, this adapter is that one, and the other adapter for that one. Very convenient and useful.

Let’s look together at those new features in action!


I hope you enjoyed the demo, and I would like to thank you for viewing.



DPM Protection Agent Failed Because The Service Did Not Respond! Internal error code: 0x8099090E

Windows Server 2016 HyperV DEMO02: Hyper-V Replica Support For Hot Add/Remove of VHDX


Let me know what you think, or ask a question...

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to Stay in Touch

Never miss out on your favorite posts and our latest announcements!

The content of this website is copyrighted from being plagiarized!

You can copy from the 'Code Blocks' in 'Black' by selecting the Code.

Please send your feedback to the author using this form for any 'Code' you like.

Thank you for visiting!