#358 kvm-80 AMD unknown symbols

closed
nobody
kernel (27)
5
2012-10-09
2008-12-08
Mishehu Mashehu
No

System is an Athlon64 Socket AM2, 1 dual core CPU, host OS is Slamd64 12.1 running kernel 2.6.27.7 (vanilla from kernel.org patched with Edward Shishkin's reiser4-for-2.6.27.patch).

Built kvm-80 using the following slackbuild script:

/ Script starts /

!/bin/sh

PKGNAM=kvm
VERSION=80
BUILD=1
TMP=/usr/local/src/kvm-80/tmp

. /etc/pkghelpers
pkghelpers_env

cd $TMP
tar xfv $CWD/$PKGNAM-$VERSION.tar.gz || exit 1
cd $PKGNAM-$VERSION
./configure \ --prefix=/usr \ #--with-patched-kernel \ --enable-mixemu \ --audio-drv-list=alsa \ --disable-gcc-check
make -j5 || exit 1

make install DESTDIR=$PKG

cd $PKG
mv usr/share/man usr/man
mkdir install
cat $CWD/slack-desc > install/slack-desc
pkghelpers_fixup
pkghelpers_makepkg

/ script ends /

Everybody builds fine (minus an occasional compiler warning), and I end up with /lib/modules/2.6.27.7/extra/kvm.ko , kvm-amd.ko, and kvm-intel.ko after I install the newly created slackpack.

However, whenever I attempt to modprobe the modules, I get the following:

kvm: Unknown symbol intel_iommu_domain_alloc
kvm: Unknown symbol intel_iommu_detach_dev
kvm: Unknown symbol intel_iommu_page_mapping
kvm: Unknown symbol intel_iommu_context_mapping
kvm: Unknown symbol intel_iommu_iova_to_pfn
kvm: Unknown symbol intel_iommu_domain_exit
kvm_amd: Unknown symbol kvm_exit
kvm_amd: Unknown symbol kvm_init
kvm_amd: Unknown symbol kvm_enable_efer_bits
kvm_amd: Unknown symbol kvm_timer_intr_post
kvm_amd: Unknown symbol kvm_get_msr_common
kvm_amd: Unknown symbol kvm_vcpu_uninit
kvm_amd: Unknown symbol kvm_emulate_halt
kvm_amd: Unknown symbol kvm_lapic_find_highest_irr
kvm_amd: Unknown symbol kvm_task_switch
kvm_amd: Unknown symbol kvm_enable_tdp
kvm_amd: Unknown symbol kvm_disable_tdp
kvm_amd: Unknown symbol kvm_queue_exception
kvm_amd: Unknown symbol emulate_instruction
kvm_amd: Unknown symbol fx_init
kvm_amd: Unknown symbol kvm_cpu_has_interrupt
kvm_amd: Unknown symbol kvm_lapic_get_cr8
kvm_amd: Unknown symbol kvm_get_cr8
kvm_amd: Unknown symbol kvm_x86_ops
kvm_amd: Unknown symbol kvm_vcpu_cache
kvm_amd: Unknown symbol kvm_emulate_hypercall
kvm_amd: Unknown symbol load_pdptrs
kvm_amd: Unknown symbol kvm_handle_fault_on_reboot
kvm_amd: Unknown symbol kvm_mmu_unprotect_page_virt
kvm_amd: Unknown symbol kvm_get_cs_db_l_bits
kvm_amd: Unknown symbol kvm_mmu_page_fault
kvm_amd: Unknown symbol kvm_lapic_set_tpr
kvm_amd: Unknown symbol kvm_mmu_reset_context
kvm_amd: Unknown symbol kvm_queue_exception_e
kvm_amd: Unknown symbol kvm_emulate_cpuid
kvm_amd: Unknown symbol kvm_vcpu_init
kvm_amd: Unknown symbol kvm_set_msr_common
kvm_amd: Unknown symbol kvm_mmu_load
kvm_amd: Unknown symbol kvm_cpu_get_interrupt
kvm_amd: Unknown symbol kvm_emulate_pio

I have tried multiple fresh reconfiguration/recompilations of the kernel and turn up the same result. Since everything else appears fine up to this point, and since nobody on the irc channel could tell what is the issue, it appears to be a bug.

Discussion

  • Most recent kernel 2.6.27.7 configuration

     
    Attachments
  • I managed to stumble upon a solution for this. Although one of the fellow users on the #kvm channel didn't think it was the CONFIG_DMAR in the kernel, I came across another posting on a newsgroup. I have since disabled DMAR and I have been able to successfully been able to insert the module.