This also affects CentOS release on Newton ** Also affects: nova (CentOS) Importance: Undecided Status: New
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/997014 Title: [SRU] Memory is not correctly computed for Xen+libvirt Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) essex series: Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Precise: Fix Released Status in nova package in CentOS: New Bug description: The current code in libvirt/connection.py does not compute the memory usage correctly when using Xen. It takes the information from /proc/meminfo whose information is not correct (at least for Xen 4.1.2 on Ubuntu). I've spotted the following situations: - No memory limit on the dom0. Whenever a machine is spawned, the dom0 memory might be ballooned down, so the memory reported by meminfo is also shrinked. This causes that the memory_mb column in the compute_nodes table changes. - Memory limit on the dom0 (i.e dom0_mem option in grub). Meminfo only shows the memory available for the dom0, but will not honour the total memory and the memory that is actually available for the domUs (xm info|grep memory). I'm currently working on a fix, that I hope will be submitted soon. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997014/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp