Storage QoS for Hyper-V
You can use Windows Server 2016 and Windows Server 2012 R2 to configure QoS parameters for virtual
machine storage. You can now specify a maximum number of IOPS on a per-virtual-hard-disk basis. This
means that as an administrator, you can ensure that no single virtual machine consumes an excessive
amount of storage resources. You specify maximum and minimum values in terms of normalized IOPS;
every 8 kilobytes (KB) of data counts as a single I/O operation. You can also specify minimum IOPS
threshold values so that you are notified if a virtual hard disk falls below a specific performance thresh

Pass-through disks
Virtual machines use pass-through disks to access a physical disk drive rather than using a virtual hard
disk. You can use pass-through disks to connect a virtual machine directly to an Internet SCSI (iSCSI) LUN
or a directly attached disk. When you use pass-through disks, the virtual machine must have exclusive
access to the target disk. To do this, you must use the host’s Disk Management console to take the disk
offline. After the disk is offline, you can connect it to one of the virtual machine’s disk controllers.
You can attach a pass-through disk by performing the following steps:
1. Ensure that the target hard disk is offline.
2. Use Hyper-V Manager to edit an existing virtual machine’s properties.
3. Click an integrated drive electronics (IDE) or SCSI controller, click Add, and then click Hard Drive.
4. In the Hard Drive dialog box, select Physical Hard Disk. In the drop-down list box, select the disk
that you want to use as the pass-through disk.

Nested Virtualization

After enabling nested virtualization, you can install Hyper-V on a virtual machine the same way as you
would for a Hyper-V host. The following features are disabled or will fail after you enable nested
• Virtual-based security
• Device Guard
• Dynamic Memory
• Hot add Static Memory
• Checkpoints
• Live migration

Windows Server 2016 supports two types of containers, each offering different degrees of isolation and
having different requirements:
• Windows Server containers. Provide app isolation by using process and namespace isolation.
However, Windows Server containers share the operating system kernel with the host and with all
other containers running on the host. Therefore. this does not provide for complete isolation but does
provide for faster startup.
• Hyper-V containers. Provide for improved isolation by running each container in an optimized virtual
machine. This means that the kernel of the host is not shared with the containers.

Leave a Reply

Your email address will not be published. Required fields are marked *