summaryrefslogtreecommitdiffstats
path: root/TODO.virt-top
diff options
context:
space:
mode:
authorRichard W.M. Jones <rjones@redhat.com>2008-02-20 11:42:37 +0000
committerRichard W.M. Jones <rjones@redhat.com>2008-02-20 11:42:37 +0000
commit63dfe1865a7a32e39f3811f4ce0ce6d39f7d2dbd (patch)
treec5eb8b245d9e39afce501d4848004a0762a07383 /TODO.virt-top
parentd7a277ed8a3312d927d712cb01807ea07d7b96ae (diff)
downloadvirt-top-63dfe1865a7a32e39f3811f4ce0ce6d39f7d2dbd.tar.gz
virt-top-63dfe1865a7a32e39f3811f4ce0ce6d39f7d2dbd.tar.xz
virt-top-63dfe1865a7a32e39f3811f4ce0ce6d39f7d2dbd.zip
Extra tasks for jmh
Diffstat (limited to 'TODO.virt-top')
-rw-r--r--[-rwxr-xr-x]TODO.virt-top4
1 files changed, 4 insertions, 0 deletions
diff --git a/TODO.virt-top b/TODO.virt-top
index 442ba1c..186aa42 100755..100644
--- a/TODO.virt-top
+++ b/TODO.virt-top
@@ -87,3 +87,7 @@ periodically (eg. every so often, specific time of day, etc.)
Can we look inside the guest to find out how much memory the guest
is actually using? Scenario is: One guest is maxed out and swapping
while other guests aren't using much of their allocated memory.
+
+*** 13 [jmh] Display reason why disk & network stats cannot be displayed.
+
+*** 14 [jmh] Show version of libvirt compiled against, running against.