Description of problem: The Ceilometer which is one of OpenStack components logged, at warning level, periodically as follows. 2015-10-12 13:06:21.100 2189 WARNING ceilometer.compute.pollsters.memory [-] Cannot inspect data of MemoryUsagePollster for 41879320-053a-4742-a3f8-e03e707477ad, non-fatal reason: Failed to inspect memory usage of instance-0000003d, can not get info from libvirt The Libvirt seems not to be able to inspect actual memory usage from windows instances. This unexpected situation happens to only memory inspection. Version-Release number of selected component (if applicable): libvirt-1.2.8-16.el7_1.4.x86_64 Every non-windows instances which are usually linux are fine. Is there any condition where the Libvirt ends up with failing to inspect that usage. How reproducible: Steps to Reproduce: 1. Launch a new windows instance. 2. 3. Actual results: Expected results: Additional info:
Those memory statistics requested by ceilometer: https://github.com/openstack/ceilometer/blame/master/ceilometer/compute/virt/libvirt/inspector.py#L193 require cooperation of the guest's memballoon driver. If all the guests have a <memballoon> device with the period for gathering memory statistics set in that device - <stats period='5'/>, then there's nothing else libvirt can do. If the statistics are needed, make sure there is a virtio memory balloon driver installed in the guest. If they are not, maybe ceilometer's logging is too verbose. Either way this does not look like a libvirt bug. Please reassign it to the proper component - either virtio-win (if you suspect there is a bug in the guest driver) or ceilometer (if the verbose logging is the issue).
I'm fairly sure that the virtio-win drivers don't support returning detailed guest memory statistics.
@Daniel, Thank you for your suggestion. Rgds, Shinobu