By a very strict reading, this is an API change.
Matt argues (and I agree) that if you really depend on autosync being
off by default, then you were depending on the undefined behaviour
that happens when you kill the qemu container without first doing
sync. ie. Data might or might not have been written, depending on how
fast the kernel was writing to disk versus how soon the container got
killed.
On the other hand, this is a frequent cause of problems when using the
API (see
http://libguestfs.org/guestfs.3.html#libguestfs_gotchas) and
changing the default means this problem goes away.
You can revert to the old behaviour by adding:
guestfs_set_autosync (g, 0);
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://et.redhat.com/~rjones/libguestfs/
See what it can do:
http://et.redhat.com/~rjones/libguestfs/recipes.html