What is new in Windows Server 2012 R2 concerning to Hyper-V?
- New VMs of the second generation, called Gen2 VM. Gen1 VM actually have a very old hardware.Gen2 VMs booting faster, and the operating systems can install quicker. You use UEFI boot from virtual SCSI drives or network. Posssible guest operating systems are only Windows Server 2012 and Windows 8 or higher (64 bits each). A change or a migration from Gen1 to Gen2 VM-VM is not possible. Gen1 VM are still supported in Windows Server 2012 R2.
- Access to machines is now also possible without a network connection (Enhanced VM Interaction), clipboard, file exchange
- Live migration has been significantly accelerated by different techniques (data compression, RDMA and SMB Multichannel)
- VMs in VHDX format allow you to change the size now in operation. This only works for drives that are attached to a virtual SCSI controller.
- A VM can be exported without shutdown
- Hyper-V Replica (running machine in duplicate external data center) now offers three different intervals: 30 seconds, 5 minutes or 15 minutes. In addition, several replications can be set (eg host 1 to host 2 to host 3 – so-called extended replication).
- Shared noting live migration from 2012-2012 R2 is possible (for migration scenarios)
- Linux gets dynamic memory, online memory, online VHDX resize and new graphics drivers
- Storage QOS: bandwidth for storage is more effectively distributed. VMs that require a lot of bandwidth, can not consume the whole bandwidth with Storage QOS enabled. A minimum bandwidth can be defined. Basic unit in MS is IOPS. IOPS are 8K by default.
- Guest clustering with shared virtualDisk: eg SQL hereby can get access to the same cluster VHDx. Both machines can obtain the VHDX via a virtual SAS interface connected.
- SMB direct: Machine data can be transmitted via SMB. Several NICs may be used simultaneously. SMB Direct cards are also supported . SMB over RDMA provides high performance.
- Snapshots are now called checkpoints
- Virtual machines can be migrated to Azure
- A newly installed server with normal GUI and the Hyper-V role requires approximately 12 GB of space
- Nested Virtualization – eg Hyper-V Server on Hyper-V server is still not working. I would love to have it for lab or demo. But there aren not enough requests for it that Microsoft will implement it.
- An ISO file can not still integrate over the network. Why not? Wan’t to have all my isos in one place on a server!
The VM-generation selection in Windows Server 2012 R2
Dynamic or static RAM allocation? Windows Server 2012 R2
Display the VM generation in Hyper-V Manager
A Gen1 VM in Hyper-V Manager – looks familiar
Properties of a Gen2 VM in Hyper-V Manager – not quite as before – IDE, legacy, legacy BIOS completely missing…