Open Stack

Il 10/05/2012 11:48, Alvaro Lopez ha scritto:
> On Thu 10 May 2012 (10:41), Muriel wrote:
>> If I remember correctly, the qcow images are not the only problem
>> with xen, but I'm far from the code for too long time. In the past
>> (diablo), the method for counting the ram (and cpu perhaps?) did not
>> work with xen and this affected the choices of the scheduler. I have
>> no idea if this happens in essex/folsom.
> I've sent to review some code [1] that tries to fix this issue [2].
>
> [1] https://review.openstack.org/#/c/7296/
> [2] https://bugs.launchpad.net/nova/+bug/997014
>
> Regards,
Great! But there is a reason if are you using /proc/meminfo instead of 
getInfo when calculating the memory used?
You know if there is a way to get, using libvirt, the reserved memory 
for dom0? Or the only solution is to read the configuration file of xen?

Thanks,
Muriel