KVM FAILS to start Error code 1

[Amori]

Hello,

I have a dedicated server with proxmox version 3.2-2. I have a couple of VPS inside, and they are working fine. Today one of my client contacted me about his VM is not working. I was trying to start it but I got this error

pvedaemon[765017]: start failed: command '/usr/bin/kvm -id 109 -chardev 'socket,id=qmp,path=/var/run/qemu-server/109.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/109.vnc,x509,password -pidfile /var/run/qemu-server/109.pid -daemonize -name wbs -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -no-hpet -cpu 'kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep' -k en-us -m 4096 -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' -drive 'file=/var/lib/vz/images/109/vm-109-disk-1.raw,if=none,id=drive-ide0,format=raw,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap109i0,script=/var/lib/qemu-server/pve-bridge' -device 'e1000,mac=E21:CA:84:6D:60,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

My syslog>
root@sd-64607:~# tail -f /var/log/syslog
Jul 1 23:25:36 sd-64607 pvedaemon[764350]: start VM 109: UPID:sd-64607:000BA9BE :06A1CC5C:53B32750:qmstart:109:root@pam:
Jul 1 23:25:36 sd-64607 pvedaemon[763513]: <root@pam> starting task UPID:sd-646 07:000BA9BE:06A1CC5C:53B32750:qmstart:109:root@pam:
Jul 1 23:25:36 sd-64607 kernel: device tap109i0 entered promiscuous mode
Jul 1 23:25:36 sd-64607 kernel: vmbr1: port 3(tap109i0) entering forwarding sta te
Jul 1 23:25:36 sd-64607 kernel: vmbr1: port 3(tap109i0) entering disabled state
Jul 1 23:25:36 sd-64607 kernel: vmbr1: port 3(tap109i0) entering disabled state
Jul 1 23:25:36 sd-64607 pvedaemon[764350]: start failed: command '/usr/bin/kvm -id 109 -chardev 'socket,id=qmp,path=/var/run/qemu-server/109.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/109.vnc,x509,pas sword -pidfile /var/run/qemu-server/109.pid -daemonize -name wbs -smp 'sockets=1 ,cores=2' -nodefaults -boot 'menu=on' -vga std -no-hpet -cpu qemu64 -k en-us -m 4096 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -dev ice 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=ball oon0,bus=pci.0,addr=0x3' -drive 'file=/mnt/pve/GSA2048/template/iso/2008.iso,if= none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,driv e=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/109/vm-109-d isk-1.raw,if=none,id=drive-ide0,format=raw,aio=native,cache=none' -device 'ide-h d,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id= net0,ifname=tap109i0,script=/var/lib/qemu-server/pve-bridge' -device 'e1000,mac= E21:CA:84:6D:60,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'd riftfix=slew,base=localtime' -machine 'accel=tcg' -global 'kvm-pit.lost_tick_pol icy=discard'' failed: exit code 1
Jul 1 23:25:36 sd-64607 pvedaemon[763513]: <root@pam> end task UPID:sd-64607:00 0BA9BE:06A1CC5C:53B32750:qmstart:109:root@pam: start failed: command '/usr/bin/k vm -id 109 -chardev 'socket,id=qmp,path=/var/run/qemu-server/109.qmp,server,nowa it' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/109.vnc,x509, password -pidfile /var/run/qemu-server/109.pid -daemonize -name wbs -smp 'socket s=1,cores=2' -nodefaults -boot 'menu=on' -vga std -no-hpet -cpu qemu64 -k en-us -m 4096 -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=b alloon0,bus=pci.0,addr=0x3' -drive 'file=/mnt/pve/GSA2048/template/iso/2008.iso, if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,d rive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/109/vm-10 9-disk-1.raw,if=none,id=drive-ide0,format=raw,aio=native,cache=none' -device 'id e-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap, id=net0,ifname=tap109i0,script=/var/lib/qemu-server/pve-bridge' -device 'e1000,m ac=E21:CA:84:6D:60,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'accel=tcg' -global 'kvm-pit.lost_tick_ policy=discard'' failed: exit code 1
Jul 1 23:25:42 sd-64607 pvedaemon[763513]: <root@pam> update VM 109: -delete kv m
Jul 1 23:26:17 sd-64607 pvedaemon[764076]: <root@pam> successful auth for user 'root@pam'

Can someone tell me how to solve this?

Thanks

 

[Amori]

pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-28-pve: 2.6.32-124
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

 

[tom]

you run not the latest version (but seems not the cause).

post the VM config:

> qm config 109

can you run other VM´s without issues?

 

[Amori]

you run not the latest version (but seems not the cause).

post the VM config:

> qm config 109

can you run other VM´s without issues?

Thanks problem solved yesterday. I just made a clone, then I was able to start it.

unfortunately I can't test your command TOM because the old VM is removed.

 

[phk]

Hi all.

Gor the same problem with 3.4 only cloning did not work. No vm works.
3.3 ran fine.
now installed 3.4 with raid1
Got the error:
kvm: -drive file=/var/lib/vz/images/102/vm-102-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/102/vm-102-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/102/vm-102-disk-1.qcow2: Could not open '/var/lib/vz/images/102/vm-102-disk-1.qcow2': Invalid argument
TASK ERROR: start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/102.vnc,x509,password -pidfile /var/run/qemu-server/102.pid -daemonize -smbios 'type=1,uuid=d0d433aa-1798-4e59-b336-b68afff1caa7' -name w81org-1 -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'Haswell,hv_spinlocks=0xffff,hv_relaxed,+x2apic' -m 10240 -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:9a5941afd4ec' -drive 'file=/var/lib/vz/template/iso/virtio-win-0.1-100.iso,if=none,id=drive-ide0,media=cdrom,aio=native' -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200' -drive 'file=/var/lib/vz/template/iso/IR5_CCSA_X64FRE_NL-NL_DV9.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201' -drive 'file=/var/lib/vz/images/102/vm-102-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=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=DE:0E:5C:67:C5:B9,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

config of 101.conf:
balloon: 512
bootdisk: ide0
cores: 1
ide0: local:101/vm-101-disk-1.qcow2,size=32G
ide2: local:iso/IR5_CCSA_X64FRE_NL-NL_DV9.iso,media=cdrom
memory: 10240
name: w8
net0: e1000=FE:A9:65:3C:23:5D,bridge=vmbr0
numa: 0
ostype: win8
smbios1: uuid=17dfa0f8-bbb6-4584-a830-5e70efe62166
sockets: 1


Other post mentioned versionproblems for qemu-kvm. it is 2.1
I did an
apt-get upgrade
apt-get dist-upgrade
reboot

same problem.

Any Ideas?

tnx
PH

 

[dietmar]

Any Ideas?

Change cache mode of disk from 'none' to 'writeback'

 

[phk]

Change cache mode of disk from 'none' to 'writeback'

Tnx Dietmar!

That helped! Installation is running as we speak.
How could i have know this for i have nevere encountered this in previous versions of proxmox; 3.1 and 3.3.

I have introduced Proxmox as a vritualisation alternative to HyperV and VMware at a school in the Neterlands.
Lots of studens have done installations AND KVM-virtualisations for training and comparison purposes.
Never heard one of them talking about this issue.

With kind regards!

PH

 

[dietmar]

How could i have know this for i have nevere encountered this in previous versions of proxmox; 3.1 and 3.3.

This is just a temporary problem with zfs 0.6.3. It will be solved with future zfs versions.