start virtual machine error

J

jdaliz

New Member
Jun 23, 2015
9
0
1
Venezuela
good day! when I start my virtual machine gives me the error "Error: start failed: command" / usr / bin / kvm-id ... "I made a noteworthy Proxmox installation through debian wheezy guiding me by the Wikipedia page My server has 10 gig of ram momeria and one of two 250gb hard drive and a 450GB is an HP-DL140. Any kind of help or guidance where this problem. agradesco it THANKS ...:)
 
Please try to start manually on the command line:

# qm start <vmid>

and then post the full error message.
 
Jun 23 12:15:03 Debian pvedaemon[2841]: start failed: command '/usr/bin/kvm -id 505 -chardev 'socket,id=qmp,path=/var/run/qemu-server/505.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/505.vnc,x509,password -pidfile /var/run/qemu-server/505.pid -daemonize -smbios 'type=1,uuid=e3f9c837-fe24-466b-9179-8a601e4691bb' -name whezzy -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 1024 -k en-us -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:261a3eedab61' -drive 'file=/var/lib/vz/template/iso/Debian_7.7.0_M-A_1.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' -drive 'file=/var/lib/vz/images/505/vm-505-disk-1.raw,if=none,id=drive-virtio0,format=raw,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=user,id=net0,hostname=whezzy' -device 'virtio-net-pci,mac=A2:2B:E0:D4:3C:4C,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
 
Dietmar Hello, excuse delay, reinstall Proxmox again from the cd instead of using debian, like I can not start the machine, I send the command output qm start , pveversion and lscpu Thanks and sorry for all the inconvenience caused

root@jose:/# qm start 100 Running as unit 100.scope. 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/systemd-run --scope --slice qemu --unit 100 -p 'CPUShares=1000' /usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=e064b158-1c18-4805-9a1d-e77fffc3a596' -name windows8.1 -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+x2apic,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 1024 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -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:75d0292ce4f4' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/Windows_8_1.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=F2:55:1C:F6:A9:C4,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1


root@jose:/# pveversion -v
proxmox-ve: 4.0-3 (running kernel: 3.19.8-1-pve)
pve-manager: 4.0-16 (running version: 4.0-16/a7dc5694)
pve-kernel-3.19.8-1-pve: 3.19.8-3
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-13
qemu-server: 4.0-12
pve-firmware: 1.1-5
libpve-common-perl: 4.0-8
libpve-access-control: 4.0-5
libpve-storage-perl: 4.0-11
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.3-5
pve-container: 0.7-2
pve-firewall: 2.0-3
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-1
lxcfs: 0.9-pve1
cgmanager: 0.37-pve1

root@jose:/# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 15
Model name: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz
Stepping: 6
CPU MHz: 1595.877
BogoMIPS: 3191.75
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0,1

 
Last edited:
root@jose:/# pveversion -v
proxmox-ve: 4.0-3 (running kernel: 3.19.8-1-pve)
pve-manager: 4.0-16 (running version: 4.0-16/a7dc5694)
pve-kernel-3.19.8-1-pve: 3.19.8-3
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-13
qemu-server: 4.0-12
pve-firmware: 1.1-5
libpve-common-perl: 4.0-8
libpve-access-control: 4.0-5
libpve-storage-perl: 4.0-11
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.3-5
pve-container: 0.7-2
pve-firewall: 2.0-3
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-1
lxcfs: 0.9-pve1
cgmanager: 0.37-pve1
 
Thanks friend, I needed was right Enable virtualization bios, you can close it. :) , There are some guidance or some documentation which could to learn more about Proxmox I am a rookie and I want to learn , again thanks
 
I appear to have very similar symptoms with an Intel E6750, which supports VT-x. Virtualisation is turned on in the BIOS, but machines still do not start. Do you suggest anything else to try?

root@node02:~# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 15
Model name: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
Stepping: 11
CPU MHz: 2667.000
CPU max MHz: 2667.0000
CPU min MHz: 2000.0000
BogoMIPS: 5320.37
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0,1

root@node02:~# pveversion -v
proxmox-ve: 4.1-32 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-4 (running version: 4.1-4/ccba54b0)
pve-kernel-4.2.6-1-pve: 4.2.6-32
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-44
pve-firmware: 1.1-7
libpve-common-perl: 4.0-43
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-20
pve-container: 1.0-37
pve-firewall: 2.0-15
pve-ha-manager: 1.0-16
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie

root@node02:~# cat /proc/cpuinfo | grep flags | uniq
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 lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow vnmi flexpriority

root@node02:~# qm start 100
Running as unit 100.scope.
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/systemd-run --scope --slice qemu --unit 100 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=5dde9fe9-092e-4153-b255-a5f1c10b641c' -name firewall -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 512 -k en-us -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -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:c6c4417560c1' -drive 'file=/var/lib/vz/template/iso/OPNsense-15.7.18-OpenSSL-cdrom-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/mnt/pve/Disks/images/100/vm-100-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=62:30:33:34:38:62,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -netdev 'type=tap,id=net1,ifname=tap100i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=66:63:35:37:30:61,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301'' failed: exit code 1
 
ITWarrior said:
I appear to have very similar symptoms with an Intel E6750, which supports VT-x. Virtualisation is turned on in the BIOS, but machines still do not start. Do you suggest anything else to try?
Click to expand...

poweroff your server, unplug it. and try again.

and check if there is a bios upgrade available.
 
OK, so I figured it out.

I switched the machine out with another Optiplex 755 (which, somehow, happens to have the A22 BIOS). Dropped the hard drive into this new machine and booted it up. It still wouldn't start a KVM machine, so I don't think it was BIOS version related.

Neither of these machines have VT-d (only VT-x), yet the option to turn on VT-d is available in the BIOS. They also both have the option 'Trusted Execution'. The blurb for this is as follows:

"This field specifies whether a Measured Virtual Machine Monitor (MVMM) can utilise the additional hardware capabilities provided by Intel(R) Trusted Execution Technology. The TPM, Virtualization Technology, and Virtualization Technology for Direct I/O must be enabled to use this feature."

This was enabled on both machines, as were the dependencies that it required. I'm guessing that since TE couldn't use VT-d (even though it was technically turned on) it was blocking everything else from working properly, including VT-x.

TL;DR: Turn off Trusted Execution.
 
You must log in or register to reply here.
Top Bottom