Could not access KVM kernel module after upgradeing to 3.4-6

skeates

New Member
Feb 12, 2015
24
0
1
I did an upgrade today of Proxmox to version 3.4-6 I did not take a note of the previose version which was 3.4-something.

I've done upgrades in the past and they have been fine. I was told after the update that there had been a patch to the kernal ( think that was the termenolgy might have been update) and I should reboot this node when I have a chance. I procedded to reboot the node and the machine came backup as normal.

Although none of the VM's will start up. I am getting the following errors:

Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm -id 110 -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/110.vnc,x509,password -pidfile /var/run/qemu-server/110.pid -daemonize -smbios 'type=1,uuid=22951564-f8ae-4ce1-b247-b664ca248be6' -name KerioOperator -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 4096 -k en-gb -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:67b81728199' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/var/lib/vz/images/110/vm-110-disk-1.vmdk,if=none,id=drive-sata0,format=vmdk,aio=native,cache=none,detect-zeroes=on' -device 'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/kerio-operator-installer-2.3.3-3740-p2.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap110i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=5A:3C:E1:37:70:33,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

Has anyone got any ideas of where I can start to look to resolve this problem. Just as a note this install of Proxmox is runnig on a MacMini and has been running fine for about 5 months and I have upgraded proxmox in the same fasion previously with not problem even going from 3.2 to 3.3 to 3.4
 

skeates

New Member
Feb 12, 2015
24
0
1
Just an update this is still an issue, but disabling KVM Hardware virtulization on the VM appears to let the VM's start up, but very slowly. Any ideas?
 

skeates

New Member
Feb 12, 2015
24
0
1
Are you sure that cpu vt-x extension is enabled in your bios ? (Dont known how it's work in mac mini)

I've checked a few times now and from all I can see it is enabled. It was working fine before the update and even after the update it was working ok it was only after I rebooted the system that it stopped working and I assume that was when the kernel update/patch was applied.

I've installed and run rdmsr 0x3A and got a return of 5 which means VT extensions are enabled on the CPU. The mac mini has no bios as such, but it has always worked from day one.

Is there anyway for me to tell what was patched in the kernel and possibly undo it? Any other thoughts would be great.
 

skeates

New Member
Feb 12, 2015
24
0
1
So just did a search and found the apt logs from the update. At the bottom of the Term log are some errors would this be what has possibly caused the problem?

history log:

Code:
Start-Date: 2015-06-07  14:45:48
Commandline: apt-get dist-upgrade
Install: pve-kernel-2.6.32-39-pve:amd64 (2.6.32-156, automatic)
Upgrade: libpve-storage-perl:amd64 (3.0-32, 3.0-33), pve-qemu-kvm:amd64 (2.2-8, 2.2-10), libnvpair1:amd64 (0.6.3-3~wheezy, 0.6.4-3~wheezy), proxmox-ve-2.6.32:amd64 (3.4-150, 3.4-156), qemu-server:amd64 (3.4-3, 3.4-6), grub-pc:amd64 (2.02~bpo70+3, 2.02~bpo70+6), pve-manager:amd64 (3.4-3, 3.4-6), libzpool2:amd64 (0.6.3-3~wheezy, 0.6.4-3~wheezy), pve-cluster:amd64 (3.0-16, 3.0-17), libuutil1:amd64 (0.6.3-3~wheezy, 0.6.4-3~wheezy), libzfs2:amd64 (0.6.3-3~wheezy, 0.6.4-3~wheezy), grub-pc-bin:amd64 (2.02~bpo70+3, 2.02~bpo70+6), libcurl3-gnutls:amd64 (7.26.0-1+wheezy12, 7.26.0-1+wheezy13), grub-common:amd64 (2.02~bpo70+3, 2.02~bpo70+6), grub2-common:amd64 (2.02~bpo70+3, 2.02~bpo70+6)
End-Date: 2015-06-07  14:46:07

Term log:



Code:
Log started: 2015-06-07  14:45:48
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 39832 files and directories currently installed.)
Preparing to replace libcurl3-gnutls:amd64 7.26.0-1+wheezy12 (using .../libcurl3-gnutls_7.26.0-1+wheezy13_amd64.deb) ...
Unpacking replacement libcurl3-gnutls:amd64 ...
Preparing to replace libuutil1 0.6.3-3~wheezy (using .../libuutil1_0.6.4-3~wheezy_amd64.deb) ...
Unpacking replacement libuutil1 ...
Preparing to replace libnvpair1 0.6.3-3~wheezy (using .../libnvpair1_0.6.4-3~wheezy_amd64.deb) ...
Unpacking replacement libnvpair1 ...
Preparing to replace libzpool2 0.6.3-3~wheezy (using .../libzpool2_0.6.4-3~wheezy_amd64.deb) ...
Unpacking replacement libzpool2 ...
Preparing to replace libzfs2 0.6.3-3~wheezy (using .../libzfs2_0.6.4-3~wheezy_amd64.deb) ...
Unpacking replacement libzfs2 ...
Preparing to replace grub-pc 2.02~bpo70+3 (using .../grub-pc_2.02~bpo70+6_amd64.deb) ...
Unpacking replacement grub-pc ...
Preparing to replace grub-pc-bin 2.02~bpo70+3 (using .../grub-pc-bin_2.02~bpo70+6_amd64.deb) ...
Unpacking replacement grub-pc-bin ...
Preparing to replace grub2-common 2.02~bpo70+3 (using .../grub2-common_2.02~bpo70+6_amd64.deb) ...
Unpacking replacement grub2-common ...
Preparing to replace grub-common 2.02~bpo70+3 (using .../grub-common_2.02~bpo70+6_amd64.deb) ...
Unpacking replacement grub-common ...
Preparing to replace libpve-storage-perl 3.0-32 (using .../libpve-storage-perl_3.0-33_all.deb) ...
Unpacking replacement libpve-storage-perl ...
Selecting previously unselected package pve-kernel-2.6.32-39-pve.
Unpacking pve-kernel-2.6.32-39-pve (from .../pve-kernel-2.6.32-39-pve_2.6.32-156_amd64.deb) ...
Preparing to replace pve-qemu-kvm 2.2-8 (using .../pve-qemu-kvm_2.2-10_amd64.deb) ...
Unpacking replacement pve-qemu-kvm ...
Preparing to replace pve-cluster 3.0-16 (using .../pve-cluster_3.0-17_amd64.deb) ...
Unpacking replacement pve-cluster ...
Preparing to replace qemu-server 3.4-3 (using .../qemu-server_3.4-6_amd64.deb) ...
Unpacking replacement qemu-server ...
Preparing to replace pve-manager 3.4-3 (using .../pve-manager_3.4-6_amd64.deb) ...
Unpacking replacement pve-manager ...
Preparing to replace proxmox-ve-2.6.32 3.4-150 (using .../proxmox-ve-2.6.32_3.4-156_all.deb) ...
Unpacking replacement proxmox-ve-2.6.32 ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Processing triggers for pve-firewall ...
Restarting Proxmox VE firewall: pve-firewall.
Setting up libcurl3-gnutls:amd64 (7.26.0-1+wheezy13) ...
Setting up libuutil1 (0.6.4-3~wheezy) ...
Setting up libnvpair1 (0.6.4-3~wheezy) ...
Setting up libzpool2 (0.6.4-3~wheezy) ...
Setting up libzfs2 (0.6.4-3~wheezy) ...
Setting up grub-common (2.02~bpo70+6) ...
Installing new version of config file /etc/grub.d/10_linux ...
Installing new version of config file /etc/grub.d/30_os-prober ...
Installing new version of config file /etc/grub.d/20_linux_xen ...
Setting up grub2-common (2.02~bpo70+6) ...
Setting up grub-pc-bin (2.02~bpo70+6) ...
Setting up grub-pc (2.02~bpo70+6) ...
Installing for i386-pc platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-2.6.32-39-pve
Found linux image: /boot/vmlinuz-2.6.32-37-pve
Found initrd image: /boot/initrd.img-2.6.32-37-pve
Found linux image: /boot/vmlinuz-2.6.32-34-pve
Found initrd image: /boot/initrd.img-2.6.32-34-pve
Found linux image: /boot/vmlinuz-2.6.32-32-pve
Found initrd image: /boot/initrd.img-2.6.32-32-pve
Found linux image: /boot/vmlinuz-2.6.32-26-pve
Found initrd image: /boot/initrd.img-2.6.32-26-pve
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
done
Setting up libpve-storage-perl (3.0-33) ...
Setting up pve-kernel-2.6.32-39-pve (2.6.32-156) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-39-pve /boot/vmlinuz-2.6.32-39-pve
update-initramfs: Generating /boot/initrd.img-2.6.32-39-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.32-39-pve /boot/vmlinuz-2.6.32-39-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-2.6.32-39-pve
Found initrd image: /boot/initrd.img-2.6.32-39-pve
Found linux image: /boot/vmlinuz-2.6.32-37-pve
Found initrd image: /boot/initrd.img-2.6.32-37-pve
Found linux image: /boot/vmlinuz-2.6.32-34-pve
Found initrd image: /boot/initrd.img-2.6.32-34-pve
Found linux image: /boot/vmlinuz-2.6.32-32-pve
Found initrd image: /boot/initrd.img-2.6.32-32-pve
Found linux image: /boot/vmlinuz-2.6.32-26-pve
Found initrd image: /boot/initrd.img-2.6.32-26-pve
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
done
Setting up pve-qemu-kvm (2.2-10) ...
Setting up pve-cluster (3.0-17) ...
Restarting pve cluster filesystem: pve-cluster.
Setting up qemu-server (3.4-6) ...
Setting up pve-manager (3.4-6) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE API Proxy Server: pveproxy.
Restarting PVE SPICE Proxy Server: spiceproxy.
Restarting PVE Status Daemon: pvestatd.
Setting up proxmox-ve-2.6.32 (3.4-156) ...
installing proxmox release key: OK
Log ended: 2015-06-07  14:46:07


Log started: 2015-06-07  15:12:38
Selecting previously unselected package qemu-utils.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 42325 files and directories currently installed.)
Unpacking qemu-utils (from .../qemu-utils_1.1.2+dfsg-6a+deb7u7_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/qemu-utils_1.1.2+dfsg-6a+deb7u7_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man8/qemu-nbd.8.gz', which is also in package pve-qemu-kvm 2.2-10
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package sharutils.
Unpacking sharutils (from .../sharutils_1%3a4.11.1-1_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Errors were encountered while processing:
 /var/cache/apt/archives/qemu-utils_1.1.2+dfsg-6a+deb7u7_amd64.deb
 

spirit

Famous Member
Apr 2, 2010
5,680
623
133
www.odiso.com
qemu-utils from debian package should not be installed !

it's conflict with proxmox, and I think you have also installed qemu.

I think qemu package from debian have replaced pve-qemu-kvm from proxmox, that could explain the kvm error.

can you try:

apt-get install pve-qemu-kvm ?
 

skeates

New Member
Feb 12, 2015
24
0
1
maybe can you try to boot on older kernel ?

also, maybe can you try pve-kernel-3.10 ?

I've just tried rebooting the machine with all of the following and the same issue appears, so I guess it must be something else that has gone wrong

2.6.32-39-pve
2.6.32-37-pve
2.6.32-34-pve
2.6.32-32-pve
2.6.32-26-pve
 

skeates

New Member
Feb 12, 2015
24
0
1
That was probably me trying find out what was going on initially. I just ran the following

Code:
[FONT=Menlo]root@proxmox:~# apt-get remove qemu-utils[/FONT]
[FONT=Menlo]Reading package lists... Done[/FONT]
[FONT=Menlo]Building dependency tree       [/FONT]
[FONT=Menlo]Reading state information... Done[/FONT]
[FONT=Menlo]Package 'qemu-utils' is not installed, so not removed[/FONT]
[FONT=Menlo]0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.[/FONT]
Code:
[FONT=Menlo]root@proxmox:~# apt-get remove qemu[/FONT]
[FONT=Menlo]Reading package lists... Done[/FONT]
[FONT=Menlo]Building dependency tree       [/FONT]
[FONT=Menlo]Reading state information... Done[/FONT]
[FONT=Menlo]Package 'qemu' is not installed, so not removed[/FONT]
[FONT=Menlo]0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.[/FONT]
Code:
[FONT=Menlo]root@proxmox:~# apt-get install pve-qemu-kvm[/FONT]
[FONT=Menlo]Reading package lists... Done[/FONT]
[FONT=Menlo]Building dependency tree       [/FONT]
[FONT=Menlo]Reading state information... Done[/FONT]
[FONT=Menlo]pve-qemu-kvm is already the newest version.[/FONT]
[FONT=Menlo]0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.[/FONT]
 

skeates

New Member
Feb 12, 2015
24
0
1
can you do a:

#lsmod|grep kvm


to see if kvm module is loaded ? (it should be if vt-x is enabled is bios)

Code:
[FONT=Menlo]root@proxmox:~#  #lsmod|grep kvm
[/FONT][FONT=Menlo]root@proxmox:~#[/FONT]


So that would imply it is not enabled, but there is no reason for it not to be as it was working prior to the update.
 
Last edited:

spirit

Famous Member
Apr 2, 2010
5,680
623
133
www.odiso.com
Code:
[FONT=Menlo]root@proxmox:/var/log/apt#  #lsmod|grep kvm[/FONT][FONT=Menlo]root@proxmox:/var/log/apt#[/FONT]


So that would imply it is not enabled, but there is no reason for it not to be as it was working prior to the update.

ok, so we are sure it's come from the kernel.

just to be sure :

#uname -a ?
 

skeates

New Member
Feb 12, 2015
24
0
1
Outputs nothing same as the previous command

Code:
[FONT=Menlo]root@proxmox:~# #uname -a[/FONT]
[FONT=Menlo]root@proxmox:~#[/FONT]

Just ran

Code:
[FONT=Menlo]root@proxmox:~# uname -a[/FONT]
[FONT=Menlo]Linux proxmox 2.6.32-39-pve #1 SMP Fri May 8 11:27:35 CEST 2015 x86_64 GNU/Linux[/FONT]
[FONT=Menlo]root@proxmox:~#[/FONT]
 
Last edited:

skeates

New Member
Feb 12, 2015
24
0
1
Tried that it seems to error so not sure if that means something is not installed correctly or something has become corrupt

Code:
[FONT=Menlo]root@proxmox:~# modprobe kvm[/FONT][FONT=Menlo]root@proxmox:~# modprobe kvm_intel[/FONT]
[FONT=Menlo]ERROR: could not insert 'kvm_intel': Unknown symbol in module, or unknown parameter (see dmesg)[/FONT]
[FONT=Menlo]root@proxmox:~#[/FONT]

I just ran cat /proc/cpuinfo to double check the CPU and the output I get is below if that makes helps any.

Code:
[FONT=Menlo]root@proxmox:~# cat /proc/cpuinfo[/FONT][FONT=Menlo]processor    : 0[/FONT]
[FONT=Menlo]vendor_id    : GenuineIntel[/FONT]
[FONT=Menlo]cpu family    : 6[/FONT]
[FONT=Menlo]model        : 58[/FONT]
[FONT=Menlo]model name    : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz[/FONT]
[FONT=Menlo]stepping    : 9[/FONT]
[FONT=Menlo]microcode    : 21[/FONT]
[FONT=Menlo]cpu MHz        : 2494.139[/FONT]
[FONT=Menlo]cache size    : 3072 KB[/FONT]
[FONT=Menlo]physical id    : 0[/FONT]
[FONT=Menlo]siblings    : 4[/FONT]
[FONT=Menlo]core id        : 0[/FONT]
[FONT=Menlo]cpu cores    : 2[/FONT]
[FONT=Menlo]apicid        : 0[/FONT]
[FONT=Menlo]initial apicid    : 0[/FONT]
[FONT=Menlo]fpu        : yes[/FONT]
[FONT=Menlo]fpu_exception    : yes[/FONT]
[FONT=Menlo]cpuid level    : 13[/FONT]
[FONT=Menlo]wp        : yes[/FONT]
[FONT=Menlo]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 xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt[/FONT]
[FONT=Menlo]bogomips    : 4988.27[/FONT]
[FONT=Menlo]clflush size    : 64[/FONT]
[FONT=Menlo]cache_alignment    : 64[/FONT]
[FONT=Menlo]address sizes    : 36 bits physical, 48 bits virtual[/FONT]
[FONT=Menlo]power management:[/FONT]
[FONT=Menlo]
[/FONT]
[FONT=Menlo]processor    : 1[/FONT]
[FONT=Menlo]vendor_id    : GenuineIntel[/FONT]
[FONT=Menlo]cpu family    : 6[/FONT]
[FONT=Menlo]model        : 58[/FONT]
[FONT=Menlo]model name    : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz[/FONT]
[FONT=Menlo]stepping    : 9[/FONT]
[FONT=Menlo]microcode    : 21[/FONT]
[FONT=Menlo]cpu MHz        : 2494.139[/FONT]
[FONT=Menlo]cache size    : 3072 KB[/FONT]
[FONT=Menlo]physical id    : 0[/FONT]
[FONT=Menlo]siblings    : 4[/FONT]
[FONT=Menlo]core id        : 1[/FONT]
[FONT=Menlo]cpu cores    : 2[/FONT]
[FONT=Menlo]apicid        : 2[/FONT]
[FONT=Menlo]initial apicid    : 2[/FONT]
[FONT=Menlo]fpu        : yes[/FONT]
[FONT=Menlo]fpu_exception    : yes[/FONT]
[FONT=Menlo]cpuid level    : 13[/FONT]
[FONT=Menlo]wp        : yes[/FONT]
[FONT=Menlo]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 xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt[/FONT]
[FONT=Menlo]bogomips    : 4988.27[/FONT]
[FONT=Menlo]clflush size    : 64[/FONT]
[FONT=Menlo]cache_alignment    : 64[/FONT]
[FONT=Menlo]address sizes    : 36 bits physical, 48 bits virtual[/FONT]
[FONT=Menlo]power management:[/FONT]
[FONT=Menlo]
[/FONT]
[FONT=Menlo]processor    : 2[/FONT]
[FONT=Menlo]vendor_id    : GenuineIntel[/FONT]
[FONT=Menlo]cpu family    : 6[/FONT]
[FONT=Menlo]model        : 58[/FONT]
[FONT=Menlo]model name    : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz[/FONT]
[FONT=Menlo]stepping    : 9[/FONT]
[FONT=Menlo]microcode    : 21[/FONT]
[FONT=Menlo]cpu MHz        : 2494.139[/FONT]
[FONT=Menlo]cache size    : 3072 KB[/FONT]
[FONT=Menlo]physical id    : 0[/FONT]
[FONT=Menlo]siblings    : 4[/FONT]
[FONT=Menlo]core id        : 0[/FONT]
[FONT=Menlo]cpu cores    : 2[/FONT]
[FONT=Menlo]apicid        : 1[/FONT]
[FONT=Menlo]initial apicid    : 1[/FONT]
[FONT=Menlo]fpu        : yes[/FONT]
[FONT=Menlo]fpu_exception    : yes[/FONT]
[FONT=Menlo]cpuid level    : 13[/FONT]
[FONT=Menlo]wp        : yes[/FONT]
[FONT=Menlo]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 xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt[/FONT]
[FONT=Menlo]bogomips    : 4988.27[/FONT]
[FONT=Menlo]clflush size    : 64[/FONT]
[FONT=Menlo]cache_alignment    : 64[/FONT]
[FONT=Menlo]address sizes    : 36 bits physical, 48 bits virtual[/FONT]
[FONT=Menlo]power management:[/FONT]
[FONT=Menlo]
[/FONT]
[FONT=Menlo]processor    : 3[/FONT]
[FONT=Menlo]vendor_id    : GenuineIntel[/FONT]
[FONT=Menlo]cpu family    : 6[/FONT]
[FONT=Menlo]model        : 58[/FONT]
[FONT=Menlo]model name    : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz[/FONT]
[FONT=Menlo]stepping    : 9[/FONT]
[FONT=Menlo]microcode    : 21[/FONT]
[FONT=Menlo]cpu MHz        : 2494.139[/FONT]
[FONT=Menlo]cache size    : 3072 KB[/FONT]
[FONT=Menlo]physical id    : 0[/FONT]
[FONT=Menlo]siblings    : 4[/FONT]
[FONT=Menlo]core id        : 1[/FONT]
[FONT=Menlo]cpu cores    : 2[/FONT]
[FONT=Menlo]apicid        : 3[/FONT]
[FONT=Menlo]initial apicid    : 3[/FONT]
[FONT=Menlo]fpu        : yes[/FONT]
[FONT=Menlo]fpu_exception    : yes[/FONT]
[FONT=Menlo]cpuid level    : 13[/FONT]
[FONT=Menlo]wp        : yes[/FONT]
[FONT=Menlo]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 xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt[/FONT]
[FONT=Menlo]bogomips    : 4988.27[/FONT]
[FONT=Menlo]clflush size    : 64[/FONT]
[FONT=Menlo]cache_alignment    : 64[/FONT]
[FONT=Menlo]address sizes    : 36 bits physical, 48 bits virtual[/FONT]
[FONT=Menlo]power management:[/FONT]
 

skeates

New Member
Feb 12, 2015
24
0
1
I tried these versions

2.6.32-39-pve
2.6.32-37-pve
2.6.32-34-pve
2.6.32-32-pve
2.6.32-26-pve

all with the same result. So my guess is something else on the system has gone wrong during the update.
 

udo

Famous Member
Apr 22, 2009
5,923
180
83
Ahrensburg; Germany
Tried that it seems to error so not sure if that means something is not installed correctly or something has become corrupt

Code:
[FONT=Menlo]root@proxmox:~# modprobe kvm[/FONT][FONT=Menlo]root@proxmox:~# modprobe kvm_intel[/FONT]
[FONT=Menlo]ERROR: could not insert 'kvm_intel': Unknown symbol in module, or unknown parameter (see dmesg)[/FONT]
[FONT=Menlo]root@proxmox:~#[/FONT]
Hi,
strange!
Do you have the same checksum?
Code:
md5sum /lib/modules/2.6.32-39-pve/kernel/arch/x86/kvm/kvm-intel.ko
55e9820ca5873596885337aaff5a0eeb  /lib/modules/2.6.32-39-pve/kernel/arch/x86/kvm/kvm-intel.ko
And what is the output (last lines) of dmesg after modprobe?

Udo
 

skeates

New Member
Feb 12, 2015
24
0
1
md5 below

Code:
[FONT=Menlo]root@proxmox:~# md5sum /lib/modules/2.6.32-39-pve/kernel/arch/x86/kvm/kvm-intel.ko [/FONT][FONT=Menlo]55e9820ca5873596885337aaff5a0eeb  /lib/modules/2.6.32-39-pve/kernel/arch/x86/kvm/kvm-intel.ko[/FONT]
[FONT=Menlo]root@proxmox:~#[/FONT]

dmesg below

Code:
[FONT=Menlo]kvm_intel: Unknown parameter `nested'[/FONT][FONT=Menlo]kvm_intel: Unknown parameter `nested'[/FONT]
[FONT=Menlo]kvm_intel: Unknown parameter `nested'[/FONT]
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!