[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Ubuntu 10.04 stuck in detect_extended_topology()

  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "AP Xen" <apxeng@xxxxxxxxx>
  • Date: Wed, 9 Jun 2010 11:01:03 -0700
  • Delivery-date: Wed, 09 Jun 2010 11:02:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=uSvt1+lrg26H52vmk8ciQnXRY3wbXafYp2rh7r81V5NapEJHSciWnBDZQK/ukO0ZXn 9q6u5826iS2CQlya+5Ij01be0UgjMTNbxGv4i9kcU5M6tBo4mgxQWZbj4Gy+onrjWZda PFqA20zLnr+B6HywQGvvO/jq+gRq2HNAKZ4A0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcsH/blOmgiLEprmQCuu+TR6lWgNTw==

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:


       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);





       } while (LEAFB_SUBTYPE(ecx) != INVALID_TYPE);



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.



Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.