Il 16/06/2014 18:47, John Nielsen ha scritto:
On Jun 16, 2014, at 10:39 AM, Paolo Bonzini 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", w
On Jun 16, 2014, at 10:39 AM, Paolo Bonzini 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 th
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 @
[Adding -devel to CC.]
I've opened a bug regarding this issue:
https://bugs.launchpad.net/qemu/+bug/1329956
I was unable to duplicate the issue in a different hypervisor, so it seems
likely the problem (or at least its solution) is in Qemu. Any ideas or feedback
still very much appreciated.
J
