yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

The code remains this way in Juno, and I can confirm it's reporting
correctly with libvirt 1.2.2. I wonder if the documentation for libvirt
is just wrong?

Grizzly is also out of support at this point, so the branch is no longer
active. However there should be an AUDIT message in you compute nodes
that you can match to the actual memory on the box to figure out if it's
completely bonkers.

** Changed in: nova
       Status: New => Opinion

-- 
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/1374132

Title:
  Nova libvirt driver convertion error?

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  Hi guys,

      We've noticed a weird behavior with nova compute reporting the
  wrong free memory size in Grizzly and Ubuntu.   The version of libvirt
  used is 1.0.2 and according to the documentation of libvirt, the
  memory is returned in KB but in the code, it says MB?  Did I miss
  something?

  
  Dave

  Doc:
  http://libvirt.org/guide/html/ch03s04s04.html
  http://libvirt.org/html/libvirt-libvirt.html#virNodeInfo

  The chunk of code in question:
      def get_memory_mb_total(self):
          """Get the total memory size(MB) of physical computer.

          :returns: the total amount of memory(MB).

          """

          return self._conn.getInfo()[1]

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1374132/+subscriptions