From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: xen-devel@lists.xensource.com
Subject: PV domU with 255GB boot failure
Date: Mon, 16 Feb 2009 20:00:41 -0800 [thread overview]
Message-ID: <499A3669.6020605@oracle.com> (raw)
Hi,
Trying to boot a PV 64bit guest with 255GB mem it hangs in
extend_init_mapping() in init-xen.c. The hang is in the loop:
/* Finally, blow away any spurious initial mappings. */
while (1) {
pmd = (pmd_t *)&page[pmd_index(va)];
if (pmd_none(*pmd))
break;
HYPERVISOR_update_va_mapping(va, __pte_ma(0), 0);
va += PAGE_SIZE;
}
More details:
tables_space : 0x1ff05000
__START_KERNEL_map == 0xffffffff80000000
&_text == 0xffffffff80200000
start_pfn == 0x20cf8
The va going into above loop is 0xffffffffc0cf5000. This is L3 at 511 which
is NULL and so bad things happening.
I'm still trying to figure where the initial PTEs are being setup, I
don't see in hypervisor, my fear is libxc, or worse python :)....
Could the fix be made in the loop above the above mentioned loop in the
function where it's ensuring init mappings cover kernel+tables to check
for pud also?
/* Ensure init mappings cover kernel text/data and initial
* tables. */
while (va < (__START_KERNEL_map
+ (start_pfn << PAGE_SHIFT)
+ tables_space)) {
check for pud_none() <======= ????????????
pmd = (pmd_t *)&page[pmd_index(va)];
if (pmd_none(*pmd)) {
pte_page = alloc_static_page(&phys);
................
Thanks a lot,
Mukesh
next reply other threads:[~2009-02-17 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 4:00 Mukesh Rathor [this message]
2009-02-17 8:02 ` PV domU with 255GB boot failure Keir Fraser
2009-02-17 9:29 ` venkatesh k
2009-02-17 11:56 ` Please do not post homework questions to this mailing list Ian Jackson
2009-02-18 13:08 ` PV domU with 255GB boot failure Mark Williamson
2009-02-18 3:39 ` Mukesh Rathor
2009-02-18 8:21 ` Keir Fraser
2009-02-18 12:21 ` Jan Beulich
2009-02-18 19:12 ` Mukesh Rathor
2009-02-19 7:49 ` Jan Beulich
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=499A3669.6020605@oracle.com \
--to=mukesh.rathor@oracle.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.