Search results

Thanks, it seems now solved with the problematic VM to local storage: INFO: starting new backup job: vzdump 302 --compress gzip INFO: Starting Backup of VM 302 (qemu) INFO: status = running INFO: update VM 302: -lock backup INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: creating...

$ sudo qm showcmd 302 /usr/bin/kvm -id 302 -chardev socket,id=qmp,path=/var/run/qemu-server/302.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/302.vnc,x509,password -pidfile /var/run/qemu-server/302.pid -daemonize -name monit -smp sockets=1,cores=2 -nodefaults...

Unfortunately, same result.

Which one ? There's a new kernel in test ? It fails with 2.6.32-27-pve too.

Back on kernel proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-26-pve) and it still crashes on the same VM. Backup is on local storage, 2 others KVM with the same configuration are OK, 10 oVZ without any problem: Mar 20 00:09:31 INFO: Starting Backup of VM 302 (qemu) Mar 20 00:09:31 INFO...

Thanks for notice, BTW the result is the same: no backup and crashed VM since update 3.1->3.2. Log from yesterday ;) Mar 17 00:09:14 INFO: Starting Backup of VM 302 (qemu) Mar 17 00:09:14 INFO: status = running Mar 17 00:09:15 INFO: update VM 302: -lock backup Mar 17 00:09:15 INFO: backup mode...

Hello, Same problem here, it's failed since update to 3.2 and reboot to kernel 2.6.32-27-pve. Backup is on local disk. # pveversion -v proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve) pve-manager: 3.2-1 (running version: 3.2-1/1933730b) pve-kernel-2.6.32-27-pve: 2.6.32-121...