Could not access KVM kernel module: No such file or directory

Don Daniello

Member
Jan 28, 2012
46
3
8
Hello,
I have just installed Promox 2 on a new dedicated server on top of a clean Debian Squeeze.

The proper kernel is running (Linux hn2.dondaniello.com 2.6.32-6-pve #1 SMP Mon Dec 19 10:15:23 CET 2011 x86_64 GNU/Linux), all packages are installed.

The problem is that VMs don't work, while VCs do.

root@hn2:~# qm start 201Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
No accelerator found!
start failed: command '/usr/bin/kvm -id 201 -chardev 'socket,id=monitor,path=/var/run/qemu-server/201.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/201.vnc,x509,password -pidfile /var/run/qemu-server/201.pid -daemonize -usbdevice tablet -name 178.33.53.12 -smp 'sockets=4,cores=1' -nodefaults -boot 'menu=on' -vga std -tdf -localtime -rtc-td-hack -k pl -drive 'file=/var/lib/vz/template/iso/WindowsServer2008R2_SP1_EN_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2,bootindex=200' -drive 'file=/var/lib/vz/images/201/vm-201-disk-1.qcow2,if=none,id=drive-ide0,aio=native' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=device-ide0,bootindex=100' -m 4096 -netdev 'type=tap,id=net0,ifname=tap201i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=02:00:00:5B:F8:04,netdev=net0,bus=pci.0,addr=0x12,bootindex=300' -cpuunits 1000' failed: exit code 1
This is the output from command line, ofc in the GUI it's the same.

Why does it complain about missing modules when I installed every package from the instructions?
pve-manager: 2.0-18 (pve-manager/2.0/16283a5a)running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.8-3
pve-cluster: 1.0-17
qemu-server: 2.0-13
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: 1.0-5
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1
 

blanchae

New Member
Nov 7, 2012
9
0
1
I had a similar problem and it was because the Intel virtualization technology was not enabled in the server's BIOS. I found this because of these error messages:

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 100 -chardev ',......
 

rmoglia

Member
Jul 28, 2009
83
0
6
Re: Could not access KVM kernel module: No such file or directory (same here)

Code:
root@xray:~# qm start 101
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
start  failed: command '/usr/bin/kvm -id 101 -chardev  'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon  'chardev=qmp,mode=control' -vnc  unix:/var/run/qemu-server/101.vnc,x509,password -pidfile  /var/run/qemu-server/101.pid -daemonize -smbios  'type=1,uuid=e7c0a8aa-46b3-4cd7-8e03-6675c332c691' -name teste -smp  'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu  kvm64,+lahf_lm,+x2apic,+sep -k en-us -m 512 -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:974c66ee34e8' -drive  'file=/var/lib/vz/template/iso/discos-2.0.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' -device  'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive  'file=/var/lib/vz/images/101/vm-101-disk-1.raw,if=none,id=drive-sata0,format=raw,aio=native,cache=none,detect-zeroes=on'  -device  'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev   'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown'  -device  'e1000,mac=D6:CF:BB:D7:83:EE,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300''  failed: exit code 1
root@xray:~# modprobe kvm-intel
ERROR: could not insert 'kvm_intel': Operation not supported
root@xray:~# pveversion -v
proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-34-pve: 2.6.32-139
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
CPU 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 pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm
 

darkpixel

New Member
Oct 26, 2010
23
0
1
I just ran into this on one of my boxes. It had been in production for years, and suddenly stopped working after upgrading to the latest proxmox.

Turns out the CPU battery died and apparently the BIOS reset at some point during rebooting and disabled the Intel VT extensions.
 
Jun 14, 2017
9
0
1
36
I just ran into this on one of my boxes. It had been in production for years, and suddenly stopped working after upgrading to the latest proxmox.

Turns out the CPU battery died and apparently the BIOS reset at some point during rebooting and disabled the Intel VT extensions.
I am having a similar error, how did you fix the vt extensions or otherwise enable the intel kernel
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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!