Problem with Snapshot Rollback (PVE 3.4)

[fireon]

Hello,

we have done some snapshots on a Windowsserver, with RAM. Nothing special. We build 3 Snapshots. After we would like to Rollback to Snapshot 2, then we get the following errors:

VM 122 qmp command 'cont' failed - got timeout
TASK ERROR: VM 122 qmp command 'qom-set' failed - unable to connect to VM 122 qmp socket - timeout after 31 retries

Second trail:
we tries to shutdown the vm before rollback:
VM quit/powerdown failed - terminating now with SIGTERM
VM still running - terminating now with SIGKILL
VM 122 qmp command 'cont' failed - got timeout
TASK ERROR: VM 122 qmp command 'qom-set' failed - unable to connect to VM 122 qmp socket - timeout after 31 retries

Then we try the rollback another 3 times, and then it has worked out. But with an Error:
VM 122 qmp command 'cont' failed - got timeout
TASK ERROR: VM 122 qmp command 'qom-set' failed - unable to connect to VM 122 qmp socket - timeout after 31 retries

What is here the problem, is this only an timeout from webinterface, the the rollback has worked at first try?

Thanks and best Reards

proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-34-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-34-pve: 2.6.32-140
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

not correctly installed is only because we use an older kernel. (issue in pvecluster)

 

[spirit]

Hi,
can you post your vmid.conf ?

They are a known bug with windows and qemu 2.2.0 snapshot rollback,
but It's fixed in qemu 2.2.1. (the version you have currently)

 

[fireon]

Here it is:

#Testserver fuer SWTEST von Michi
boot: cdn
bootdisk: virtio0
cores: 3
cpuunits: 40000
hotplug: disk,network
ide0: none,media=cdrom
ide2: none,media=cdrom
memory: 10000
name: vsrv-stepstest.winnet.local
net0: virtio=AE:B2:D4:4D:DC:30,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
parent: SWTEST2014_5_mit_fehler2
scsihw: virtio-scsi-pci
smbios1: uuid=369f9ca4-d290-4c9c-b35a-7823b0d08f2e
sockets: 2
virtio0: local:122/vm-122-disk-1.qcow2,format=qcow2,size=83G

[SWTEST2014_5_mit_fehler]
boot: cdn
bootdisk: virtio0
cores: 3
cpuunits: 40000
hotplug: disk,network
ide0: none,media=cdrom
ide2: none,media=cdrom
machine: pc-i440fx-2.2
memory: 10000
name: vsrv-stepstest.winnet.local
net0: virtio=AE:B2:D4:4D:DC:30,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
scsihw: virtio-scsi-pci
smbios1: uuid=369f9ca4-d290-4c9c-b35a-7823b0d08f2e
snaptime: 1434462260
sockets: 2
virtio0: local:122/vm-122-disk-1.qcow2,format=qcow2,size=83G
vmstate: local:122/vm-122-state-SWTEST2014_5_mit_fehler.raw

[SWTEST2014_5_mit_fehler2]
boot: cdn
bootdisk: virtio0
cores: 3
cpuunits: 40000
hotplug: disk,network
ide0: none,media=cdrom
ide2: none,media=cdrom
machine: pc-i440fx-2.2
memory: 10000
name: vsrv-stepstest.winnet.local
net0: virtio=AE:B2:D4:4D:DC:30,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
parent: SWTEST2014_5_mit_fehler
scsihw: virtio-scsi-pci
smbios1: uuid=369f9ca4-d290-4c9c-b35a-7823b0d08f2e
snaptime: 1434462826
sockets: 2
virtio0: local:122/vm-122-disk-1.qcow2,format=qcow2,size=83G
vmstate: local:122/vm-122-state-SWTEST2014_5_mit_fehler2.raw

[SWTEST2014_5_ohne_fehler]
boot: cdn
bootdisk: virtio0
cores: 3
cpuunits: 40000
hotplug: disk,network
ide0: none,media=cdrom
ide2: none,media=cdrom
machine: pc-i440fx-2.2
memory: 10000
name: vsrv-stepstest.winnet.local
net0: virtio=AE:B2:D4:4D:DC:30,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
parent: SWTEST2014_5_mit_fehler2
scsihw: virtio-scsi-pci
smbios1: uuid=369f9ca4-d290-4c9c-b35a-7823b0d08f2e
snaptime: 1434465784
sockets: 2
virtio0: local:122/vm-122-disk-1.qcow2,format=qcow2,size=83G
vmstate: local:122/vm-122-state-SWTEST2014_5_ohne_fehler.raw

 

[spirit]

does it work in you remove
"machine: pc-i440fx-2.2"

from snapshots configuration

?

 

[fireon]

Test this next wheek... sorry had scant time...

 

[fireon]

Ok, i copied the hole VM with Snapshot's on an Testmachine, and without remove the machineline the rollback goes fine (don't know). I must also say we does not had this problem before. What i've seen: This "machine line" is only in Snapshots. I had a look at the other vm's. In no config there is this "machine line" only in the snapshot section. So what had this to do?

Thanks