From: Ian Campbell <ian.campbell@citrix.com>
To: Andreas Sundstrom <sunkan+lists.xen-devel@zappa.cx>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>, xen-devel@lists.xen.org
Subject: Re: [BUG] XEN domU crash when PV grub chainloads 32-bit domU grub
Date: Wed, 23 Sep 2015 15:18:42 +0100 [thread overview]
Message-ID: <1443017922.10338.234.camel@citrix.com> (raw)
In-Reply-To: <20150923124711.Horde.fWm6OM5grq3w6d8plIH4Fpd@apache.zappa.cx>
On Wed, 2015-09-23 at 12:47 +0000, Andreas Sundstrom wrote:
> Citerar Ian Campbell <ian.campbell@citrix.com>:
>
> > Along those lines, if the _host_ has buckets of RAM then might it be
> > worth
> > restricting it in case the issue is with getting MFNs which are not
> > representably by the 32-bit PV interfaces? (IIRC the limit is ~160G due
> > to
> > the size of the m2p hole, a 32-bit MFN spans 16TB so it's unlikely to
> > be
> > that).
> >
> > Likewise maybe the issue is with full addresses which don't fit in a 32
> > -bit
> > number (which is maybe more likely to happen if grub uses a 1:1 mapping
> > like I would guess it does), so limiting the host to <4GB might also be
> > interesting?
> >
>
> If this was meant for me I will need more information to understand
> what to test.
> dom0 has either 12G or 8G memory in my test machines if that makes a
> difference.
It was, sorry for not being clear.
How much memory do the test machines have?
If it is more than 160G then try booting with "mem=160G" on the hypervisor
(not Linux) command line. You can just edit that in via grub.
Then try with mem=4G (which might require shrinking dom0 too of course).
Ian.
next prev parent reply other threads:[~2015-09-23 14:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 20:03 [BUG] XEN domU crash when PV grub chainloads 32-bit domU grub Andreas Sundstrom
2015-09-22 7:22 ` Andrew Cooper
2015-09-22 8:52 ` Ian Campbell
2015-09-22 13:26 ` Andreas Sundstrom
2015-09-22 8:53 ` [Xen-devel] " Ian Campbell
2016-01-22 12:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-22 13:01 ` Andrew Cooper
2016-01-22 13:01 ` [Xen-devel] " Andrew Cooper
2016-01-22 13:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-22 13:43 ` Andrew Cooper
2016-01-22 13:43 ` [Xen-devel] " Andrew Cooper
2016-01-22 13:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-22 17:44 ` [Xen-devel] " Andreas Sundstrom
2016-01-22 17:44 ` Andreas Sundstrom
2016-01-22 12:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-09-22 8:53 ` Ian Campbell
2015-09-22 22:37 ` Samuel Thibault
2015-09-23 8:34 ` Ian Campbell
2015-09-23 12:47 ` Andreas Sundstrom
2015-09-23 14:18 ` Ian Campbell [this message]
2015-09-24 17:28 ` Andreas Sundstrom
2015-09-25 8:36 ` Ian Campbell
2015-09-25 13:23 ` Andreas Sundstrom
2015-09-23 8:37 ` Andreas Sundstrom
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=1443017922.10338.234.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=sunkan+lists.xen-devel@zappa.cx \
--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 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.