From mboxrd@z Thu Jan 1 00:00:00 1970 From: "AP Xen" Subject: RE: Ubuntu 10.04 stuck in detect_extended_topology() Date: Wed, 9 Jun 2010 17:29:39 -0700 Message-ID: <007a01cb0834$052e8ed0$0f8bac70$@com> References: <006c01cb081e$74908320$5db18960$@com> <4C101896.8090608@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C101896.8090608@goop.org> Content-Language: en-us List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: 'Jeremy Fitzhardinge' Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > > 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. The host cpu type is "Intel(R) Xeon(R) CPU E5520 @ 2.27GHz" (x86_64). What should I specify in "cpuid=" in the config file? I tried the following: cpuid = [ '0xb:ebx=xxxxxxxxxxxxxxxx0000000000000000' ] Is that correct? However, it did not have any effect. I do not see any mention of it in xend.log. Maybe the version of Xen packaged with CentOS 5.4 not support the cpuid config option. xen_major : 3 xen_minor : 1 xen_extra : .2-164.11.1.el5 AP