WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] RE: [Xen-users] Xen in a 32 way system
From: "Pablo Montesinos" <pablomontesinos@xxxxxxxxx>
Date: Thu, 1 Jun 2006 10:30:06 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Uros Trebec <uros.trebec@xxxxxxxxx>, "Petersson, Mats" <Mats.Petersson@xxxxxxx>, Ryan Harper <ryanh@xxxxxxxxxx>, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 01 Jun 2006 10:30:46 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=i8QKTlg0u03tkYTVx+IY0iA0kgCy91dMi3q2gNESjGatmACgspoDOrxXz4IU9dshGQjaawTa+xWQRA4f//KevTaonK9wAfa+rOLUGkjd52j2TG3pnfOwt0mMX1GVD8UQxUhu6lol1Qpm1BC2amap0hDjL7SEnf9nc+6ytMXgBao=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <a19e41a6b9be4202fdd5a28f4e1f907b@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <907625E08839C4409CE5768403633E0BA7FCD1@xxxxxxxxxxxxxxxxx> <a19e41a6b9be4202fdd5a28f4e1f907b@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
The reason why I wanted to use a 2.6.16 kernel is the following. When
I installed this morning the "vanilla unstable" version I downloaded,
it created only one kernel, 2.6.16.13-xen. I booted the system with
it, and it didn't work well because of some network card, but RHEL
acutally booted. I didnt check the output while it booted, but I
assumed that it was using all the cpus. So I reconfigured the kernel
with my kernel config, and I got the crash.

I am inserting some extra code in XEN to check how many cpus it is
seeing. But this is the first time I look into XEN's code, so I am
going very slow.

Thanks,
Pablo

On 6/1/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

On 1 Jun 2006, at 18:00, Petersson, Mats wrote:

> The line you have the BUG in is a VCPUOP_initialize, which ends up in
> .../xen/common/domain.c: do_vcpu_op(), where it does essentially the
> first thing is a check:
>       if ((vcpuid < 0) || (vcpuid >= MAX_VIRT_CPUS))
>               return -EINVAL;
>
> And I think this check will fail if vcpuid is 32, unless MAX_VIRT_CPUS
> is not the standard value in . RSI is 32 (0x20)

Our smpboot.c in Linux should only try to initialise context for cpus
in cpu_possible_map. And that map is initialised by querying Xen about
the state of each VCPU. So it's unclear how you can end up getting this
crash. Looks like it needs some more tracing added...

  -- Keir



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