From: Juergen Gross <jgross@suse.com>
To: pgnet.dev@gmail.com, Xen-devel@lists.xen.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: Xen 4.9 + kernel 4.13rc2 -- ballooning regression? reappearance of "Over-allocation for domain 1" errors
Date: Wed, 2 Aug 2017 14:01:05 +0200 [thread overview]
Message-ID: <dbb8a1c6-ea09-3bcd-b510-f589eedcb8ec@suse.com> (raw)
In-Reply-To: <740d5758-d357-a1cb-7992-7211dd8daa88@gmail.com>
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.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-02 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 18:20 Xen 4.9 + kernel 4.13rc2 -- ballooning regression? reappearance of "Over-allocation for domain 1" errors PGNet Dev
2017-07-28 6:23 ` Juergen Gross
2017-07-28 16:02 ` PGNet Dev
2017-08-01 14:28 ` PGNet Dev
2017-08-02 12:01 ` Juergen Gross [this message]
2017-08-02 22:43 ` Boris Ostrovsky
2017-08-03 13:51 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbb8a1c6-ea09-3bcd-b510-f589eedcb8ec@suse.com \
--to=jgross@suse.com \
--cc=Xen-devel@lists.xen.org \
--cc=boris.ostrovsky@oracle.com \
--cc=pgnet.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.