X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=src%2Fguestfs.pod;h=514db030954abf350327e702d0ee0460fd0bc43f;hb=699f38f05f2545a2c188370500df17cc52cbdf98;hp=84eec6359caefec1c4287b06d77e25a97112213c;hpb=c0baa7bdb2b404e8c808700984b3fc1a699d8dd7;p=libguestfs.git diff --git a/src/guestfs.pod b/src/guestfs.pod index 84eec63..514db03 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -33,7 +33,8 @@ schemes, qcow, qcow2, vmdk. Libguestfs provides ways to enumerate guest storage (eg. partitions, LVs, what filesystem is in each LV, etc.). It can also run commands -in the context of the guest. Also you can access filesystems over FTP. +in the context of the guest. Also you can access filesystems over +FUSE. Libguestfs is a library that can be linked with C and C++ management programs (or management programs written in OCaml, Perl, Python, Ruby, @@ -558,6 +559,15 @@ Note that in L I. So quick and dirty guestfish scripts that forget to sync will work just fine, which can make this extra-puzzling if you are trying to debug a problem. +=item Mount option C<-o sync> should not be the default. + +If you use C, then C<-o sync,noatime> are added +implicitly. However C<-o sync> does not add any reliability benefit, +but does have a very large performance impact. + +The work around is to use C and set the mount +options that you actually want to use. + =item Read-only should be the default. In L, I<--ro> should be the default, and you should @@ -579,6 +589,29 @@ C to run commands. =back +=head2 PROTOCOL LIMITS + +Internally libguestfs uses a message-based protocol to pass API calls +and their responses to and from a small "appliance" (see L +for plenty more detail about this). The maximum message size used by +the protocol is slightly less than 4 MB. For some API calls you may +need to be aware of this limit. The API calls which may be affected +are individually documented, with a link back to this section of the +documentation. + +A simple call such as C returns its result (the file +data) in a simple string. Because this string is at some point +internally encoded as a message, the maximum size that it can return +is slightly under 4 MB. If the requested file is larger than this +then you will get an error. + +In order to transfer large files into and out of the guest filesystem, +you need to use particular calls that support this. The sections +L and L document how to do this. + +You might also consider mounting the disk image using our FUSE +filesystem support (L). + =head1 CONNECTION MANAGEMENT =head2 guestfs_h *