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

[Xen-devel] Unable to bring up x86_64 UP DomU on processor #32

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Unable to bring up x86_64 UP DomU on processor #32
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Fri, 21 Oct 2005 17:10:32 -0400
Delivery-date: Fri, 21 Oct 2005 21:07:49 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXWg99KZW7llr03Ti6ckEbkGDQv0Q==
Thread-topic: Unable to bring up x86_64 UP DomU on processor #32
I am running x86_64 Xen on an ES7000 with 32 logical processors. I am
trying to force a DomU to come up on CPU #32 by specifying "cpu=31" in
the DomU configuration file. "xm" gives me the following error message:

"Error: Error creating domain: signed integer is greater than maximum"

I am able to do "cpu=30" successfully.

Is this a bug? Should I be opening up a bug report?

BTW, this does NOT happen on x86_32 PAE.

Aravindh

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