All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: PAE requirement in config file for HVM guests
Date: Wed, 22 Nov 2006 09:47:35 +0000	[thread overview]
Message-ID: <C189CD37.4DD3%keir@xensource.com> (raw)
In-Reply-To: <45641A31.76E4.0078.0@novell.com>




On 22/11/06 08:36, "Jan Beulich" <jbeulich@novell.com> wrote:

> Could anyone explain why it was necessary in 3.0.3 to require config files
> for 32-bit/PAE or 64-bit x86 hvm guests on respective hypervisors to have
> an explicit 'pae = 1', whereas in 3.0.2 this wasn't needed? It would seem
> that the emulated CPUID feature flag should, as in 3.0.2, just be
> suppressed if the hypervisor really can't support PAE (i.e. 32-bit non-PAE
> build).

It's only to allow pae to be masked off. I think that you can specify pae=1
always and it won't be advertised to the guest if the host doesn't support
it. If this isn't the case it should be, and I'd take a patch to make it so.
:-)

Oh, and xend should default pae=1 if it doesn't do so already.

 -- Keir

      reply	other threads:[~2006-11-22  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  8:36 PAE requirement in config file for HVM guests Jan Beulich
2006-11-22  9:47 ` Keir Fraser [this message]

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=C189CD37.4DD3%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.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.