From: Keir Fraser <keir.fraser@eu.citrix.com>
To: abhinavs_iitkgp@yahoo.co.in, xen-devel@lists.xensource.com
Subject: Re: How to build non-PAE dom0 kernel with Xen-3.2-testing (PAE-disabled)?
Date: Tue, 23 Sep 2008 17:38:47 +0100 [thread overview]
Message-ID: <C4FEDA27.27667%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <317701.10184.qm@web7902.mail.in.yahoo.com>
On 23/9/08 17:17, "Abhinav Srivastava" <abhinavs_iitkgp@yahoo.co.in> wrote:
>> Ah, actually we removed non-PAE support from Xen 3.2. So
>> you have to build a
>> PAE hypervisor and kernel. If you want non-PAE support, you
>> have to use Xen
>> 3.1.
>>
>> -- Keir
>
> Ohh no. Did it happen recently? I knew that Xen-3.3 did not have non-PAE
> support. But, I did not know about Xen 3.2. I took Xen3.2 testing version
> kernel in july from mercury and could built non-PAE hypervisor and kernel. Is
> it someway I can get that build from mercury or it got changed backwardly?
>
> Thanks for the clarification.
Oh sorry, you're quite right. All versions of Xen 3.2 do support non-PAE.
However, the current tip of the linux-2.6.18-xen.hg repository does not.
What you should do within that repository is 'hg update xen-3.2.0': this
will revert your repository to a version which is old enough to support
building as non-PAE. Another thing which might work instead, and let you
keep other more recent changes and fixes, is 'hg export 616 | patch -Rp1'.
-- Keir
next prev parent reply other threads:[~2008-09-23 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 1:38 How to build non-PAE dom0 kernel with Xen-3.2-testing (PAE-disabled)? Abhinav Srivastava
2008-09-23 6:43 ` Keir Fraser
2008-09-23 15:58 ` Abhinav Srivastava
2008-09-23 16:06 ` Keir Fraser
2008-09-23 16:17 ` Abhinav Srivastava
2008-09-23 16:38 ` Keir Fraser [this message]
2008-09-23 17:00 ` Abhinav Srivastava
2008-09-23 18:15 ` 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=C4FEDA27.27667%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=abhinavs_iitkgp@yahoo.co.in \
--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.