On Thu, Apr 20, 2017 at 12:57:08AM +0800, ZhiPeng Lu wrote: > we can get the network card statistics inside a virtual machine by > guest-network-get-interface-stat command. > it is very userful for us to monitor and analyze network traff.
In most cases you can already monitor guest network traffic from the statistics on the QEMU backend device (ie tap device). The exception is when doing PCI device assignment. Is the latter the reason why you need to add this functionality instead of just quuerying the host backend ? There have been a lot of proposals for new QEMU geust agent commands in the past few weeks - NIC statistics - Logged in users - Timezone offset - Hostname - OS version / product This makes me wonder what our intended scope is for the guest agent ? Are we happy to add arbitrary functionality to the guest agent, allowing it grow in size & complexity without bound. Or is it better to restrict it to tasks which are needed in order to coordinate management of the host virtualization layer and leave general purpose guest OS management to another app. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
