From: PGNet Dev <pgnet.dev@gmail.com>
To: 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 09:27:40 -0700 [thread overview]
Message-ID: <bc792403-2c17-a1d2-fe92-7443074b25b0@gmail.com> (raw)
In-Reply-To: <57740C8802000078000F9E12@prv-mh.provo.novell.com>
In summary, there's a problem
An indication of the guest trying to allocate more memory that the host
admin has allowed.
that's filling logs with 10s of thousands of redundant log entries, with
a suspicion that it's 'ballooning' issue in the guest
Perhaps something wrong in the guest's balloon driver.
With no currently known way to identify or troubleshoot the problem, and
provide info here that could be helpful
I'm simply not aware of existing output which would help; I can't
see any way around instrumenting involved code.
Not particularly ideal.
Since this is the recommended bug-report channel, any next suggestions?
Is there a particular dev involved in the ballooning that can be cc'd,
perhaps to add some insight?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-29 16:27 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
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 [this message]
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=bc792403-2c17-a1d2-fe92-7443074b25b0@gmail.com \
--to=pgnet.dev@gmail.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).