xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: "Jonathan Tripathy" <jonnyt@abpni.co.uk>,
	"Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xen.org" <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 09:12:15 +0100	[thread overview]
Message-ID: <CC5BA46F.49F32%keir@xen.org> (raw)
In-Reply-To: <5035DB70.8090800@abpni.co.uk>

On 23/08/2012 08:27, "Jonathan Tripathy" <jonnyt@abpni.co.uk> wrote:

> Thanks, Pasi.
> 
> A couple of questions:
> 
> I'm guessing xen.efi (from 4.2) just replaces grub??
> 
> Also, if I were to apply that patch from superuser
> (http://serverfault.com/questions/342109/xen-only-sees-512mb-of-system-ram-sho
> uld-be-8gb-uefi-boot),
> would have have any bad consequences? I'm very security conscience as
> the DomUs are untrusted...

Firstly, the same effect *should* be had by adding no-real-mode to your Xen
command line. So try that first.

Secondly, it is arguable that we should patch Xen to prefer "Multiboot-e820"
over "Xen-e801".

And yes, overall if you have a UEFI BIOS then using UEFI Xen is probably
best of all :)

 -- Keir

> Thanks
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2012-08-23  8:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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  0:11   ` 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 [this message]
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
2012-08-23  9:50 Jonathan Tripathy
2012-08-23 11:17 ` Keir Fraser

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=CC5BA46F.49F32%keir@xen.org \
    --to=keir@xen.org \
    --cc=jbeulich@suse.com \
    --cc=jonnyt@abpni.co.uk \
    --cc=pasik@iki.fi \
    --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).