Differences

This shows you the differences between two versions of the page.

--- kb:linux:kvm:hyperv_enightments [2015/12/12 21:27] – milano
+++ kb:linux:kvm:hyperv_enightments [2015/12/12 21:32] (current) – milano
@@ Line 5: / Line 5: @@
 Windows has support for several paravirt features that it will use when running on Hyper-V, Microsoft's hypervisor. These features are called enlightenments. Many of the features are similar to paravirt functionality that exists with Linux on KVM (virtio, kvmclock, PV EOI, etc.)
-Nowadays QEMU/KVM can also enable support for several Hyper-V enlightenments. When enabled, Windows VMs running on KVM will use many of the same paravirt optimizations they would use when running on Hyper-V. For detailed info, see Vadim's presentation from KVM Forum 2012.
+Nowadays QEMU/KVM can also enable support for several Hyper-V enlightenments. When enabled, Windows VMs running on KVM will use many of the same paravirt optimizations they would use when running on Hyper-V. For detailed info, see [[http://www.linux-kvm.org/images/0/0a/2012-forum-kvm_hyperv.pdf|Vadim's presentation from KVM Forum 2012]].
 From the QEMU/KVM developers, the recommended configuration is:
@@ Line 17: / Line 17: @@
  <features>
   <hyperv>
-   <relaxed state='on'/>
+   <relaxed state='on'/>   // only this option is supported on Centos 6.5 KVM hypervisor
    <vapic state='on'/>
    <spinlocks state='on' retries='8191'/>