On Tue, 2013-05-14 at 14:58 -0600, Eric Blake wrote: > > > > Virt-manager will then have cater for both cases, when libvirt can > > provide this info via QMP query commands and when it can't. > > virt-manager doesn't care about the difference. The libvirt API will > either have information to provide (super-old qemu that blocked on HMP, > or modern API that uses new QMP) or it won't (intermediate qemu that > ditched the info to avoid blocking). All you have to do is upgrade qemu > and libvirt, and virt-manager will magically start providing stats again. Yes, I agree with you that virt-manager won't care about the difference. However, currently virt-manager doesn't even use the virDomainMemoryStats() function. To obtain the memory stats, it uses the virDomainGetInfo() function (see: https://git.fedorahosted.org/cgit/virt-manager.git/tree/virtManager/domain.py#n1716 https://git.fedorahosted.org/cgit/virt-manager.git/tree/virtManager/domain.py#n1294), which only reports the current VM memory allocation. This issue is being tracked at: https://bugzilla.redhat.com/show_bug.cgi?id=878425 > Yes, please - having it filed by you (as opposed to me) will give it > some more weight when Red Hat evaluates which bugs to fix for RHEL. No problem, filed a new bug: https://bugzilla.redhat.com/show_bug.cgi?id=963488 Best regards, Tadej _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
