On 15/03/2018 16:49, Eric Blake wrote:
Yes, having two processes (in this case, the qemu process under
libvirt's control, and the qemu-img process) both trying to write to a
single qcow2 file at once is a recipe for disaster. You are VERY likely
to cause irreparable disk corruption;
On 03/15/2018 08:55 AM, Gionatan Danti wrote:
Il 15-03-2018 09:13 Ján Tomko ha scritto:
It is not safe.
For a running domain, you need to go through libvirt and also save the
memory of the VM - doing just the disk snapshot for a running machine
would be an equivalent of copying a physical hard
Il 15-03-2018 09:13 Ján Tomko ha scritto:
It is not safe.
For a running domain, you need to go through libvirt and also save the
memory of the VM - doing just the disk snapshot for a running machine
would be an equivalent of copying a physical hard drive after pulling
out the power cord.
Jan
On Wed, Mar 14, 2018 at 09:36:52AM +0100, Gionatan Danti wrote:
Hi all,
I have a question about internal qcow2 snapshots of a live/running
virtual machine taken via "qemu-img snapshot command".
My question is: is it safe to execute the command above against a
running machine? Or it will cause
Hi all,
I have a question about internal qcow2 snapshots of a live/running
virtual machine taken via "qemu-img snapshot command".
My question is: is it safe to execute the command above against a
running machine? Or it will cause corruption? Naively I think it should
*not* be safe, however,
