From: Keir Fraser <keir@xen.org>
To: Jonathan Tripathy <jonnyt@abpni.co.uk>, xen-devel@lists.xen.org
Subject: Re: Can't see more than 3.5GB of RAM / UEFI / no e820 memory map detected
Date: Thu, 23 Aug 2012 12:17:19 +0100 [thread overview]
Message-ID: <CC5BCFCF.49F7F%keir@xen.org> (raw)
In-Reply-To: <bcb6194956c235510cd981003ba7e999@abpni.co.uk>
On 23/08/2012 10:50, "Jonathan Tripathy" <jonnyt@abpni.co.uk> wrote:
> On 23.08.2012 10:43, Keir Fraser wrote:
>> On 23/08/2012 09:58, "Jonathan Tripathy" <jonnyt@abpni.co.uk> wrote:
>>
>>>> What does your RAM map look like now from early Xen boot, using
>>>> no-real-mode? It shouldn't be "Xen-e801" any more at least, else
>>>> the
>>>> no-real-mode parameter isn't working.
>>>>
>>>
>>> Still Xen-e801, so it looks like no-real-mode isn't working :(
>>
>> Grrr it's been broken since tboot support went in, long ago. Going to
>> have
>> to fix that and backport to 4.1 and 4.0 branches...
>>
>> -- Keir
>
> Just for info, is it safe to use no-real-mode on a production system?
> Please keep in mind that our DomUs are untrusted. Or would it be better
> if I created a patch to change the order of the if block to prefer the
> multi-boot memory map?
No-real-mode is perfectly safe to use from that point of view -- it will
have no impact on safe containment of untrusted DomU's.
However, of course it is nice to not have to rely on no-real-mode, so please
try switching the ordring of that if block.
-- Keir
> Thanks
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-08-23 11:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 9:50 Can't see more than 3.5GB of RAM / UEFI / no e820 memory map detected Jonathan Tripathy
2012-08-23 11:17 ` Keir Fraser [this message]
[not found] <50356E43.3030208@abpni.co.uk>
2012-08-22 23:48 ` Can't see more than 3.5GB of RAM Jonathan Tripathy
2012-08-23 6:06 ` Can't see more than 3.5GB of RAM / UEFI / no e820 memory map detected Pasi Kärkkäinen
2012-08-23 7:22 ` Pasi Kärkkäinen
2012-08-23 7:27 ` Jonathan Tripathy
2012-08-23 7:39 ` Jan Beulich
2012-08-23 8:07 ` Jonathan Tripathy
2012-08-24 15:35 ` Jan Beulich
2012-08-24 17:39 ` Jonathan Tripathy
2012-08-24 20:05 ` Keir Fraser
2012-08-28 19:36 ` Jonathan Tripathy
2012-08-28 21:10 ` Keir Fraser
2012-08-28 21:13 ` Jonathan Tripathy
2012-08-28 21:37 ` Keir Fraser
2012-08-28 21:41 ` Keir Fraser
2012-08-28 21:50 ` Jonathan Tripathy
2012-08-28 21:52 ` Jonathan Tripathy
2012-08-28 22:05 ` Jonathan Tripathy
2012-08-28 22:31 ` Keir Fraser
2012-08-28 22:33 ` Jonathan Tripathy
2012-08-23 8:12 ` Keir Fraser
2012-08-23 8:28 ` Jonathan Tripathy
2012-08-23 8:43 ` Keir Fraser
2012-08-23 8:49 ` Ian Campbell
2012-08-23 8:58 ` Jonathan Tripathy
2012-08-23 9:43 ` Keir Fraser
2012-08-23 9:13 ` Pasi Kärkkäinen
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=CC5BCFCF.49F7F%keir@xen.org \
--to=keir@xen.org \
--cc=jonnyt@abpni.co.uk \
--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).