Il 16/06/2014 18:47, John Nielsen ha scritto:
On Jun 16, 2014, at 10:39 AM, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote:
Il 16/06/2014 18:09, John Nielsen ha scritto:
The only substantial difference on the hardware side is the CPU.
The hosts where the problem occurs use "Intel(R) Xeon(R) CPU
E5-2650 v2 @ 2.60GHz", while the hosts that don't show the
problem use the prior revision, "Intel(R) Xeon(R) CPU E5-2650 0 @
2.00GHz".
Can you do "grep . /sys/module/kvm_intel/parameters/*" on both hosts please?
No differences that I can see. Output below.
Not really:
Working host:
Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
# grep . /sys/module/kvm_intel/parameters/*
/sys/module/kvm_intel/parameters/enable_apicv:N
Problem host:
Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
# grep . /sys/module/kvm_intel/parameters/*
/sys/module/kvm_intel/parameters/enable_apicv:Y
So we have a clue. Let me study the code more, I'll try to get back
with a suggestion.
In the meanwhile, I'm CCing the KVM list and BCCing QEMU, so that
follow-ups come to the KVM list.
Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
