Lost KVM after upgrade to 1.7

[tauronik]

Hi all,

after updating from 1.6 to 1.7 via apt-get I lost the possibility to start/use KVM. In the kernel.log I have:

kernel: kvm: disagrees about version of symbol smp_ops
kernel: kvm: Unknown symbol smp_ops
kernel: kvm_amd: Unknown symbol kvm_exit
kernel: kvm_amd: Unknown symbol kvm_init
kernel: kvm_amd: Unknown symbol kvm_enable_efer_bits
kernel: ....

I even updated to the latest pvetest to no avail:

pveversion -v
pve-manager: 1.7-12 (pve-manager/1.7/5490)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
qemu-server: 1.1-29
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-1
ksm-control-daemon: 1.0-5

I had KVM guests running before but they won't start anymore. There is no possibility to build new kvm guests.

And YES, virtualisation is enabled:

cat /proc/cpuinfo
...
model name      : AMD Athlon(tm) II X2 250 Processor
stepping        : 3
cpu MHz         : 3012.874
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
...

Anyone any ideas?

TIA
Michael

 

[dietmar]

already rebooted the host (because of new kernel)?

 

[tauronik]

Thanks for looking into this issue.

already rebooted the host (because of new kernel)?

Yes of course. Even did a cold reboot.
Any other ideas?

 

[m.ardito]

did you try to plug off the ac cable? for weird itr seems, this solved me a vt reported "present" but not working, until i plugged og the cable, waited and booted the machine again...

see http://forum.proxmox.com/threads/99...-virtual-machines-(no-Intel-VT-AMD-V-support)

Marco

 

[dietmar]

what is the output of:

# modinfo kvm-amd

 

[tauronik]

@dietmar

root# modinfo kvm-amd
filename:       /lib/modules/2.6.32-4-pve/kernel/arch/x86/kvm/kvm-amd.ko
license:        GPL
author:         Qumranet
depends:        kvm
vermagic:       2.6.32-4-pve SMP mod_unload modversions
parm:           npt:int
parm:           nested:int

@marco
I had a totally cold reboot, even with unplugging ac cable. Nothing changed.

 

[dietmar]

what is the output of:

# md5sum /lib/modules/2.6.32-4-pve/kernel/arch/x86/kvm/kvm-amd.ko

 

[tauronik]

Here is the ouput

root# md5sum /lib/modules/2.6.32-4-pve/kernel/arch/x86/kvm/kvm-amd.ko
e411be177ea3986d46fb0c486f0f55e7  /lib/modules/2.6.32-4-pve/kernel/arch/x86/kvm/kvm-amd.ko

 

[dswartz]

Might it be easier at this point to just reinstall with 1.7 and then restore your VMs?

 

[tauronik]

Might it be easier at this point to just reinstall with 1.7 and then restore your VMs?

That's an option, of course. But before I do that, I want to know what went wrong. This server will go to production state and I must confirm that updates run smoothly.

 

[tom]

just did some test with our amd boxes in the lab, no issues. but I do not have exact the same cpu.

 

[tauronik]

just did some test with our amd boxes in the lab, no issues. but I do not have exact the same cpu.

Thanks for your effort. As I wrote before, all systems up and running on 1.6. Then did an upgrade and kvm went away.

Probably I will re-install from scratch

 

[tom]

I am not sure if this helps - 1.7 is out since a long time and we had no such issue. try a mainboard bios upgrade, just to make sure that a already solved bios bug is not the reason.

 

[tauronik]

I think there is no newer BIOS update for my mobo, but I will double-check. Anyway, I will re-install in a few days (to busy right now) and report back.

 

[Fra]

I think there is no newer BIOS update for my mobo, but I will double-check. Anyway, I will re-install in a few days (to busy right now) and report back.

Hi tauronik, did you solve the issue?
I have exactly the same problem

 

[tauronik]

Hi oriettaxx,

this is an old thread but I will answer for anyone looking here in.

The bad news: Only re-installing from scratch solved my problem. I had all my data on a seperate LVM drive so I had my data at hand and only lost my ISO dir. Be sure to backup everything and then go the way re-installing. It will be by far the fastest solution. I hope this will never strike again.

Heads up, strong coffee and hey, proxmox is free ... ist's as always : you get what you pay for

Michael