[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH][RFC] to fix xm list memory reporting
This patch addresses bugzilla #649, enabling `xm list' to display the actual amount of memory allocated by a guest. This is done by checking the value that the balloon driver returns after memory requests. As a result, I'm noticing that a guest that I've set to start with 128Mb will actually give the user 126Mb. All other allocations perform normally, and attempting to over-allocate will simply return the amount of space that the domain was able to expand to. Under the premises that xm list should report actual memory values, 2 tests in xm-test may need to be modified to verify the amount of memory that a guest is physically using, and not rely on the value in the config file as being the amount of memory that the guest will have. xm-test reactions to patch as of changset 11376: REASON: Started domain with 128MB, but it got 126 MB FAIL: 08_create_mem128_pos.test REASON: Started domain with 256MB, but it got 254 MB FAIL: 09_create_mem256_pos.test Running 'free' inside of each guest shows 126, and 254 respectively, not their config file #'s. Signed-off-by: Tommie McAfee <tommie.mcafee@xxxxxxxxxx> Regards, Tommie McAfee Xen-Testing Attachment:
xm_list.patch _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |