Website under construction

 
Figure 2-21:
VM task manager showing memory usage 
Use the settings for VM2 to change the RAM used by this VM from 2 GB to 4 GB and then click Apply 
while the VM is still running. Within a few seconds, Hyper-V Manager shows that VM2 is now running 
with 4 GB of RAM, with no reboot necessary, as illustrated in Figure 2-22. 
Figure 2-22
VM memory settings changing while running 
Virtual Machine Connection shows that the clock is still running in VM2, and Task Manager displays 
4 GB of memory available to the VM, using the hot-add memory feature of Windows Server 2016, as 
shown in Figure 2-23. 

---

29 
CHAPTER 2 | Software-defined datacenter 
Figure 2-23:
VM Task Manager showing the VM with new memory 
Hot add and remove network adapters 
Adding or removing a network adapter while the VM is running without incurring downtime works 
only for Generation 2 VMs running either Windows or Linux. Supported Windows operating systems 
include Windows Server 2016. 
In the following example, connecting to the Generation 2 VM named VM1 using Virtual Machine 
Connection and opening the Network Connections folder shows that this VM has only a single 
network connection named Ethernet 2, as depicted in Figure 2-24. 
Figure 2-24:
Single VM NIC 
To hot-add another network adapter to this VM, in the Settings dialog box, on the Add Hardware 
page, select Network Adapter, as shown for VM1 in Figure 2-25. 

---

30 
CHAPTER 2 | Software-defined datacenter 
Figure 2-25:
Adding a NIC to a VM 
Note If the Network Adapter option is unavailable on the Add Hardware page of the Settings 
dialog box, it is because the VM is Generation 1, which does not support hot add and remove 
network adapter functionality. 
Click Apply for the changes to take effect. After a few seconds, the new network adapter is installed 
while the VM is still running, as shown in the Network Connections folder in Virtual Machine 
Connection. Figure 2-26, demonstrates that the hot-add of the network adapter is successful. 
Figure 2-26:
VM displaying the newly added NIC 

---

31 
CHAPTER 2 | Software-defined datacenter 
Failover cluster 
By John Marlin and Colin Robinson 
This section describes key improvements Microsoft has made to failover clustering in Windows Server 
2016. These improvements include the following: 

Cloud witness using Microsoft Azure 

Shared VHDX improvements 

Improved cluster logs 

Active memory dumps 

Network name diagnostics 

Cluster operating system rolling upgrade 

Workgroup and multidomain clusters 

SMB multichannel and multi-NIC cluster networks 

VM improvements 
In addition, Colin Robinson walks us through a detailed demonstration of performing a rolling 
upgrade on a failover cluster.