[SOLVED] Start failed: command '/usr/bin/kvm...' failed: exit code 1

[jad340]

deleted

 

[udo]

Hello, I run a small cluster with 2 nodes currently present. When I try to run a qemu/KVM VM from one node, pve0, I get this error message:

 kvm: -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none,detect-zeroes=on: file system may not support O_DIRECT kvm: -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none,detect-zeroes=on: could not open disk image /var/lib/vz/images/101/vm-101-disk-1.qcow2: Could not open '/var/lib/vz/images/101/vm-101-disk-1.qcow2': Invalid argument 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=5644e407-47aa-4b9a-b692-1e9978db8633' -name http -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu host,+x2apic -m 1600 -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:d79ba294b077' -drive 'file=/var/lib/vz/template/iso/cd57.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/101/vm-101-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,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=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BE:FC:0A:DC:B5:8D,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

I use (mostly - just qcow2 disk size and max memory changed) the same settings on another VM on my second node, pve1, which works fine. Here are the output of a few commands that might be useful

 root@pve0:~# pveversion -v proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e) pve-kernel-2.6.32-37-pve: 2.6.32-147 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-2 pve-cluster: 3.0-16 qemu-server: 3.3-20 pve-firmware: 1.1-3 libpve-common-perl: 3.0-24 libpve-access-control: 3.0-16 libpve-storage-perl: 3.0-31 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-12 ksm-control-daemon: 1.1-1 glusterfs-client: 3.5.2-1

 root@pve0:~# qm config 101 balloon: 256 bootdisk: virtio0 cores: 1 cpu: host ide2: local:iso/cd57.iso,media=cdrom memory: 1600 name: http net0: virtio=BE:FC:0A:DC:B5:8D,bridge=vmbr0 numa: 0 ostype: other smbios1: uuid=5644e407-47aa-4b9a-b692-1e9978db8633 sockets: 1 virtio0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=20G

All of my packages are up to date on both nodes. I would greatly appreciate any help with this. Thanks!

Hi,
does your host support x2apic?

cat /proc/cpuinfo | grep x2apic

Udo