All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: pgnet.dev@gmail.com, Xen-devel@lists.xen.org
Subject: Re: Xen 4.9 + kernel 4.13rc2 -- ballooning regression? reappearance of "Over-allocation for domain 1" errors
Date: Fri, 28 Jul 2017 08:23:26 +0200	[thread overview]
Message-ID: <372c3a6d-085e-5ae0-e6a7-c89a54839434@suse.com> (raw)
In-Reply-To: <efd3a17c-6ae8-6796-f988-deb2e1c5d382@gmail.com>

On 27/07/17 20:20, PGNet Dev wrote:
> I've upgraded a Xen server's
> 
> 	xen-4.9.0_08-517.2.x86_64
> 	xen-libs-4.9.0_08-517.2.x86_64
> 
> kernel from 4.12x to 4.13x
> 
> 	uname -rm
> 		4.13.0-rc2-2.gb545b87-default x86_64
> 
> After upgrading, I see in my Dom0-attached serial console, a steady stream of,
> 
> 	...
> 	(XEN) [2017-07-27 18:00:25] d1v0 Over-allocation for domain 1: 524545 > 524544
> 	(XEN) [2017-07-27 18:00:58] d1v0 Over-allocation for domain 1: 524545 > 524544
> 	(XEN) [2017-07-27 18:01:31] d1v0 Over-allocation for domain 1: 524545 > 524544
> 	(XEN) [2017-07-27 18:02:04] d1v0 Over-allocation for domain 1: 524545 > 524544
> 	(XEN) [2017-07-27 18:02:36] d1v0 Over-allocation for domain 1: 524545 > 524544
> 	...
> 
> every 32-33 seconds.

Can you please post the domain's config file used to create the domain
and the kernel config?


Juergen

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

  reply	other threads:[~2017-07-28  6:23 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 [this message]
2017-07-28 16:02   ` PGNet Dev
2017-08-01 14:28     ` PGNet Dev
2017-08-02 12:01       ` Juergen Gross
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=372c3a6d-085e-5ae0-e6a7-c89a54839434@suse.com \
    --to=jgross@suse.com \
    --cc=Xen-devel@lists.xen.org \
    --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.