X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=examples%2Fguestfs-testing.pod;h=c35c3b86698a12e787336f0ecd4f120965386d48;hp=3f2f0b4412c5bedad87109ee0c471770c7c67d28;hb=HEAD;hpb=a3b24296810d98e47552c6838dcd6ab6845aba03

diff --git a/examples/guestfs-testing.pod b/examples/guestfs-testing.pod
index 3f2f0b4..c35c3b8 100644
--- a/examples/guestfs-testing.pod
+++ b/examples/guestfs-testing.pod
@@ -38,8 +38,13 @@ following command a few times:
 After a few runs, the time should settle down to a few seconds (under
 5 seconds on fast 64 bit hardware).
 
+How to check for hardware virt:
+
 http://virt-tools.org/learning/check-hardware-virt/
 
+If the command above does not work at all, use
+L<libguestfs-test-tool(1)>.
+
 =head2 Run virt-alignment-scan on all your guests.
 
 Run L<virt-alignment-scan(1)> on guests or disk images:
@@ -97,7 +102,29 @@ L<virt-df(1)> lists disk space.  Run:
 
  virt-df
 
-Do the results match what's reported inside the guests?
+You can try comparing this to the results from L<df(1)> inside the
+guest, but there are some provisos:
+
+=over 4
+
+=item *
+
+The guest must be idle.
+
+=item *
+
+The guest disks must be synched using L<sync(1)>.
+
+=item *
+
+Any action such as booting the guest will write log files causing the
+numbers to change.
+
+=back
+
+We don't guarantee that the numbers will be identical even under these
+circumstances.  They should be similar.  It would indicate a bug if
+you saw greatly differing numbers.
 
 =head2 Try importing virt-df CSV output into a spreadsheet or database.