Take Snapshot is Disabled on qcow2 after 2.3 upgrade to 3.0

[Farsh]

I had a KVM container with a disk format of qcow2 in my 2.3 install. I had already taken a snapshot of this install. I upgraded to 3.0 using the script and after restart I noticed that Take Snapshot was disabled. I verified disk format and it was still in qcow2. Any idea what I need to do to enable Snapshots?

 

[dietmar]

I am sure this still works in 3.0. Please can you post you VM config?

 

[Farsh]

Here is my config:

bootdisk: ide0
cores: 2
ide0: local:200/vm-200-disk-1.qcow2,format=qcow2,size=40G
memory: 5000
name: TMP200
net0: virtio=06:EC:56:B9:40F,bridge=vmbr0
ostype: win8
sockets: 2

 

[dietmar]

Works here. You rebooted the server after the upgrade? If not, please try.

and post your 'pveversion -v'

 

[Farsh]

Yes I have rebooted. Will do it one more time... In the meantime here is the pveversion -v results:



pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-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.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1

 

[Farsh]

After restart it did not work and it was still disabled, however after 10 minutes it all of a sudden became available.

 

[dietmar]

After restart it did not work and it was still disabled, however after 10 minutes it all of a sudden became available.

Maybe something was wrong with the system time?

 

[Farsh]

I know for a fact that the time was correct, we have several servers that need to be upgraded, I can look to see if the issue is detected on any other one. Is there anything you like me to collect or look at if in case we could replicate the problem?

 

[dietmar]

I can look to see if the issue is detected on any other one. Is there anything you like me to collect or look at if in case we could replicate the problem?

Run firebug an see if the API calls return some errors.

 

[CTCcloud]

I found the same thing. We have a four node cluster and 3 out of the 4 machines are upgraded to Proxmox 3.0. I was seeing the same thing, snapshotting was not available on VMs that are in QCOW2 format. I finally realized though that I was looking at the cluster through the one Proxmox 2.3 node that hasn't yet been upgraded...when I opened up the GUI from one of the nodes that is already upgraded to 3.0 the snapshotting is available for those VMs that are in QCOW2 format. Is this possibly what happened here? I just thought I'd mention this in case it helps to possibly understand what may have happened.

Awesome job Proxmox team for an excellent product!

Regards,

ctcknows

 

[Mantas]

I found the same thing. We have a four node cluster and 3 out of the 4 machines are upgraded to Proxmox 3.0. I was seeing the same thing, snapshotting was not available on VMs that are in QCOW2 format. I finally realized though that I was looking at the cluster through the one Proxmox 2.3 node that hasn't yet been upgraded...when I opened up the GUI from one of the nodes that is already upgraded to 3.0 the snapshotting is available for those VMs that are in QCOW2 format. Is this possibly what happened here? I just thought I'd mention this in case it helps to possibly understand what may have happened.

Awesome job Proxmox team for an excellent product!

Regards,

ctcknows

Exactly, that is the case.

Thanks.