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

Re: [Xen-API] CloudLinux on Xen

To: brooks@xxxxxxxxxxx
Subject: Re: [Xen-API] CloudLinux on Xen
From: R J <torushikeshj@xxxxxxxxx>
Date: Mon, 24 Oct 2011 22:57:20 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Oct 2011 10:27:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WVc5nveXfUEuSFp5nhvsftS8zEKrj/YFjo8lDaYORfs=; b=dv/CrFpNYcdA37y7Nnm3eyU0Z7sHlKhSVOIB/nqGvRG1+p91OLhcO5qZG4dKEvLp0r G9wmIx2B3eBjy+Yd4sJ1qmzumzpASq/KHQokhaJjrxHpTEIRq0I0HXy7a+yUmOTUvETa TrIDeuI5DbG8xoh/+xFkBtMq1rXvjGyHD8VfU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.LRH.2.02.1110240952500.2904@xxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <CAO14VsPQO3LmevkV9xa6P=aXHCGrmnG9vURM4soiJEykeciX0Q@xxxxxxxxxxxxxx> <alpine.LRH.2.02.1110240921460.2904@xxxxxxxxxxxxxx> <CAO14VsOL+JHGJ+-EyEkBm+-xornWRkn-52f+DBfP2QXxhLwh-A@xxxxxxxxxxxxxx> <alpine.LRH.2.02.1110240952500.2904@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Yes its strange.

I have XCP1 with following version of CloudLinux Kernel.
Please see if the same issue replicates at your environment.

[root@centos ~]# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/xvda3
#          initrd /initrd-version.img
#boot=/dev/xvda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CloudLinux Server (2.6.18-374.3.1.el5.lve0.8.44xen)
    root (hd0,0)
    kernel /vmlinuz-2.6.18-374.3.1.el5.lve0.8.44xen ro root=LABEL=/ console=xvc0
    initrd /initrd-2.6.18-374.3.1.el5.lve0.8.44xen.img
title CentOS (2.6.18-194.el5xen)
    root (hd0,0)
    kernel /vmlinuz-2.6.18-194.el5xen ro root=LABEL=/ console=xvc0
    initrd /initrd-2.6.18-194.el5xen.img


I'm using CloudLinux 5 on XCP1 and not 1.1
On default xen kernel it boots and runs fine on allocated vCPUs but 2.6.18-374.3.1.el5.lve0.8.44xen kernel is making things strange.


Regards,
R J

On Mon, Oct 24, 2011 at 10:34 PM, <brooks@xxxxxxxxxxx> wrote:

On Mon, 24 Oct 2011, R J wrote:

Hi Brooks,

Thanks for the reply.
I have X5650 node with 24 CPUs. This is Dual Socket Hexacore machine.

I used XenCenter to monitor the node and it showed 2 vCPUs for that DomU. I
rechecked it with vm-param-list, it showed 2.
When I checked /proc/cpuinfo in DomU, it shows 32.

That's (very) strange.  I have a similar environment set up and running with CloudLinux 5 under XenServer 5.5 and all of the CPU/VCPU mapping is working as expected.  I'm currently testing XCP 1.1 but have yet to bring up a CL VM on it.  Are you using CL 5 or CL 6, and is this XCP 1.0 or 1.1?
Did you happen to check /proc/cpuinfo before applying the CL RPMs?

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api