berrange at redhat
May 10, 2012, 6:41 AM
On Thu, May 10, 2012 at 03:17:59PM +0200, Muriel wrote:
Re: Improving Xen support in the libvirt driver
[In reply to]
> 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  that tries to fix this issue .
> > https://review.openstack.org/#/c/7296/
> > https://bugs.launchpad.net/nova/+bug/997014
> 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?
Dom0 appears as just another guest in Xen/libvirt, so you can query
its memory allocation using normal libvirt APIs
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
Mailing list: https://launchpad.net/~openstack
Post to : openstack [at] lists
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp