[PVE-User] Windows 2012r2 snapshot with RAM => freeze ?

[Gilou]

Le 01/10/2015 10:57, Emmanuel Kasper a écrit :
> 
> On 10/01/2015 10:51 AM, Gilou wrote:
>> Le 01/10/2015 10:44, Alexandre DERUMIER a écrit :
>>> hi,
>>>
>>> I think this bug has been fixed for proxmox 4.0
>>>
>>> https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commit;h=68b7e74b8d9817bc10558faf009956053ee1ea8b
>>> https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commit;h=3a0076907edf0c90869eff3b3bac45346c4ad49c
>>>
>>> I don't known if it's planned to backport them to 3.4.
>>> (maybe as to pve-devel mailing list)
>>
>> OK, not sure if it fixes it, I'll try it on Proxmox 4 later on and
>> report back then...
>>
> 
> Unfortunately the problem stills appears randomly in some corner cases
> and we're still working in sorting this out.
> 
> @gilles: can you confirm the problem on your side only happens with
> Windows VMs ?

I haven't noticed any Linux machines freezing on a live snapshot
rollback, no.


> What is the output of the VNC Console in this case ?

The console has the last image from the snapshot, but it's frozen. The
VM responds to ICMP, and I can do a TCP handshake, but nothing more...
So it's not fully brain dead...

> Can you also post  here the configuration of your VM ? (qm config <myVMID>)

# qm config 305
bootdisk: virtio0
cores: 2
cpu: host
ide2: images-pve3:iso/WIN2012R2_FR.ISO,media=cdrom
memory: 2048
name: win2012r2-gilles
net0: virtio=8E:9E:15:11:86:03,bridge=vmbr0
numa: 0
ostype: win8
parent: test_live_snapshot
smbios1: uuid=986667c3-3b4a-4f0b-ac3f-177d4070bd3e
sockets: 1
virtio1: local:305/vm-305-disk-1.qcow2,format=qcow2,size=50G

> 
> If you manage to reproduce the bug with Proxmox 4.0 ( and only in that
> case), please post your pve4.0 qm config in
> https://bugzilla.proxmox.com/show_bug.cgi?id=694.
> We use this bugzilla entry to track the issue for Proxmox 4.0

Will do.

Thanks,

Gilles