* Ubuntu 10.04 stuck in detect_extended_topology()
@ 2010-06-09 21:55 AP Xen
2010-06-09 22:41 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 7+ messages in thread
From: AP Xen @ 2010-06-09 21:55 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]
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:
<snip>
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);
break;
}
sub_index++;
} while (LEAFB_SUBTYPE(ecx) != INVALID_TYPE);
<snip>
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.
Thanks!
[-- Attachment #1.2: Type: text/html, Size: 8767 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Ubuntu 10.04 stuck in detect_extended_topology()
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
0 siblings, 1 reply; 7+ messages in thread
From: Jeremy Fitzhardinge @ 2010-06-09 22:41 UTC (permalink / raw)
To: AP Xen; +Cc: xen-devel
On 06/09/2010 02:55 PM, AP Xen wrote:
>
> 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:
>
> <snip>
>
> 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);
>
> break;
>
> }
>
>
>
> sub_index++;
>
> } while (LEAFB_SUBTYPE(ecx) != INVALID_TYPE);
>
> <snip>
>
>
>
> 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.
J
^ permalink raw reply [flat|nested] 7+ messages in thread* RE: Ubuntu 10.04 stuck in detect_extended_topology()
2010-06-09 22:41 ` Jeremy Fitzhardinge
@ 2010-06-10 0:29 ` AP Xen
2010-06-10 0:54 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 7+ messages in thread
From: AP Xen @ 2010-06-10 0:29 UTC (permalink / raw)
To: 'Jeremy Fitzhardinge'; +Cc: xen-devel
> > 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ubuntu 10.04 stuck in detect_extended_topology()
2010-06-10 0:29 ` AP Xen
@ 2010-06-10 0:54 ` Jeremy Fitzhardinge
2010-06-10 6:01 ` Pasi Kärkkäinen
2010-07-02 13:48 ` Andrew Jones
0 siblings, 2 replies; 7+ messages in thread
From: Jeremy Fitzhardinge @ 2010-06-10 0:54 UTC (permalink / raw)
To: AP Xen; +Cc: xen-devel
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.
J
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Ubuntu 10.04 stuck in detect_extended_topology()
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
1 sibling, 1 reply; 7+ messages in thread
From: Pasi Kärkkäinen @ 2010-06-10 6:01 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: Ubuntu 10.04 stuck in detect_extended_topology()
2010-06-10 6:01 ` Pasi Kärkkäinen
@ 2010-06-10 16:53 ` AP Xen
0 siblings, 0 replies; 7+ messages in thread
From: AP Xen @ 2010-06-10 16:53 UTC (permalink / raw)
To: 'Pasi Kärkkäinen',
'Jeremy Fitzhardinge'
Cc: xen-devel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ubuntu 10.04 stuck in detect_extended_topology()
2010-06-10 0:54 ` Jeremy Fitzhardinge
2010-06-10 6:01 ` Pasi Kärkkäinen
@ 2010-07-02 13:48 ` Andrew Jones
1 sibling, 0 replies; 7+ messages in thread
From: Andrew Jones @ 2010-07-02 13:48 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2010-07-02 13:48 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).