On 01/27/2011 08:09 PM, David Ahern wrote:
On 01/27/11 02:55, Avi Kivity wrote: > On 01/26/2011 06:51 PM, Asdo wrote: >> Some time ago in this list it was mentioned that old kernels pre-2.6.28 >> don't work well with KVM. >> (in particular we have a machine with 2.6.24) >> > > pre 2.6.27 kernels don't have mmu notifiers and thus don't handle > overcommit well. No idea if there's anything wrong with 2.6.27 itself. The KVM code in the 2.6.27 kernel is broken. qemu-kvm emits: KVM kernel module broken (DESTROY_MEMORY_REGION). Please upgrade to at least kernel 2.6.29 or recent kvm-kmod (see http://sourceforge.net/projects/kvm). You'll need to use newer kvm-kmod versions.
Ah, but that's not a host kernel issue. So you could have kvm-kmod-2.6.37 atop 2.6.27 (still I wouldn't recommend it).
-- 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
