For KVM, it is technically impossible to write content of RAM anywhere, with any other storage than the QCOW2 format - this is a native KVM limitations, and has nothing to do with CloudStack.
So no, you need to have QCOW2 on some file system in order to have VM snapshots support. On Tue, 16 Feb 2021 at 15:19, Peter Klein <pkl...@untangledtechnology.com> wrote: > Hi Matt, > > We run Cloudstack + KVM + Ceph. We haven't had any luck getting > snapshots to work but the alternative we've settled on for now is to > take snapshots of the storage volume instead of the VM itself. Restoring > from a snapshot this way is pretty cumbersome as you need to create a > template from the storage snapshot and then create a "new" VM instance > using that template. > > > Thanks, > > Peter > > On 2/16/21 09:04, Matthew Ritchie wrote: > > Hi everyone, > > > > I am working on a Cloudstack + KVM + Solidfire PoC and as far as I > > understand it is not possible to get a VM snapshot using SF as a primary > > storage. > > > > I wanted to ask the community what is the recommended way to get a VM > > snapshot when one is using Cloudstack + KVM + (some block storage > solution)? > > > > As it is crucial to provide to clients the "VM snapshot" capability I > guess > > there will be some sort of experience on that matter. > > > > thanks in advance > > Matt > > > -- Andrija Panić
