[pve-devel] Hyper-V enlightenments with KVM

Alexandre DERUMIER aderumier at odiso.com
Wed Jan 21 10:58:15 CET 2015

>>So hv_vapic is known to make problems.

hv_apic in current kernel 3.10 is buggy on some processor (> Westmere),

I should be fixed in comming rhel 7.1 kernel

>>Not sure if we can/should add hv_time?

kernel 3.10 work fine currently

----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>, "Lindsay Mathieson" <lindsay.mathieson at gmail.com>
Envoyé: Mercredi 21 Janvier 2015 07:54:51
Objet: Re: [pve-devel] Hyper-V enlightenments with KVM

> From look at the kvm args in the process list I see we have: 
> hv_relaxed,hv_spinlocks=0xffff 
> but the current recomendations are: 
> hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time 

This is a comment from current code: 
if ($ost eq 'win7' || $ost eq 'win8' || $ost eq 'w2k8' || 
$ost eq 'wvista') { 
push @$globalFlags, 'kvm-pit.lost_tick_policy=discard'; 
push @$cmd, '-no-hpet'; 
#push @$cpuFlags , 'hv_vapic" if !$nokvm; #fixme, my win2008R2 hang at 
boot with this 
push @$cpuFlags , 'hv_spinlocks=0xffff' if !$nokvm; 

if ($ost eq 'win7' || $ost eq 'win8') { 
push @$cpuFlags , 'hv_relaxed' if !$nokvm; 

So hv_vapic is known to make problems. 

Not sure if we can/should add hv_time? 

pve-devel mailing list 
pve-devel at pve.proxmox.com 

More information about the pve-devel mailing list