proxmox-1:~# lsmod | grep kvm
kvm 213288 0
proxmox-1:~# ls /dev/kvm
ls: cannot access /dev/kvm: No such file or directory
proxmox-1:~# qm start 109
open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
proxmox-1:~# qm start 109
VM 109 already running - start failed
proxmox-1:~#
proxmox-1:~# qm create 100 --memory 256 --kvm yes --ide0 4 --vlan0 e1000
Formatting '/var/lib/vz/images/100/vm-100-disk-1.raw', fmt=raw size=4294967296
proxmox-1:~#
proxmox-1:~# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-3-pve
proxmox-ve-2.6.32: 1.6-14
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-7
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4
proxmox-1:~#
Yup... your VM does not export the Intel-VT or AMD-V part of the CPU... I don't think that's possible in any VM system. So it'll never work like that.
---Guy
Ok, thanks for the info. Then I won't spend any more time trying to make it work. At least the OpenVZ works...
-Todd
Ok, thanks for the info. Then I won't spend any more time trying to make it work. At least the OpenVZ works...
-Todd