Re: [PATCH v3 0/3] Mark and document restore with managed save as risky

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Michal and Daniel,

On Fri, Jan 10, 2020 at 11:01:14AM +0100, Michal Privoznik wrote:
> > > This series marks restore of an inactive qemu snapshot while there is
> > > managed saved state as risky due to the reasons explained in patch 1 and
> > > 3. Patch 2 is a simple reformatting of the documentation with no other
> > > changes in preparation of addition of more reasons why reverts might
> > > need to be forced.
> > > 
> > > Changes from v2:
> > > - fix manpage typo exising -> existing
> > > - change manpage qemu hypervisor name case to QEMU
> > > 
> > > Changes from v1:
> > > - reword error message to "error: revert requires force: snapshot
> > >    without memory state, removal of existing managed saved state strongly
> > >    recommended to avoid corruption"
> > > - add documentation of the new behaviour
> > > 
> > > Michael Weiser (3):
> > >    qemu: Warn of restore with managed save being risky
> > >    docs: Reformat snapshot-revert force reasons
> > >    docs: Add snapshot-revert qemu managedsave force
> > All patches:
> > Reviewed-by: Daniel Henrique Barboza <danielhb413@xxxxxxxxx>
> And pushed now.

Thank you for your help on this!
-- 
Thanks,
Michael


--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list





[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux