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-users

Re: [Xen-devel] Re: [Xen-users] XCP - Maximum CPU cores

To: Outback Dingo <outbackdingo@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] XCP - Maximum CPU cores
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Wed, 13 Apr 2011 05:34:22 +0000
Cc: Eduardo Bragatto <eduardo@xxxxxxxxxxxx>, Dustin Marquess <dmarquess@xxxxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 12 Apr 2011 22:35:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=4k0jyCnqoJEvxfbz6JZNBVTFE8p9om2WZuuzpo58v9g=; b=AcUvzxDPTKDvQ4KNfGfrKFjlpXSf5GEt9KoI2Cbf4zWFcjVdQ4dkvQC0x8qR+jN+Sc bOAMjz7/ZZ3RFGRzODaZTtF43J302cWBNhoCy8O9QcmQAAO1qSSlDRnWzYt+Wm0LH2jj 68eqgQ7NbMSEd4qG3DPsN/bIUTyN+0Y7h6Ej4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=n5EzIX3uF8dsBoSeW9YYsxMbIf0wlsEISSbGum2Cxx08dPSwaU3cYGsQL2QrtxZrtR UjTQssaX5TZNX5DbFI+GipfQ/x74c/pjSJjz3t6tr9nMzsxDlvRsiw2hB2otXB5sya8w /T6s8sWQupCJryl4OegN284IeOLlxAN+KN3Qw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTikUAMc4soHigiZGFsPm5Bqu0cQQMQ@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinZLvkqO14F-NoQxTr1dPcCjekVR_yGPm9rnd=Y@xxxxxxxxxxxxxx> <AANLkTinyiiyNpWE_p1Ly_zN6Zm3NM8VgE5kYupGdwNHc@xxxxxxxxxxxxxx> <000601cbddb9$dfb265d0$9f173170$@com> <AANLkTikJOigU=B0L+km_q0y2cLiAxz079BPGffYbvJX+@xxxxxxxxxxxxxx> <000c01cbddbf$3af974b0$b0ec5e10$@com> <AANLkTikg0FSitJPCQFh3JUca6hGwBpZLdh3b5szBXZAc@xxxxxxxxxxxxxx> <AANLkTimenK8bfGb2RAcoG1w+A0_9YYTi19TVVVDYeSWd@xxxxxxxxxxxxxx> <003101cbddc9$9395e3b0$bac1ab10$@com> <AANLkTindY3xF8RdMq+0jcbmBdz7YahfyD6EOLusP=Qez@xxxxxxxxxxxxxx> <AANLkTinycT0+LeVx=LQ6-R_zo_ugt6+9H9Xu=bHSKgdX@xxxxxxxxxxxxxx> <AANLkTinS38EiyYcoff40AJoNp53YKNBJaUXWSWqfErp5@xxxxxxxxxxxxxx> <F9937284-686B-4BF1-9146-7DA1C25CEBC8@xxxxxxxxxxxx> <AANLkTikZ0vOZDh5wkeS+g7nU7iLZExL0bTMkLoESvQbH@xxxxxxxxxxxxxx> <BANLkTikUAMc4soHigiZGFsPm5Bqu0cQQMQ@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
adding xen-api to the CC

BCC xen-devel

On Wed, Apr 13, 2011 at 3:24 AM, Outback Dingo <outbackdingo@xxxxxxxxx> wrote:
> On Thu, Mar 31, 2011 at 9:51 AM, Dustin Marquess <dmarquess@xxxxxxxxx>
> wrote:
>>
>> No.  The hypervisor itself is still 64-bit.
>>
>> -Dustin
>>
>> On Thu, Mar 31, 2011 at 6:35 AM, Eduardo Bragatto <eduardo@xxxxxxxxxxxx>
>> wrote:
>> > 32bit kernel? Does that mean XCP can only run 32bit guests?
>> >
>> > -Eduardo
>> >
>> > On Mar 31, 2011, at 1:20 AM, Dustin Marquess wrote:
>> >
>> >> It's based on 32-bit CentOS 5.5 + a custom kernel.
>> >>
>> >> -Dustin
>> >>
>> >> On Wed, Mar 30, 2011 at 8:15 PM, Outback Dingo <outbackdingo@xxxxxxxxx>
>> >> wrote:
>> >>>
>> >>> On Tue, Mar 8, 2011 at 2:51 PM, Todd Deshane <todd.deshane@xxxxxxx>
>> >>> wrote:
>> >>>>
>> >>>> On Tue, Mar 8, 2011 at 2:46 PM, AP Xen <apxeng@xxxxxxxxx> wrote:
>> >>>>>
>> >>>>> Technically, it is possible as XCP is open source. You would have to
>> >>>>> download the source ISO and rebuild Xen with nr_phys_cpus=128.
>> >>>>> Trying
>> >>>>> to
>> >>>>> replace Xen in XCP with the Xen 4.x might be more difficult.
>
>
> Ok, well heres an update, i did succesfully build/install xen-4.1 on XCP,
> and got the system to reboot, issue is now
> that the api seems to be completely out of whack..... and following
> http://wiki.xensource.com/xenwiki/XCP_Building_Instructions
> plainly fails with
> make
> omake phase1
> *** omake: reading OMakefiles
> *** omake: finished reading OMakefiles (0.17 sec)
> - build ocaml/util util_inventory.o
> + ocamlfind ocamlopt -package stdext,log -g -dtypes -thread -warn-error
> +a-4-6-9-27-28-29 -ccopt -fPIC -I +ocamldoc -c util_inventory.ml
> File "util_inventory.ml", line 20, characters 11-25:
> Error: Unbound module Debug.Debugger
> *** omake: 186/329 targets are up to date
> *** omake: failed (0.23 sec, 0/14 scans, 1/15 rules, 1/313 digests)
> *** omake: targets were not rebuilt because of errors:
>    ocaml/util/util_inventory.cmx
>       depends on: ocaml/util/util_inventory.ml
>    ocaml/util/util_inventory.o
>       depends on: ocaml/util/util_inventory.ml
> make: *** [all] Error 2
>
>
>>
>> >>>>>
>> >>>>
>> >>>> True it is open source and should be possible. You're going to want
>> >>>> to
>> >>>> make sure you use at least the 4.1 branch as it has better libxl
>> >>>> integration.
>> >>>
>> >>> Continuation of this conversation, XCP is based on RedHat correct ?
>> >>> which
>> >>> version?
>> >>> cat /etc/redhat-release
>> >>> XCP release 1.0.0-42052c (xcp)
>> >>> [root@xenserver-gvratnau ~]# uname -a
>> >>> Linux xenserver-gvratnau 2.6.32.12-0.7.1.xs1.0.0.311.170586xen #1 SMP
>> >>> Tue
>> >>> Feb 1 17:10:20 EST 2011 i686 i686 i386 GNU/Linux
>> >>> And if i use the source ISO im not getting version 4.1, so i need to
>> >>> natively build XEN 4.1 branch on some redhat release... then
>> >>> "remaster"
>> >>> the
>> >>> iso so its installable
>> >>> on multiple systems without the pain of manually doing this to say 20
>> >>> machines. I realize im way ahead of the curve here probably and am
>> >>> willing
>> >>> to suffer through
>> >>> some pain, and well report back, document the needed steps, however
>> >>> the
>> >>> remastering piece im sure someone can provide a clue to how this is
>> >>> done.
>> >>> _______________________________________________
>> >>> Xen-users mailing list
>> >>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> >>> http://lists.xensource.com/xen-users
>> >>>
>> >>
>> >> _______________________________________________
>> >> Xen-users mailing list
>> >> Xen-users@xxxxxxxxxxxxxxxxxxx
>> >> http://lists.xensource.com/xen-users
>> >
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/xen-users
>> >
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html

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

<Prev in Thread] Current Thread [Next in Thread>