From: "AP Xen" <apxeng@gmail.com>
To: "'Pasi Kärkkäinen'" <pasik@iki.fi>,
"'Jeremy Fitzhardinge'" <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: RE: Ubuntu 10.04 stuck in detect_extended_topology()
Date: Thu, 10 Jun 2010 09:53:48 -0700 [thread overview]
Message-ID: <008601cb08bd$8281b1d0$87851570$@com> (raw)
In-Reply-To: <20100610060142.GH17817@reaktio.net>
This really blows :( But it looks like a good excuse to move to Xen4!
Thanks,
AP
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Wednesday, June 09, 2010 11:02 PM
> To: Jeremy Fitzhardinge
> Cc: AP Xen; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Ubuntu 10.04 stuck in
> detect_extended_topology()
>
> On Wed, Jun 09, 2010 at 05:54:03PM -0700, 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.
> >
>
> I already did that some time ago :)
> https://bugzilla.redhat.com/show_bug.cgi?id=525873
>
> You could re-open the bug of course..
>
> -- Pasi
next prev parent reply other threads:[~2010-06-10 16:53 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 [this message]
2010-07-02 13:48 ` Andrew Jones
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='008601cb08bd$8281b1d0$87851570$@com' \
--to=apxeng@gmail.com \
--cc=jeremy@goop.org \
--cc=pasik@iki.fi \
--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).