snapshot problem since 3.4

silverado · May 12, 2015

spirit said:
can you post vmid.conf of restored vm and new vm ?

Thanks for your reply.

This is the conf of the vm with working snapshots (created on unencryptet Proxmox, backupped and restored on encrypted Proxmox):
________________________________________________________________
bootdisk: virtio0
cores: 1
ide2: local:iso/ubuntu-14.04.1-server-i386.iso,media=cdrom
memory: 512
name: ubuntu-pve
net0: virtio=82:FC:F3:BB:8E:61,bridge=vmbr0
numa: 0
ostype: l26
parent: test2
smbios1: uuid=55e1e400-e01e-4f38-87f7-2271ff9b928b
sockets: 1
virtio0: local:7002/vm-7002-disk-1.qcow2,format=qcow2,cache=writeback,size=32G

[test]
bootdisk: virtio0
cores: 1
ide2: local:iso/ubuntu-14.04.1-server-i386.iso,media=cdrom
machine: pc-i440fx-2.2
memory: 512
name: ubuntu-pve
net0: virtio=82:FC:F3:BB:8E:61,bridge=vmbr0
numa: 0
ostype: l26
smbios1: uuid=55e1e400-e01e-4f38-87f7-2271ff9b928b
snaptime: 1429993401
sockets: 1
virtio0: local:7002/vm-7002-disk-1.qcow2,format=qcow2,cache=writeback,size=32G
vmstate: local:7002/vm-7002-state-test.raw

[test2]
bootdisk: virtio0
cores: 1
ide2: local:iso/ubuntu-14.04.1-server-i386.iso,media=cdrom
machine: pc-i440fx-2.2
memory: 512
name: ubuntu-pve
net0: virtio=82:FC:F3:BB:8E:61,bridge=vmbr0
numa: 0
ostype: l26
parent: test
smbios1: uuid=55e1e400-e01e-4f38-87f7-2271ff9b928b
snaptime: 1431418976
sockets: 1
virtio0: local:7002/vm-7002-disk-1.qcow2,format=qcow2,cache=writeback,size=32G
vmstate: local:7002/vm-7002-state-test2.raw
________________________________________________________________

This is the conf of the vm with failing snapshots (created on encrypted Proxmox)
________________________________________________________________

bootdisk: virtio0
cores: 2
ide2: local:iso/ubuntu-14.04.1-server-i386.iso,media=cdrom
memory: 1024
name: test2
net0: virtio=C6:01:12:06:A3:95,bridge=vmbr0
numa: 0
ostype: l26
smbios1: uuid=b068216e-03e8-4bd7-ac25-5abd1875d9a8
sockets: 1
virtio0: local:7005/vm-7005-disk-1.qcow2,format=qcow2,cache=writeback,size=32G

________________________________________________________________

Looking at these files I tried something new:

As the vm with working snapshots has only 1 core and 512 MB RAM I altered the setting to 2 cores and 1024 MB (so that they match the settings of the failing vm) and suddenly also on this vm snapshots failed.
I played around with the settings and found out that snapshots always fail when the vm has more than 512 MB and/or more than 1 core. When I go back to the original settings snapshots work again.

Then I altered the setting on the other vm (created on the encrypted Proxmox) to 512 MB and 1 core and voilà: Now the snapshots work.

In other words: The failure of snapshots on an encrypted Proxmox is somehow related to the number of cores and the size of memory.

spirit · May 12, 2015

Does it fail only when you snapshot with vmstate (memory ?)

Do you have a crash of the vm ? (can you send the task log ?)

silverado · May 12, 2015

Sorry, I'm in a hurry, so I will have to continue with the troubleshooting later.

Just wanted to report that I was able to take Snaphots of an imported vm with Windows Server 2008 using two cores and 3 Gigs of RAM!

But snapshots of a basically identical vm created on the encrypted Proxmox failed. I'm confused...

I think I will have to do some more systematic investigation on this whole issue.

spirit · May 12, 2015

silverado said:
Sorry, I'm in a hurry, so I will have to continue with the troubleshooting later.

Just wanted to report that I was able to take Snaphots of an imported vm with Windows Server 2008 using two cores and 3 Gigs of RAM!

But snapshots of a basically identical vm created on the encrypted Proxmox failed. I'm confused...

I think I will have to do some more systematic investigation on this whole issue.

Just to be sure, are you running qemu 2.2.1 ?

# kvm --version

carles89 · May 27, 2015

Hi,

I have the same problem, but with Windows Server 2012 R2 guest (1CPU and 2GB RAM).

The server is not encrypted, it's a standard Proxmox installation from a dedicated OVH server (with pve-enterprise enabled).

The thing is that the first time I try to do a snapshot of any vm with Win2012 (with ram, without ram works ok), it freezes the vm, and takes abot 20min until the task fails with this message:

Formatting '/var/lib/vz/images/103/vm-103-state-test.raw', fmt=raw size=4819255296 snapshot create failed: starting cleanupTASK ERROR: query-savevm returned status 'failed'

If I try again, the snapshot works flawessly. Now, if I do another snapshot (child of the first one), the same error, it hangs and I have to do it again (and works ok).

On the same Proxmox node, a snapshot of W7 machine works ok at the first try.

The qemu version is 2.2.1

Any thoughts on that? Thanks in advance!

spirit · May 28, 2015

carles89 said:
Hi,

I have the same problem, but with Windows Server 2012 R2 guest (1CPU and 2GB RAM).

The server is not encrypted, it's a standard Proxmox installation from a dedicated OVH server (with pve-enterprise enabled).

The thing is that the first time I try to do a snapshot of any vm with Win2012 (with ram, without ram works ok), it freezes the vm, and takes abot 20min until the task fails with this message:

If I try again, the snapshot works flawessly. Now, if I do another snapshot (child of the first one), the same error, it hangs and I have to do it again (and works ok).

On the same Proxmox node, a snapshot of W7 machine works ok at the first try.

The qemu version is 2.2.1

Any thoughts on that? Thanks in advance!

Hi, they are a known bug with qemu 2.2.0 and windows rtc clock with memory snapshot (and also live migration).
Are you sure that the vm s running qemu 2.2.1 ? (do you have stop/start the vm after qemu upgrade to 2.2.1 ?)

to be sure, can you do a "info version" in vm monitor tab ?

carles89 · May 28, 2015

Hi spirit,

Here is the output of the command:

Code:

Type 'help' for help.
# info version
2.2.1

And here is also the package version information:

Code:

proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-156
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Just to be sure, I reinstalled Proxmox on the server (not yet in production) from the OVH's template, and I've got the same behaviour.

Thanks!

immo · Jul 9, 2015

same here.. proxmox 3.4-6/102d4547 root@prox05:~# cat /etc/pve/nodes/prox05/qemu-server/143.conf balloon: 1536 boot: dc bootdisk: virtio0 cores: 2 hotplug: disk,network ide0: none,media=cdrom memory: 3072 name: GRFV8021--10.0.1.209 net0: virtio=4E:1E:27:CA:C4:27,bridge=vmbr2 numa: 0 onboot: 1 ostype: win7 smbios1: uuid=7f9dfcff-acee-4a66-a49a-3c943e068692 sockets: 1 virtio0: Storage:103/base-103-disk-1.qcow2/143/vm-143-disk-1.qcow2,format=qcow2,cache=unsafe,size=30G

carles89 · Jul 9, 2015

immo said:
same here.. proxmox 3.4-6/102d4547 root@prox05:~# cat /etc/pve/nodes/prox05/qemu-server/143.conf balloon: 1536 boot: dc bootdisk: virtio0 cores: 2 hotplug: disk,network ide0: none,media=cdrom memory: 3072 name: GRFV8021--10.0.1.209 net0: virtio=4E:1E:27:CA:C4:27,bridge=vmbr2 numa: 0 onboot: 1 ostype: win7 smbios1: uuid=7f9dfcff-acee-4a66-a49a-3c943e068692 sockets: 1 virtio0: Storage:103/base-103-disk-1.qcow2/143/vm-143-disk-1.qcow2,format=qcow2,cache=unsafe,size=30G

Hi Immo,

Do you have qemu-guest installed inside your VM?

Regards

spirit · Jul 10, 2015

immo said:
same here.. proxmox 3.4-6/102d4547 root@prox05:~# cat /etc/pve/nodes/prox05/qemu-server/143.conf balloon: 1536 boot: dc bootdisk: virtio0 cores: 2 hotplug: disk,network ide0: none,media=cdrom memory: 3072 name: GRFV8021--10.0.1.209 net0: virtio=4E:1E:27:CA:C4:27,bridge=vmbr2 numa: 0 onboot: 1 ostype: win7 smbios1: uuid=7f9dfcff-acee-4a66-a49a-3c943e068692 sockets: 1 virtio0: Storage:103/base-103-disk-1.qcow2/143/vm-143-disk-1.qcow2,format=qcow2,cache=unsafe,size=30G

can you send the snasphot task log ?

(BTW, you shouldn't use cache=unsafe for production, I don't think that the disk snapshot will be ok with this)

immo · Jul 10, 2015

Ok I'm not reall sure if that one is the log you requested... root@prox05:~# cat /var/log/pve/tasks/C/UPID

rox05:00007F9E:00710065:559FACDC:qmsnapshot:143:root@pam: Formatting '/mnt/pve/Storage/images/143/vm-143-state-powerfail.raw', fmt=raw size=6966738944 snapshot create failed: starting cleanup TASK ERROR: query-savevm returned status 'failed' root@prox05:~#

silverado · Sep 13, 2015

After quite a long time I'm back with the same problem. This time I have installed a fresh non encrypted Proxmox using the standard Proxmox ISO installation media.

When I try to snapshot a Debian 8 32 bit virtual machine including RAM the snapshot fails.
Formatting '/var/lib/vz/images/4011/vm-4011-state-test.raw', fmt=raw size=2671771648
snapshot create failed: starting cleanup
TASK ERROR: query-savevm returned status 'failed'

Without including RAM the snapshot works flawlessly.

Snapshots of a Windows 2012R2 VM and a Windows 7 32 bit VM work with RAM included.

So it seems that the problem first reported in February 2015 still persists.

Search

Search

snapshot problem since 3.4

silverado

Renowned Member

spirit

Distinguished Member

silverado

Renowned Member

spirit

Distinguished Member

carles89

Renowned Member

spirit

Distinguished Member

carles89

Renowned Member

immo

Renowned Member

carles89

Renowned Member

spirit

Distinguished Member

immo

Renowned Member

silverado

Renowned Member