kvm doesn't start

A

adam1000

New Member
Dec 2, 2011
6
0
1
Hi there. I've spent the last few days using the latest 2.0 baremetal installation and it's been fantastic, both for running containers and kvms. Today, I installed the pve 2.6.32-6 kernel + related applications on top of debian 6.0.3 (following the instructions here: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze) as I wanted to use a customised partition layout. I can create and run containers but when I attempt to start a vm I get the error below. Two other points:

- if I run 'lsmod | grep kvm' it returns kvm_intel and kvm so it appears the modules are loaded, notwithstanding the error message. VT-x is enabled in the bios and I've never had any trouble creating and running kvm vms before.
- the vm config below is identical to what I was using on the baremetal version where it worked fine

Can anyone help me with this (I've had a look through the forum posts but couldn't find this exact problem - apologies if I've missed anything)?

Code: 
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
No accelerator found!
TASK
ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 
socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait -mon 
chardev=monitor,mode=readline -vnc 
unix:/var/run/qemu-server/100.vnc,x509,password -pidfile 
/var/run/qemu-server/100.pid -daemonize -readconfig 
/usr/share/qemu-server/pve-usb.cfg -device usb-tablet,bus=ehci.0,port=6 
-name kvm0 -smp sockets=1,cores=1 -nodefaults -boot menu=on,order=cdn 
-vga cirrus -tdf -k en-us -drive 
file=/var/lib/vz/template/iso/CentOS-6.0-x86_64-minimal.iso,if=none,id=drive-ide2,media=cdrom,aio=native
 -device ide-drive,bus=ide.1,unit=0,drive=drive-ide2,id=device-ide2 -drive 
file=/dev/vm/vm-100-disk-1,if=none,id=drive-virtio0,aio=native,boot=on 
-device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa -m 768 -netdev 
type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge -device 
virtio-net-pci,romfile=,mac=9A:B0:CD:34:5B:19,netdev=net0,bus=pci.0,addr=0x12'
 failed: exit code 1
 
Thanks for the reply guys. However, as I mentioned, acceleration/VT-x is definitely enabled. I say this for the following reasons:

(i) I've checked in the bios - see screenshot (note, I've done multiple power cycles)
(ii) if I run 'egrep '^flags.*(vmx|svm)' /proc/cpuinfo' it returns a vmx flag
(iii) I've had no problem with kvm in the past
(iv) kvm worked fine with the baremetal install of proxmox 2.0

This problem only started when I performed my own installation of the pve kernel 2.6.32-6 (+pve applications) on top of debian 6 so perhaps there is a connection? I followed the installation instructions very closely and as I said, containers work fine. Still though, it seems like quite a coincidence right?
 

Attachments

  • vt-x.jpg
    vt-x.jpg
    55.8 KB · Views: 40
Ok, stop the press!! It just started working and I *honestly* didn't change anything. I really don't understand why this happens sometimes!
 
dietmar said:
what is the output of

# pveversion -v
Click to expand...

Code: 
pve-manager: 2.0-12 (pve-manager/2.0/784729f4)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-53
pve-kernel-2.6.32-6-pve: 2.6.32-53
lvm2: 2.02.86-1pve2
clvm: 2.02.86-1pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-12
qemu-server: 2.0-10
pve-firmware: 1.0-13
libpve-common-perl: 1.0-8
libpve-access-control: 1.0-2
libpve-storage-perl: 2.0-8
vncterm: 1.0-2
vzctl: 3.0.29-3pve3
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.1-1
 
I'm having the exact same problem, bellow you can see my processor flags and the pveversion -v

flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv

pve-manager: 2.0-14 (pve-manager/2.0/6a150142)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-54
pve-kernel-2.6.32-6-pve: 2.6.32-54
lvm2: 2.02.86-1pve2
clvm: 2.02.86-1pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-12
qemu-server: 2.0-11
pve-firmware: 1.0-13
libpve-common-perl: 1.0-10
libpve-access-control: 1.0-3
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve7
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1

Can anyone help me?
 
Hi, i had the same problem. My problem got fixed, when i tured off KVM. Go to your virtual machine to "options". Then deactivate "KVM hardware-virtualization". Proxmox probably takes then the OpenVZ virtualization methode. But i'm not shure....

1674749035806.png
 
You must log in or register to reply here.
Top Bottom