X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;ds=sidebyside;f=src%2Fguestfs.pod;h=915d8605a3759f94a7a0b854f1f7b9be03abecb9;hb=478f6c5bdbe4b7e466fe7eaca63aaba002f585ce;hp=7cfd2b29723f7639b368cbd1c23704306cecaf50;hpb=40f2b698ac765128bfcda5f0db893c95d09ae89a;p=libguestfs.git

diff --git a/src/guestfs.pod b/src/guestfs.pod
index 7cfd2b2..915d860 100644
--- a/src/guestfs.pod
+++ b/src/guestfs.pod
@@ -2671,6 +2671,10 @@ actions.
 
 L<virt-df(1)> command and documentation.
 
+=item C<edit>
+
+L<virt-edit(1)> command and documentation.
+
 =item C<examples>
 
 C API example code.
@@ -2819,6 +2823,15 @@ We have tested block devices up to 1 exabyte (2**60 or
 1,152,921,504,606,846,976 bytes) using sparse files backed by an XFS
 host filesystem.
 
+Although libguestfs probably does not impose any limit, the underlying
+host storage will.  If you store disk images on a host ext4
+filesystem, then the maximum size will be limited by the maximum ext4
+file size (currently 16 TB).  If you store disk images as host logical
+volumes then you are limited by the maximum size of an LV.
+
+For the hugest disk image files, we recommend using XFS on the host
+for storage.
+
 =head2 MAXIMUM SIZE OF A PARTITION
 
 The MBR (ie. classic MS-DOS) partitioning scheme uses 32 bit sector