Hi,
currently we're evaluating Proxmox (free edition) and have some problems with snapshotting.
We're using qcow2 disk files on an NetApp NFS share and with larger virtual disks the snapshot function provided by the Proxmox GUI results in lost network connectivity and, in some terminal cases, an unusable guest (even console access is SNAFU, only way to recover is a hard reset). When I create a snapshot with the cmd tool qemu-img the guest is running uninterrupted while the tool does its job.
Is this a known issue? And, if not, what is the difference between directly invoking the qemu tool and the GUI function? Aside from the <guest>.conf in /etc/pve/nodes/ for Proxmox' management I don't see a technical reason for the remarkable distinct behaviour of the two snapshot methods.
Thanks, Renke
currently we're evaluating Proxmox (free edition) and have some problems with snapshotting.
We're using qcow2 disk files on an NetApp NFS share and with larger virtual disks the snapshot function provided by the Proxmox GUI results in lost network connectivity and, in some terminal cases, an unusable guest (even console access is SNAFU, only way to recover is a hard reset). When I create a snapshot with the cmd tool qemu-img the guest is running uninterrupted while the tool does its job.
Is this a known issue? And, if not, what is the difference between directly invoking the qemu tool and the GUI function? Aside from the <guest>.conf in /etc/pve/nodes/ for Proxmox' management I don't see a technical reason for the remarkable distinct behaviour of the two snapshot methods.
Thanks, Renke