Changeset 1650


Ignore:
Timestamp:
Nov 15, 2008, 10:30:59 AM (16 years ago)
Author:
broder
Message:

Choose a host based on the maximum possible free memory, not the
unallocated memory

This works around the case where dom0's RAM doesn't get ballooned down

Location:
trunk/packages/invirt-remote-server
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • trunk/packages/invirt-remote-server/debian/changelog

    r1608 r1650  
     1invirt-remote-server (0.0.17) unstable; urgency=low
     2
     3  * Get the host with the most RAM based on the maximum recoverable
     4    memory, not the memory currently available to Xen
     5
     6 -- Evan Broder <broder@mit.edu>  Sat, 15 Nov 2008 10:30:10 -0500
     7
    18invirt-remote-server (0.0.16) unstable; urgency=low
    29

  • trunk/packages/invirt-remote-server/files/usr/sbin/invirt-remote-create

    r1176 r1650  
    1818    # XXX will the output of 'xm info' always be parseable YAML?
    1919    results = bcast('info')
    20     return max((int(o['free_memory']), s) for (s, o) in results)[1]
     20    return max((int(o['max_free_memory']), s) for (s, o) in results)[1]
    2121
    2222def main(argv):
Note: See TracChangeset for help on using the changeset viewer.