I don't remember where exactly i copied this from, but i found this in the mailing list somewhere. This supposedly is the output produced by the nova-diagnostics command with xen. Maybe this can help?
+----------------+-----------------+ | Property | Value | +----------------+-----------------+ | cpu0 | 4.3627 | | memory | 1171088064.0000 | | memory_target | 1171088064.0000 | | vbd_xvda_read | 0.0 | | vbd_xvda_write | 0.0 | | vif_0_rx | 3223.6870 | | vif_0_tx | 0.0 | | vif_1_rx | 104.4955 | | vif_1_tx | 0.0 | +----------------+-----------------+ On Tue, Mar 13, 2012 at 11:49 AM, Soren Hansen <so...@linux2go.dk> wrote: > 2012/3/12 Vishvananda Ishaya <vishvana...@gmail.com>: > > Diagnostics are a bunch of key/value pairs, but unfortunately there > doesn't > > seem to be an example of what they are. If someone running xen could > post > > the result of get_diagnostics so that it could be added to a docstring > and > > implemented for libvirt, that would be awesome. > > Once someone works out what this is actually supposed to look like, please > add > a unit test to test_virt_drivers to document it. > > -- > Soren Hansen | http://linux2go.dk/ > Senior Software Engineer | http://www.cisco.com/ > Ubuntu Developer | http://www.ubuntu.com/ > OpenStack Developer | http://www.openstack.org/ >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
