All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elliott Mitchell <ehem+xen@m5p.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
	Roger Pau Monn?? <roger.pau@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/pod: Do not fragment PoD memory allocations
Date: Wed, 27 Jan 2021 12:12:59 -0800	[thread overview]
Message-ID: <YBHJS3NEX5+iEqyd@mattapan.m5p.com> (raw)
In-Reply-To: <f6a75725-edc2-ee2d-0565-da1efae05190@suse.com>

On Wed, Jan 27, 2021 at 10:47:19AM +0100, Jan Beulich wrote:
> On 26.01.2021 18:51, Elliott Mitchell wrote:
> > Okay, this has been reliably reproducing for a while.  I had originally
> > thought it was a problem of HVM plus memory != maxmem, but the
> > non-immediate restart disagrees with that assessment.
> 
> I guess it's not really clear what you mean with this, but anyway:
> The important aspect here that I'm concerned about is what the
> manifestations of the issue are. I'm still hoping that you would
> provide such information, so we can then start thinking about how
> to solve these. If, of course, there is anything worse than the
> expected effects which use of PoD can have on the guest itself.

Manifestation is domain 0 and/or Xen panic a few seconds after the
domain.cfg file is loaded via `xl`.  Everything on the host is lost and
the host restarts.  Any VMs which were present are lost and need to
restart, similar to power loss without UPS.

Upon pressing return for `xl create domain.cfg` there is a short period
of apparently normal behavior in domain 0.  After this there is a short
period of very laggy behavior in domain 0.  Finally domain 0 goes
unresponsive and so far by the time I've gotten to the host's console it
has already started to reboot.

The periods of apparently normal and laggy behavior are perhaps 5-10
seconds each.

The configurations I've reproduced with have had maxmem substantially
larger than the total host memory (this is intended as a prototype of a
future larger VM).  The first recorded observation of this was with
Debian's build of Xen 4.8, though I recall running into it with Xen 4.4
too.

Part of the problem might also be attributeable to QEMU touching all
memory on start (thus causing PoD to try to populate *all* memory) or
OVMF.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445




  reply	other threads:[~2021-01-27 20:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24  4:47 [PATCH] x86/pod: Do not fragment PoD memory allocations Elliott Mitchell
2021-01-25  9:56 ` Jan Beulich
2021-01-25 10:20   ` Andrew Cooper
2021-01-25 17:46   ` Elliott Mitchell
2021-01-26 11:08     ` Jan Beulich
2021-01-26 17:51       ` Elliott Mitchell
2021-01-27  9:47         ` Jan Beulich
2021-01-27 20:12           ` Elliott Mitchell [this message]
2021-01-27 21:03             ` Andrew Cooper
2021-01-27 22:28               ` Elliott Mitchell
2021-01-28 10:19                 ` Jan Beulich
2021-01-28 18:26                   ` Elliott Mitchell
2021-01-28 22:42                     ` George Dunlap
2021-01-28 22:56                       ` George Dunlap
2021-01-29 10:56                         ` George Dunlap
2021-01-31 18:13                       ` Elliott Mitchell
2021-02-01  8:15                         ` Roger Pau Monné
2021-02-01 10:35                         ` George Dunlap
2021-02-02  5:58                           ` Elliott Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2021-01-24  4:47 Elliott Mitchell

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=YBHJS3NEX5+iEqyd@mattapan.m5p.com \
    --to=ehem+xen@m5p.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 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.