RFC: requesting APIs for host physical resource discovery

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The current libvirt APIs allow the host's physical resources to be split up
and allocated to guest domains, however, there is no way to discover what
the available host resources actually are. Thus I would like to suggest the
inclusion of new APIs to enable host resource discovery. As a starting point
I'd like to be able to query the following information:

  * Number of physical CPUs - ability to enumerate the CPUs in the host,
    both those currently present, and theoretical maximum (to take account
    of hotplug). 
  * Amount of RAM  - actual physical RAM present, and that available for
    guest usage (eg discounting that reserved by a hypervisor or equiv)
  * CPU relationship - ie ability to distinguish between CPUs which
    are hyperthread siblings, on same core, or on separate sockets

Alonside these basic queries it would be desirable to add a further resource
resource management API to allow for setting of a guest domain's CPU affinity.
ie ability control what CPUs the VMM is allowed to schedule a domain on.

Once this first basic set of caapbilties for resource discovery are provided
for, then I believe it will be neccessary to provide some more advanced 
queries, in particular:

  * NUMA topology - ability to enumerate NUMA nodes, the CPUs associated
    with each node & the RAM range mapped to that node

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]