WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Ubuntu 10.04 stuck in detect_extended_topology()

To: AP Xen <apxeng@xxxxxxxxx>
Subject: Re: [Xen-devel] Ubuntu 10.04 stuck in detect_extended_topology()
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 09 Jun 2010 15:41:26 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jun 2010 15:43:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <006c01cb081e$74908320$5db18960$@com>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <006c01cb081e$74908320$5db18960$@com>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
On 06/09/2010 02:55 PM, AP Xen wrote:
>
> 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.
>

What's the host cpu type?  You should be able to completely disable the
extended topology leaf (0xb) with the cpuid= directive in the config file.

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel