Re: OOPS loading kvm_intel or kvm_amd in kernel 3.2.77

From: astx
Date: Mon Feb 29 2016 - 13:07:56 EST


KVM - Oops is gone using kernel 3.2.78
Module kvm_intel and kvm_amd is now working as expected.

Thank you!

BR, Toni


Zitat von astx <astx@xxxxxxxxx>:

While trying to load module kvm_intel from kernel version 3.2.77 I get following Oops:


has_svm: not amd
kvm: no hardware support
BUG: unable to handle kernel NULL pointer dereference at 00000000000001f0
IP: [<ffffffffa021d865>] kvm_arch_init+0xe5/0x1c0 [kvm]
PGD 26052d067 PUD 28a417067 PMD 0
Oops: 0000 [#1] SMP
CPU 0
Modules linked in: kvm_intel(+) kvm ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit af_packet edd ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables microcode mperf dm_mod ata_generic ata_piix libata sg hpilo e1000e serio_raw iTCO_wdt pcspkr intel_agp intel_gtt button container joydev hpwdt iTCO_vendor_support ext4 jbd2 crc16 uhci_hcd sd_mod hpsa scsi_mod ehci_hcd fan processor thermal thermal_sys [last unloaded: freq_table]

Pid: 566, comm: modprobe Not tainted 3.2.77-277-smp_m_64 #1 HP PROLIANT DL120 G7
RIP: 0010:[<ffffffffa021d865>]Â [<ffffffffa021d865>] kvm_arch_init+0xe5/0x1c0 [kvm]
RSP: 0018:ffff880107d69e38Â EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffffffa023eab0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff880107d69e64 RDI: 0000000000000000
RBP: ffff880107d69e98 R08: 0000000000000000 R09: ffffe8ffffde1e20
R10: 0000000000000000 R11: ffff8802f539d000 R12: 0000000000000014
R13: 0000000000000013 R14: ffff880107d69e64 R15: ffffffffa0272e80
FS:Â 00007f426c421700(0000) GS:ffff88030bc00000(0000) knlGS:0000000000000000
CS:Â 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000000001f0 CR3: 000000010381a000 CR4: 00000000000406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 566, threadinfo ffff880107d68000, task ffff8802f2914000)
Stack:
Âffffffffa0273198 0000000000000030 ffff88030bfe6000 00000000a0273180
Âffff880107d69e68 0000000081839c60 00000000000000d0 00000000fffffff4
Âffffffffa0263d28 0000000000000010 0000000000003920 ffffffffa0273180
Call Trace:
Â[<ffffffffa020c8da>] kvm_init+0x2a/0x310 [kvm]
Â[<ffffffffa014c5e0>] ? vmx_check_processor_compat+0x64/0x64 [kvm_intel]
Â[<ffffffffa014c706>] vmx_init+0x126/0x1f6 [kvm_intel]
Â[<ffffffff8100214f>] do_one_initcall+0x3f/0x180
Â[<ffffffff8108ca50>] sys_init_module+0x90/0x1e0
Â[<ffffffff814cc5b2>] system_call_fastpath+0x16/0x1b
Code: 83 c3 04 41 83 fc 15 74 3d 8b 3b 4c 89 f6 e8 73 3c e1 e0 66 90 8b 7d cc 85 ff 78 df 81 3b 03 01 00 c0 75 c2 48 8b 05 f3 24 02 00 <ff> 90 f0 01 00 00 84 c0 75 b1 41 83 c4 01 48 83 c3 04 41 83 fc
RIPÂ [<ffffffffa021d865>] kvm_arch_init+0xe5/0x1c0 [kvm]
ÂRSP <ffff880107d69e38>
CR2: 00000000000001f0
---[ end trace 6f989560e7f26d23 ]---

_PART OF CPUINFO_:
processorÂÂÂÂÂÂ : 3
vendor_idÂÂÂÂÂÂ : GenuineIntel
cpu familyÂÂÂÂÂ : 6
modelÂÂÂÂÂÂÂÂÂÂ : 42
model nameÂÂÂÂÂ : Intel(R) Xeon(R) CPU E31220 @ 3.10GHz
steppingÂÂÂÂÂÂÂ : 7
microcodeÂÂÂÂÂÂ : 0x14
cpu MHzÂÂÂÂÂÂÂÂ : 3093.311
cache sizeÂÂÂÂÂ : 8192 KB
physical idÂÂÂÂ : 0
siblingsÂÂÂÂÂÂÂ : 4
core idÂÂÂÂÂÂÂÂ : 3
cpu coresÂÂÂÂÂÂ : 4
apicidÂÂÂÂÂÂÂÂÂ : 6
initial apicid : 6
fpuÂÂÂÂÂÂÂÂÂÂÂÂ : yes
fpu_exceptionÂÂ : yes
cpuid levelÂÂÂÂ : 13
wpÂÂÂÂÂÂÂÂÂÂÂÂÂ : yes
flagsÂÂÂÂÂÂÂÂÂÂ : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
bogomipsÂÂÂÂÂÂÂ : 6185.90
clflush sizeÂÂÂ : 64
cache_alignment : 64
address sizesÂÂ : 36 bits physical, 48 bits virtual
power management:

Attached my kernel config.gz
Up to kernel version 3.2.76 KVM subsystem was 100% OK and working flawless!
Another machine running AMD 16 core cpu has also problems loading kvm_amd from 3.2.77Â but was running fine with 3.2.76.

Maybe one can help me here.

BR, Toni