[SOLVED] VM does not start anymore, backup also not posible

fireon

Distinguished Member
Oct 25, 2010
4,597
544
183
Austria/Graz
deepdoc.at
Hello,

on VM on one of us machines does not start anymore. Backup also not possible.

System up to date:
pveversion Enterpriserepo
pve-manager/4.1-15/8cd55b52 (running kernel: 4.2.8-1-pve)
USE PVE with ZFS.

The was running last week. Yesterday the backup was fine. This time i can't start the backup, and i can't start the VM.

The Backuperror ist "Input/Output Error". No problem with Backupstorage, it is the same with USB and localbackup. And only with this one VM.

The error when i start the VM:
Code:
Mar 06 12:28:46 pve-server pvedaemon[9490]: start VM 103: UPID:pve-server:00002512:00500AE5:56DC146E:qmstart:103:user@tux.local:
Mar 06 12:28:46 pve-server pvedaemon[27652]: <user@tux.local> starting task UPID:pve-server:00002512:00500AE5:56DC146E:qmstart:103:user@tux.local:
Mar 06 12:28:46 pve-server pvedaemon[9490]: start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 103 -p 'KillMode=none' -p 'CPUShares=250000' -p 'CPUQuota=800%' /usr/bin/kvm -id 103 -chardev 'socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/103.pid -daemonize -name gtemplate.tux.local -smp '4,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga qxl -vnc unix:/var/run/qemu-server/103.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 'size=1024,slots=255,maxmem=4194304M' -object 'memory-backend-ram,size=1024M,id=ram-node0' -numa 'node,nodeid=0,cpus=0-7,memdev=ram-node0' -object 'memory-backend-ram,id=mem-dimm0,size=512M' -device 'pc-dimm,id=dimm0,memdev=mem-dimm0,node=0' -object 'memory-backend-ram,id=mem-dimm1,size=512M' -device 'pc-dimm,id=dimm1,memdev=mem-dimm1,node=0' -k de -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' -spice 'tls-port=61008,addr=localhost,tls-ciphers=DES-CBC3-SHA,seamless-migration=on' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:58e5fe8fcaf9' -drive 'file=/dev/zvol/v-machines/vm-103-disk-2,if=none,id=drive-virtio0,format=raw,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=tap103i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=52:54:00:14:EA:2D,netdev=net0,bus=pci.0,addr=0x12,id=net0'' failed: exit code 1

What is here the error. Can't see useful information... Here are the config of the VM:
Code:
qm config 103  
boot: c
bootdisk: virtio0
cores: 8
cpulimit: 8
cpuunits: 250000
description: VM-Template mit Gentoo (only 64bit)
hotplug: disk,network,memory,cpu
memory: 2048
name: gtemplate.tux.local
net0: virtio=52:54:00:14:EA:2D,bridge=vmbr0
numa: 1
ostype: l26
scsihw: virtio-scsi-pci
sockets: 1
vcpus: 4
vga: qxl
virtio0: v-machines:vm-103-disk-2,size=34G
I have an existing backup, but this is the last option for me. It is important to find why it is not starting anymore.

Thanks for help.
 
Hi,

do you tried to reboot the PVE Host?
 
Hello,

this is the command:
Code:
/usr/bin/systemd-run --scope --slice qemu --unit 103 -p KillMode=none -p CPUShares=250000 -p CPUQuota=800% /usr/bin/kvm -id 103 -chardev socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait -mon chardev=qmp,mode=control -pidfile /var/run/qemu-server/103.pid -daemonize -name gtemplate.osit.cc -smp 4,sockets=1,cores=8,maxcpus=8 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga qxl -vnc unix:/var/run/qemu-server/103.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m size=1024,slots=255,maxmem=4194304M -object memory-backend-ram,size=1024M,id=ram-node0 -numa node,nodeid=0,cpus=0-7,memdev=ram-node0 -object memory-backend-ram,id=mem-dimm0,size=512M -device pc-dimm,id=dimm0,memdev=mem-dimm0,node=0 -object memory-backend-ram,id=mem-dimm1,size=512M -device pc-dimm,id=dimm1,memdev=mem-dimm1,node=0 -k de -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 -spice tls-port=61003,addr=localhost,tls-ciphers=DES-CBC3-SHA,seamless-migration=on -device virtio-serial,id=spice,bus=pci.0,addr=0x9 -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:58e5fe8fcaf9 -drive file=/dev/zvol/v-machines/vm-103-disk-2,if=none,id=drive-virtio0,format=raw,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=tap103i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=52:54:00:14:EA:2D,netdev=net0,bus=pci.0,addr=0x12,id=net0
After execute this command the machine is running fine. And the strange thing, after this, i can start the machine normaly and backup is also possible. I do not unterstand this, nothing was changed, really nothing.

And yes I've done a full upgrade at Saturday. There was some packages, not so mutch, but also qemu and PVEthings.