From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <324fccf0704170621g1bfb4632nbf121e0fcc444336@mail.gmail.com>
Date: Tue, 17 Apr 2007 08:21:58 -0500
From: "John Osborne" <osborne6@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] xen3 and pae problems
In-Reply-To: <41cbfaf1e0b85c8124c2a873544e1430@hamnavoe.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <324fccf0704162134oa4492d4lab14bda5c0cfe34d@mail.gmail.com>
	<41cbfaf1e0b85c8124c2a873544e1430@hamnavoe.com>
Topicbox-Message-UUID: 4a3d528c-ead2-11e9-9d60-3106f5b1d025

I've tried using the non-pae package and setting grub to load the
non-pae hypervisor.  The hypervisor then complains that the Dom0 linux
kernel has pae enabled.

>>From what I've googled, PAE was enabled by default in the linux kernel
in Debian Etch back in February or so, breaking alot of stuff in what
was testing.  I've found a few similar messages on other lists
relating to Fedora, RHEL5, and CentOS as having PAE enabled in the
kernel, as well as instructions/notes on how to build a non-PAE linux
kernel, so one can run the non-PAE xen hypervisor, thus being able to
run non-PAE enabled/capable/etc guest Doms under xen.

I've been considering just installing NetBSD to work around this :P

I probably should search a little bit more...

On 4/17/07, Richard Miller <9fans@hamnavoe.com> wrote:
> > Turns out PAE is setup by default with the linux-xen kernels
> > in debian.  There is a non-PAE hypervisor, but that would require me
> > to build a new kernel.
>
> It appears there are separate packages 'xen3' and 'xen3-pae' for
> debian.  So you shouldn't need to build a kernel - just use the
> appropriate package.
>
>


-- 
John Osborne
osborne6@ieee.org/osborne6@gmail.com/jro@freeshell.org