command 'clusvcadm -e pvevm:100 -m NODE1' failed: exit code 255

J

jerim

Guest
VMs were running on friday. I come in today to find all VMs not running. When I try to start a vm I get:

/var/log/user.log

Aug 13 18:05:42 NODE1 task UPID:NODE1:00002291:0002D198:50298846:qmstart:104:root@pam:: start VM 100: UPID:NODE1:00002291:0002D198:50298846:qmstart:100:root@pam:​
Aug 13 18:05:42 NODE1 pvevm: <root@pam> starting task UPID:NODE1:00002291:0002D198:50298846:qmstart:100:root@pam:​
Aug 13 18:05:42 NODE1 task UPID:NODE1:00002291:0002D198:50298846:qmstart:100:root@pam:: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/104.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name KNT30564 -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga cirrus -k en-us -drive '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=/mnt/pve/Storage/images/100/vm-100-disk-1.raw,if=none,id=drive-virtio0,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -m 1024 -netdev 'type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=F6:2A:69:7C:B4:51,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1​
Aug 13 18:05:42 NODE1 pvevm: <root@pam> end task UPID:NODE1:00002291:0002D198:50298846:qmstart:100:root@pam: start failed: command '/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 -usbdevice tablet -name KNT30564 -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga cirrus -k en-us -drive '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=/mnt/pve/Storage/images/100/vm-100-disk-1.raw,if=none,id=drive-virtio0,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -m 1024 -netdev 'type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=F6:2A:69:7C:B4:51,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

/var/log/cluster/rgmanager.log

Aug 13 18:15:21 rgmanager Starting stopped service pvevm:100
Aug 13 18:15:22 rgmanager start on pvevm "100" returned 1 (generic error)
Aug 13 18:15:22 rgmanager #68: Failed to start pvevm:100; return value: 1
Aug 13 18:15:22 rgmanager Stopping service pvevm:100
Aug 13 18:15:22 rgmanager [pvevm] VM 100 is already stopped
Aug 13 18:15:22 rgmanager Service pvevm:100 is recovering
Aug 13 18:15:22 rgmanager #71: Relocating failed service pvevm:100
Aug 13 18:15:27 rgmanager Service pvevm:100 is stopped



It seems to indicate that it can't find the image file, but I have verified that my storage is mounted and it can access the correct image file.
 
Last edited by a moderator:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!