Matthias Hovestadt wrote:
Hi!
I am unable to reproduce - 'modprobe kvm' gets me the expected lsmod
line.
Can you reproduce with plain 2.6.27 instead of the gentoo build?
No, with a vanilla kernel from kernel.org it seems to work fine.
Please take it up with the gentoo kernel team then.
Matthias Hovestadt wrote:
Hi!
Manually loading the kvm_intel module fails with an Cannot allocate
memory error. Also starting VMs fails since he is unable to find
/dev/kvm.
Looks like a memory corruption issue. Please post your .config.
Here it is...
I am unable to reproduce -
Hi!
I am unable to reproduce - 'modprobe kvm' gets me the expected lsmod line.
Can you reproduce with plain 2.6.27 instead of the gentoo build?
No, with a vanilla kernel from kernel.org it seems to work fine.
asok04 ~ # uname -a
Linux asok04 2.6.27.19 #1 SMP Wed Mar 11 15:59:54 CET 2009
Hi!
Manually loading the kvm_intel module fails with an Cannot allocate
memory error. Also starting VMs fails since he is unable to find
/dev/kvm.
Looks like a memory corruption issue. Please post your .config.
Here it is...
Best,
Matthias
#
# Automatically generated make config:
Matthias Hovestadt wrote:
Hi!
I have a system with 2 processors and 4 cores each, which sums
up to 8 processors in total. I installed the system with Gentoo.2008
and KVM-84.
Linux asok04 2.6.27-gentoo-r8 #1 SMP Tue Mar 3 11:34:26 CET 2009
x86_64 Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
Hi Charles!
This mail seems to be somehow related to the bug report of Justin Keogh
from 30th Dec 2008. He was able to fix his problem by simply setting
CONFIG_KVM=m, but I'm already using modules, so his workaround can't be
applied here.
Quick question -- does your dmesg output include
Hi!
I have a system with 2 processors and 4 cores each, which sums
up to 8 processors in total. I installed the system with Gentoo.2008
and KVM-84.
Linux asok04 2.6.27-gentoo-r8 #1 SMP Tue Mar 3 11:34:26 CET 2009 x86_64
Intel(R) Xeon(R) CPU X5355 @ 2.66GHz GenuineIntel GNU/Linux
Everything
Matthias Hovestadt wrote:
This mail seems to be somehow related to the bug report of Justin Keogh
from 30th Dec 2008. He was able to fix his problem by simply setting
CONFIG_KVM=m, but I'm already using modules, so his workaround can't be
applied here.
Quick question -- does your dmesg output