Hyper-V
Discussion Question 1:
To configure and allocate memory size for a virtual machine (VM), a user will navigate to virtual machine settings and create a “Startup RAM” that associates with the VM as well as the VM itself. Open the Hyper-V Manager by clicking on start, navigate to Administrative Tools, and then click on Hyper-V Manager. Under the Virtual Machines in the results from the Action Pane, click on New option then select Virtual Machine. From the pop-up wizard, select Next. Make appropriate choices for the two VMs on each page. A summary of the picks will be displayed; if they are okay, click finish. In Hyper-V Manager, select the virtual machine by right-clicking and then select the connect option. The summary will contain everything that has been optimized include memory, name, generation, network, hard disk, and operating system. In the VM’s connection window, select Action, then Start. A VM can also be created using Windows PowerShell. Windows Server 2016 has Runtime Memory Resize capability (hot-add/remove memory). It is the ability to add and remove memory for a running VM that is entirely distinct from Dynamic Memory. The memory assigned to the VM will vary depending on the actual utilization within the guest operating system.
Discussion Question 2:
Microsoft Hyper-V Server 2016 is a lone product that has only a Windows Server driver architecture, the Windows hypervisor, and components used for virtualization. Hyper-V provides a simple as well as reliable virtualization option to aid in improving server utilization and is cost-effective. Without dedicated Hyper-V hosts, a suitable solution would be to have nested virtualization, which means running a hypervisor within a VM. This is useful in running emulators or performing configuration tests that will require an ordinary host. To configure nested virtualization, create a VM. While the VM is in the OFF mode, run the following command on the physical host.
It will enable nested virtualization for the VM. Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true. After running the command, start the VM. Proceed to install the Hyper-V within the VM, just like in the case of a physical server. When Hyper-V is running within the VM, the VM must be turned off to adjust the memory. It implies that the amount of memory will not change even if the dynamic memory is on. It should be noted that enabling nested virtualization will not have any effect on runtime memory or dynamic memory resize. There are two options for networking when using nested VM that include Mac address spoofing and NAT networking.