Yes, that's the scariest thing: you never know that the image is corrupted on
the same day. Usually, a week or a fortnight could pass before one gets to know
about a problem (and all old snapshots are successfully removed by that time).
Some time ago I implemented a simple script that runs `qemu
Just like that cat in a box. The observer needs to open the box to learn if the
cat is alive. :-)
‐‐‐ Original Message ‐‐‐
On Friday, 1 February 2019 22:25, Ivan Kudryavtsev
wrote:
> Yes, only after the VM shutdown, the image is corrupted.
>
> пт, 1 февр. 2019 г., 15:01 Sean Lair sl...
Hi Darren,
Thanks for reporting. I've copied Wido who can check and comment on the
packages hosted on download.cloudstack.org.
I maintain the signed deb/rpm packages from shapeblue [1]:
https://www.shapeblue.com/packages/
[1] http://packages.shapeblue.com/release.asc
- Rohit
I'd also like to add another detail, if no one minds.
Sometimes one can run into this issue without shutting down a VM. The disaster
might occur right after a snapshot is copied to a secondary storage and deleted
from the VM's image on the primary storage. I saw it a couple of times, when it
ha
By the way, RedHat recommended to suspend a VM before deleting a snapshot too:
https://bugzilla.redhat.com/show_bug.cgi?id=920020. I'll quote it here:
> 1. Pause the VM
> 2. Take an internal snapshot with the 'savevm' command of the qemu monitor
> of the running VM, not with an external qe
