From: Andrew Jones <drjones@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: Ubuntu 10.04 stuck in detect_extended_topology()
Date: Fri, 02 Jul 2010 15:48:36 +0200 [thread overview]
Message-ID: <4C2DEE34.7030507@redhat.com> (raw)
In-Reply-To: <4C1037AB.2000209@goop.org>
On 06/10/2010 02:54 AM, Jeremy Fitzhardinge wrote:
> On 06/09/2010 05:29 PM, AP Xen wrote:
>> 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?
>>
>
> Yes, or you could set 0:eax to some low number to just completely
> disable the whole leaf.
>
>
>> 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.
>>
>
> If not, I'd file a bug against RHEL Xen.
Just found this thread catching up on old email.
Right, there's no configurable cpuid masking support. However, RHEL 5.5
(s/RHEL/CentOS/) masks ext. topo.
Drew
prev parent reply other threads:[~2010-07-02 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 21:55 Ubuntu 10.04 stuck in detect_extended_topology() AP Xen
2010-06-09 22:41 ` 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 [this message]
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=4C2DEE34.7030507@redhat.com \
--to=drjones@redhat.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).