Re: [Xen-devel] Xen 4.9 + kernel 4.13rc2 -- ballooning regression? reappearance of "Over-allocation for domain 1" errors

[Juergen Gross <jgross@xxxxxxxx>]

On 03/08/17 00:43, Boris Ostrovsky wrote:
> On 08/02/2017 08:01 AM, Juergen Gross wrote:
>> On 01/08/17 16:28, PGNet Dev wrote:
>>> On 7/28/17 9:02 AM, PGNet Dev wrote:
>>>> On 7/27/17 11:23 PM, Juergen Gross wrote:
>>>>> Can you please post the domain's config file used to create the domain
>>>>> and the kernel config?
>>>> Sure.
>>>>
>>>>    https://pastebin.com/M6cr2pX7
>>>>
>>> Any add'l info needed?
>> No, I don't think so.
>>
>> IMO the problem is related to the fact that the balloon driver tries to
>> use then kernel's view of how much memory it is owning and setting this
>> number in relation to Xen's view how much memory it should try to have.
>>
>> Maybe before adding memory from Xen the kernel should ask the hypervisor
>> how much memory it has already from Xen's point of view and how much it
>> is allowed to have. This will avoid the messages you have seen as long
>> as there are no interfering actions from Xen (e.g. lowering the maximum
>> reservation) while the kernel is trying to balloon up.
> 
> Could this be caused by your recent ballooning patch
> (96edd61dcf44362d3ef0bed1a5361e0ac7886a63)?

Only by trying to reduce the domain's memory via "xl mem-set" before the
balloon driver was initialized and then adding memory after the balloon
driver has been started.

Other than that I have no idea how my patch would result in such a
behavior.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel