From: PGNet Dev <pgnet.dev@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: repeating 'd1v0 Over-allocation for domain 1' messages in xen 4.7 Host logs on PVHVM Guest launch
Date: Wed, 29 Jun 2016 05:58:42 -0700 [thread overview]
Message-ID: <b4cb25cb-13f4-a7d2-affa-243c0e76b718@gmail.com> (raw)
In-Reply-To: <5773B9FA02000078000F9BF8@prv-mh.provo.novell.com>
On 06/29/2016 03:07 AM, Jan Beulich wrote:
>> What are these 'Over-allocation' messages?
> An indication of the guest trying to allocate more memory that the
host admin has allowed.
currently, each guest has allocated
maxmem = 2048
memory = 2048
>> What needs to be fixed, or if of no concern, can these messages be silenced?
>
> Perhaps something wrong in the guest's balloon driver.
I'm seeing these @host log-entries for Ubuntu, Arch & Opensuse guests.
As a guest issue is suspected, a post of debug-level dmesg output from
the guest would be useful?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-29 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 0:06 repeating 'd1v0 Over-allocation for domain 1' messages in xen 4.7 Host logs on PVHVM Guest launch PGNet Dev
2016-06-29 10:07 ` Jan Beulich
2016-06-29 12:58 ` PGNet Dev [this message]
2016-06-29 14:10 ` PGNet Dev
2016-06-29 14:17 ` Jan Beulich
2016-06-29 15:38 ` PGNet Dev
2016-06-29 15:59 ` Jan Beulich
2016-06-29 16:27 ` PGNet Dev
2016-07-04 11:22 ` George Dunlap
2016-07-04 14:58 ` PGNet Dev
2016-07-05 13:35 ` George Dunlap
2016-07-05 14:13 ` PGNet Dev
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=b4cb25cb-13f4-a7d2-affa-243c0e76b718@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).