From: Boris Ostrovsky <bostrovsky@virtualiron.com>
To: nitin.a.kamble@intel.com, Keir.Fraser@cl.cam.ac.uk,
m+Ian.Pratt@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: RE: PAE dom0 is broken with the default config
Date: Wed, 05 Apr 2006 21:14:01 -0400 [thread overview]
Message-ID: <44346B59.8080800@virtualiron.com> (raw)
In-Reply-To: <E1FRHXg-0001cV-9t@host-192-168-0-1-bcn-london>
>> I built PAE Xen with the default config, and it is not
>> booting. Log is bellow. If I replace the
>> linux-defconfig_xen_x86_32 file with the
>> linux-defconfig_xen0_x86_32 before building then dom0 is able
>> to boot and see more than 4Gig memory. This looks like a dom0
>> kernel config issue. Do you care PAE dom0 for 3.0.2 with the
>> default config? Is anybody working on this?
>
>
> This seems pretty unlikely to be a PAE issue -- we do quite extensive
> testing.
>
> Are you sure you have the right initrd? Is the same scsi driver being
> used as in the -xen0 case?
I suspect there may indeed be some sort of problem with PAE. I have domU RHEL4-U2
SMP 32-bit kernel that dies when it tries to set PAE bit in CR4 --- it
can't find translation for the next instruction (and for anything else, for
that matter: it keeps then getting GPFs on ignore_int's first instruction).
UP version of the same kernel and SMP versions of other kernels, such as 2.6.16,
don't have this problem.
-boris
next parent reply other threads:[~2006-04-06 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1FRHXg-0001cV-9t@host-192-168-0-1-bcn-london>
2006-04-06 1:14 ` Boris Ostrovsky [this message]
2006-04-07 0:56 PAE dom0 is broken with the default config Kamble, Nitin A
-- strict thread matches above, loose matches on Subject: below --
2006-04-06 10:50 Ian Pratt
2006-04-06 10:53 ` Keir Fraser
2006-04-06 1:11 Kamble, Nitin A
2006-04-05 23:33 Ian Pratt
2006-04-05 23:00 Kamble, Nitin A
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=44346B59.8080800@virtualiron.com \
--to=bostrovsky@virtualiron.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=nitin.a.kamble@intel.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.