On 06/08/2010 03:49 PM, Peter Lieven wrote:
And finally, perhaps you have NX disabled in the bios of one of the
machines?
What does 'dmesg | grep NX' show on both hosts?
nx was disabled on one of the nodes.
That explains the problem.
i will retry the case later today and send info register output.
what is the recommended value for nx (and why)?
Enabled (so you get no-execute memory protection).
and why was it working with 2.6.34 and is not with 2.6.35-rc2?
We fixed a different bug. But you shouldn't live migrate from a machine
with nx to a machine without nx, unless you use -cpu ...,-nx on both nodes.
--
error compiling committee.c: too many arguments to function
--
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
