X-Git-Url: http://git.annexia.org/?p=virt-top.git;a=blobdiff_plain;f=virt-top%2Fvirt-top.pod;h=4d7df4ec90180d836ff74f8068e1b84263995836;hp=e11e814634a4f852187b43b870ffb6e69e0bbfd1;hb=1f3c5a55e0dbbab20fcd23cd81689e0f6ca72669;hpb=3d48ff51cf3447943537639dc6c1a9e5dc5120d2

diff --git a/virt-top/virt-top.pod b/virt-top/virt-top.pod
index e11e814..4d7df4e 100755
--- a/virt-top/virt-top.pod
+++ b/virt-top/virt-top.pod
@@ -369,6 +369,21 @@ Note that in the current implementation, options specified in
 the init file override options specified on the command line.
 This is a bug and this behaviour may change in the future.
 
+=head1 NOTES
+
+=head2 NETWORK RX BYTES AND PACKETS
+
+Libvirt/virt-top has no way to know that a packet transmitted to a
+guest was received (eg. if the guest is not listening).  In the
+network RX stats, virt-top reports the packets transmitted to the
+guest, on the basis that the guest might receive them.
+
+In particular this includes broadcast packets.  Because of the way
+that Linux bridges work, if the guest is connected to a bridge, it
+will probably see a steady "background noise" of RX packets even when
+the network interface is idle or down.  These are caused by STP
+packets generated by the bridge.
+
 =head1 SEE ALSO
 
 L<top(1)>,