On 01/30/2011 06:37 PM, David Ahern wrote:
On 01/30/11 06:03, Avi Kivity wrote: >> 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). > I don't understand. If the host kernel is 2.6.27, qemu-kvm complains and refuses to open /dev/kvm. Your options are to upgrade the host kernel or use a newer kvm-kmod version. Are you saying kvm-kmod-2.6.37 is not advisable on 2.6.27? What about kvm-kmod-2.6.32.27?
No, that kvm-kmod-2.6.27, or a pure 2.6.27 isn't good. kvm-kmod-2.6.29+ over 2.6.27+ (for mmu notifiers) or a pure 2.6.29+ setup is fine. If you're careful with overcommit you might get away with a pre 2.6.27 host.
(but take all that with a grain of salt, I haven't run kvm-kmod for a long while apart from the RHEL 5 version, and I won't recommend anything outside a supported distro kernel or an active Linux stable/longterm tree).
-- 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
