From: "AP Xen" <apxeng@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Ubuntu 10.04 stuck in detect_extended_topology()
Date: Wed, 9 Jun 2010 14:55:17 -0700 [thread overview]
Message-ID: <006c01cb081e$74908320$5db18960$@com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]
I am running Xen packaged with CentOS 5.4 and trying to install Ubuntu 10.04
as an HVM guest.
xen_major : 3
xen_minor : 1
xen_extra : .2-164.11.1.el5
After sprinkling the kernel with printks, I am seeing that it is stuck in
the function detect_extended_topology() in the following loop:
<snip>
sub_index = 1;
do {
cpuid_count(0xb, sub_index, &eax, &ebx, &ecx, &edx);
printk("%s: after cpuid_count %d\n", __FUNCTION__, sub_index);
/*
* Check for the Core type in the implemented sub leaves.
*/
if (LEAFB_SUBTYPE(ecx) == CORE_TYPE) {
core_level_siblings = LEVEL_MAX_SIBLINGS(ebx);
core_plus_mask_width = BITS_SHIFT_NEXT_LEVEL(eax);
break;
}
sub_index++;
} while (LEAFB_SUBTYPE(ecx) != INVALID_TYPE);
<snip>
The ECX leaf subtype never returns CORE_TYPE or INVALID_TYPE. So think I
might be running in to a bug / quirk in the CPUID handling code in Xen
packaged with CentOS 5.4. Is there a work around for it? Maybe specifying
something in the cpuid option in the config file.
Thanks!
[-- Attachment #1.2: Type: text/html, Size: 8767 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-06-09 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 21:55 AP Xen [this message]
2010-06-09 22:41 ` Ubuntu 10.04 stuck in detect_extended_topology() Jeremy Fitzhardinge
2010-06-10 0:29 ` AP Xen
2010-06-10 0:54 ` Jeremy Fitzhardinge
2010-06-10 6:01 ` Pasi Kärkkäinen
2010-06-10 16:53 ` AP Xen
2010-07-02 13:48 ` Andrew Jones
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='006c01cb081e$74908320$5db18960$@com' \
--to=apxeng@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).