Changes

- '''Hyper-V Aware Windows Operating Systems''' - Hyper-V aware Windows operating systems (also referred to as ''enlightened'' operating systems) are able to detect that they are running on the Hyper-V hypervisor and modify behavior to maximize performance(such as using hypercalls to directly call the hypervisor). In addition, these operating systems are able to host the Integration Services to perform such tasks as running Virtual Service Clients (VSCs) which communicate over the VMBus with the Virtual Service Providers (VSPs) running on the root partition for device access.

- '''Hyper-V Aware Non-Windows Operating Systems''' - Non-Windows Hyper-V aware operating systems are also able to run Integration Services and, through the use of VSCs supplied by third parties, access devices via the root partition VSPs. The enlightened operating systems are also able to modify behavior to optimize performance and communicate directly with the hypervisor using hypercalls.

- '''Non Hyper-V Aware Operating Systems''' - These operating systems are unaware that they are running on a hypervisor and are unable to run the Integration Services. To support these operating systems, the Hyper-V hypervisor uses emulation to provide access to device and CPU resources. Whilst this approach allows unmodified, unenlightened operating systems to function within Hyper-V virtual machines, the overheads inherent in the emulation process can be significant.