PVE 2.3 Backup in Snapshot Mode starts an stopped VM

[vcp_ai]

It seems that performing a backup in snapshot mode against an stopped machine, starts the machine, performs the backup and then stops the machine.

INFO: Starting Backup of VM 8098 (qemu)
INFO: status = stopped                              [B]<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<[/B]
INFO: backup mode: stop                              <<<<  STOP MODE
INFO: bandwidth limit: 20000 KB/s
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/Filer.21.backups2/dump/vzdump-qemu-8098-2013_04_24-10_32_58.vma.lzo'
INFO: starting kvm to execute backup task        [B]<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<[/B] MACHINE EFECTIVELLY GETS STARTED 
INFO: started backup task 'eb10373d-ff61-4d53-bbd2-a06321a8c65c'
INFO: status: 0% (62914560/6442450944), sparse 0% (294912), duration 3, 20/20 MB/s
INFO: status: 1% (125829120/6442450944), sparse 0% (364544), duration 6, 20/20 MB/s
INFO: status: 2% (188743680/6442450944), sparse 0% (577536), duration 9, 20/20 MB/s
.... ..... ..... .... 
INFO: status: 99% (6387138560/6442450944), sparse 17% (1096601600), duration 388, 20/1 MB/s
INFO: status: 100% (6442450944/6442450944), sparse 17% (1151909888), duration 391, 18/0 MB/s
INFO: transferred 6442 MB in 391 seconds (16 MB/s)
INFO: stopping kvm after backup task                   [B]<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<[/B]
INFO: archive file size: 3.04GB
INFO: delete old backup '/mnt/pve/Filer.21.backups2/dump/vzdump-qemu-8098-2013_04_17-06_26_11.vma.lzo'
INFO: Finished Backup of VM 8098 (00:06:46)

Previous versions (I think) detected if the machine was started, and if not, performed backup in stop mode. At the begging of log it says it is going to use stop mode...
I think it is the correct mode, and there is no need to start an stopped machine. And starting an stopped machine, in the middle of the night (backup time) can result in problems ... ..... .....

root@servidor170:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
root@servidor170:~#

 

[dietmar]

What is the problem (the VM is not really started, we only start kvm)?

 

[vcp_ai]

What is the problem (the VM is not really started, we only start kvm)?

I do not know what means 'we only start kvm'.
Machine appears to GUI as started (in VM list) and having a look at machine's CPU ussage, it seems as started during backup job.

 

[dietmar]

I do not know what means 'we only start kvm'.

What problem do you have exactly?

 

[vcp_ai]

What problem do you have exactly?

I've repeated backup job, with following results:
1.- Machine appears at PVE as running. CPU usage of the VM shows 'activity'. 'Start' (machine) is replaced with 'Resume'
2.- So I can try to open a console, and I obtain a black VNC console. Trying to RDP to the machine does not connect (i.e. machine seems NOT started)
3.- qm list shows the machine as running.
4.- When backup job finishes machine appears as stopped.

So machines do not start, and seems only a 'cosmetic' problem that show machine as started when they are beeing backed up.

Regards

 

[snowman66]

What happens if you choose RAW as disk format and not qcow2?

 

[tom]

I've repeated backup job, with following results:
1.- Machine appears at PVE as running. CPU usage of the VM shows 'activity'. 'Start' (machine) is replaced with 'Resume'
2.- So I can try to open a console, and I obtain a black VNC console. Trying to RDP to the machine does not connect (i.e. machine seems NOT started)
3.- qm list shows the machine as running.
4.- When backup job finishes machine appears as stopped.

So machines do not start, and seems only a 'cosmetic' problem that show machine as started when they are beeing backed up.

Regards

ad1: yes, expected.
ad2: the VM is started (KVM starts), but the OS does not boot
ad3: yes, as KVM starts, VM shows running - a bit misleading and should be improved (e.g. "started for backup")
ad4: expected if the VM was stopped before its off again after finished backup.

- - - Updated - - -

What happens if you choose RAW as disk format and not qcow2?

the new KVM backup works for all storages, so no difference here.

 

[vcp_ai]

Thanks for clarifying.

BTW machines are raw..

 

[giner]

https://bugzilla.proxmox.com/show_bug.cgi?id=359