On Thu, Apr 03, 2014 at 11:39:29AM -0400, Tomoki Sekiyama wrote: > These will freeze and thaw filesystems within guest. The APIs take @disks > and @ndisks parameters to specify disks to be frozen or thawed. > The parameters can be NULL and 0, then the all mounted filesystes are > frozen or thawed. If some disks are frozen multiple times, they are not > thawed until requested to be thawed as many times as freeze request. > @flags parameter, which are currently not used, is for future extensions. > > Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama@xxxxxxx> > --- > include/libvirt/libvirt.h.in | 10 +++++ > src/driver.h | 14 ++++++ > src/libvirt.c | 92 ++++++++++++++++++++++++++++++++++++++++++ > src/libvirt_public.syms | 6 +++ > 4 files changed, 122 insertions(+) > > diff --git a/include/libvirt/libvirt.h.in b/include/libvirt/libvirt.h.in > index 930b7e8..d408f19 100644 > --- a/include/libvirt/libvirt.h.in > +++ b/include/libvirt/libvirt.h.in > @@ -5277,6 +5277,16 @@ int virDomainFSTrim(virDomainPtr dom, > unsigned long long minimum, > unsigned int flags); > > +int virDomainFSFreeze(virDomainPtr dom, > + const char **disks, > + unsigned int ndisks, > + unsigned int flags); > + > +int virDomainFSThaw(virDomainPtr dom, > + const char **disks, > + unsigned int ndisks, > + unsigned int flags); Are all guests OS required to support unfreeze on a per disk basis. I vaguely recall someone mentioning that some OS can do all-or-none only. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list