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

To:	"'Jeremy Fitzhardinge'" <jeremy@xxxxxxxx>
Subject:	RE: [Xen-devel] Ubuntu 10.04 stuck in detect_extended_topology()
From:	"AP Xen" <apxeng@xxxxxxxxx>
Date:	Wed, 9 Jun 2010 17:29:39 -0700
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Wed, 09 Jun 2010 17:30:41 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=mmCfNJVFtz4K+0iX7xxctX9aNmbxMRF9icldEB37cCw=; b=pav0zIFA8CIZ/AXV4ahEEMp7End88lAciFZQIBcL8BT4PWAxDlOS2pUMpswHjFpiul 4YMOmCMNs/Prtdcoi6O2DeCYbtrEvu49rz4aooFHpo081PSAiPajBGya23drofsE2uc/ 0svFNSQbJFMdK8FUhsJtEeOIshbVnFvLMVFAY=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=qbHdow1ApCqh/iQ3S2QU8pJ7R/E2HlUkdIMkXLsk1Lvi2GDEBD6JCrUYlm+6zWPuNp SaqmjaWplxEwy4Tqhu+8CcIz/WDZr952ImuHf/bRmqXRYu0znuYQdwOqN/a5xtAYGUH9 Qt7vhoo7mj0NVVykUYDmgdhiCn+Ru+pQ7CJrg=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<4C101896.8090608@xxxxxxxx>
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> <4C101896.8090608@xxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcsIJPAVpAErdh82SN+RV9Q4Oz/CQgACrscg

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


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

WARNING - OLD ARCHIVES

xen-devel

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