Windows 8 Hyper-V Feature Glossary
Posted by Jordan_Tsafaridis , 22 March 2012 · 433 views
Αγαπητοί συνάδελφοι της κοινότητας σκοπός του συγκεκριμένου άρθρου είναι η καταγραφή και η παρουσίαση σε ένα πίνακα σε συνδυασμό με μια συνοπτική περιγραφή των χαρακτηριστικών τα οποία θα περιλαμβάνει ο επερχόμενος Microsoft Windows Server 8. Ο πίνακας αυτός θα ανανεώνεται κάθε φορά που θα παρουσιάζονται καινούρια χαρακτηριστικά μέχρι την επίσημη παρουσίαση και την έναρξη διάθεσης του Windows Server 8. Ελπίζω ότι θα συμφωνήσετε για την χρησιμότητά του.
features, you can create an active/active file share failover cluster. This
is supported for services that use large file with little metadata access,
e.g. Hyper-V. In other words, you can use a file share cluster instead of a SAN
for your Hyper-V cluster.
Hyper-V and Active/Active File Server roles
parent partition disks and cluster shared volumes using BitLocker for
physical security of virtual machines and data. Uses a Cluster Name Object
(CNO) for locking and unlocking CSVs.
Fibre Channel disks, rather than just the traditional VHD(X)
process for clustered hosts. It automatically drains hosts of VMs and patches
them in order.
at once between two hosts, with the only limit being your bandwidth.
by merging all of the various LAN, SAN, and cluster networks to a reduced
number of teamed high bandwidth NICs.
Although they are still NTFS, they appear as CSVFS for easier identification
as CSVs in disk administration tools.
networking protocols to run on the same network infrastructure, and therefore
helps enable the convergence of LANs and SANs onto a single unified fabric.
storage space that is required by not needlessly storing “empty” space (thin
provisioning) or redundant data (de-duplication)
DHCP services running in VMs.
Volumes (CSVs) can be backed up without Redirected I/O (Mode/Access).
draining VMs from the host
balloon down to the Minimum setting if it is underutilising the memory
allocated by the Startup setting.
processing VMQ n/w traffic across more than one CPU. It will automatically
scale up and scale down the CPU utilisation based on demand
network, this intelligent virtual switch offers extensibility for partners,
with products already announced by the likes of Cisco and Brocade.
based on application dependencies.
Clustering to restart or failover VMs based on monitored events that occur
inside of the VM.
of Non-Uniform Memory Architecture and can schedule processes in accordance
with memory placement at the physical layer. Guest NUMA can be customised on
a per-VM basis.
Clustering, allowing a service or VM to failover from one host to another,
enabling machine fault tolerance and maintenance windows with minimised
processors, up to 2 TB RAM, removal of the 8:1 logical to virtual processor
virtual machines from one location to another, supporting VSS snapshots,
failover, and IP address injection.
from the main host’s CPU to a dedicated processor on the network adapter
one host to another. This does not require Failover Clustering in Windows
first copying it and synchronising I/O until the source and destination are
identical. Can leverage Offloaded Data Transfer (ODX) in a SAN to make the
process up to 90% faster.
Virtualisation, PVLANs, and PORT ACLs, you can use Windows 8 Hyper-V in
multi-tenant environments such as IaaS public cloud hosting.
alignment for VHDs created on 4k sector physical disks, thus improving
IP address from physical IP address, allowing easier mobility of VMs across
fabrics. This is a key feature of multi-tenancy.
8 (and Hyper-V) for bandwidth aggregation and network path fault tolerance.
The NICs do not need to be from the same manufacturer.
storage faults and incrementally fix them with brief delays to I/O traffic
that don’t interrupt it. Should replace the need for
paths between virtual machines based on IP range or MAC address.
built-in PowerShell cmdlets. 100% of features are revealed via PowerShell.
in the physical network and there is a limit on how many can be configured.
Private VLANs allow Hyper-V to replace this physical networking feature.
minimum guarantees for network communications.
the same TCP/IP flow into one larger packet, reducing per-packet processing
costs for faster TCP/IP processing
network load from a network adapter to be shared across multiple processors
access of data on file shares.
memory on a per-VM basis. This data is stored with the VM and moves with the
to appear to be a number of physical NICs, and allows virtual machine
networking to bypass the virtual switch.
in Windows Server 8. Storage of VMs is supported on SMB 2.2. file shares. With
NIC teaming, you get multi-channel SMB.
a VM to merge a snapshot in Windows 8, resolving a major support issue.
without any RAID. They can be as loosely coupled as a bunch of USB drives.
The disks can be different sizes. A pool does not appear in Explorer. You can
create Storage Spaces from Storage Pools. This is one of the storage types
you could use to create a scalable and continuously available active/active
file share cluster.
of storage from a storage pool. Can be a 2-copy-mirror (Like RAID 1 in
concept and performance), 3-copy-mirror, or parity (like RAID 5 in concept
and performance) storage space. Can be lots of spaces in a single pool. A
space is divided up into slabs across disks in the pool depending on the
fault tolerance chosen. Advanced configuration allows you to choose which
pool disks to use.
in the Hyper-V Extensible Switch
type, expanding up to 16 TB, and supporting dynamic and fixed types.
adapter can be virtualised, thus enabling VMs to have their own WWN and
direct access to the SAN.
controllers are aware if they are Windows 8 Hyper-V VMs. This
prevents USN rollback (VM restore or snapshot application).
client operating system for free. It’s the same Hyper-V as in the server,
offering VM mobility and an easy introduction to Microsoft’s enterprise
virtualisation. The client version of Hyper-V requires Second Level
Address Translation (SLAT) in the CPU (Intel EPT, AMD RVI/NPT).
This is not a requirement in the server version, but it is recommended.