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

[Xen-API] Can Dom0 use more than one vcpu?

To: xen-api <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] Can Dom0 use more than one vcpu?
From: Fabio Kung <fabio.kung@xxxxxxxxx>
Date: Thu, 8 Apr 2010 21:53:00 -0300
Delivery-date: Thu, 08 Apr 2010 17:53:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:received :message-id:subject:to:content-type; bh=o0QEo4fjEZTBRWBvTtRFrz/AMCcGHlOjfA8CWO0PMOA=; b=xc85KeeF+VxmynuVO20JBtyX5Z0rq1YfFoIAQ0ztrguyCVhUs/tTQXD+EhtpPAWyYL WDtKnahii3gmnztNq67WYqQY3xD86cGKTZFfWpZM5xSjntDd9C3uDWfDK+EtdijUi+Lr ZhNR8PgA1FoQlpCh8xMuI51NH6nkoaPvWIW7E=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=s+Ka4DvC7oESz1zNHtEgn0kl19yJl8LobNzVyBeP1BrUR5DlK1c7U99FZU7u5g216H qHaBYUeOPhpQrz0qHJnS4RjiYHWgdHuBMLVFy0cNBG7UZmFU+OeUOB2Mnui7ffTmLeY5 3aSnIwY8LdcvjFt7utmz1jkd9RxOKMubIxgjM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

I know that XenSource allows us to configure how much memory and how many vcpus are available to the Domain0 through kernel boot parameters (dom0_mem and dom0_max_vcpus). XCP is underlying using XenSource, then these settings should also work with XCP.

I'm trying to specify these boot parameters in the /boot/extlinux.conf file of my Domain0 VMs (Control Domains):

# /boot/exlinux.conf
# ...
label xe
  # XenServer
  append /boot/xen.gz dom0_max_vcpus=4 dom0_mem=752M lowmem_emergency_pool=16M crashkernel=64M@32M ...


The dom0_mem works just fine. My problem is with the dom0_max_vcpus boot parameter, which apparently isn't working. After setting this boot parameter, I also tried to set the number of vcpus of my Control Domains with xapi:

xe vm-param-set VCPUs-at-startup=4 uuid=<ControlDomainUUID>
xe vm-param-set VCPUs-max=4 uuid=<ControlDomainUUID>

None of them worked. My domain0 is still seeing only one vcpu. The strange thing is that XenSource's dom0_mem boot parameter did work as expected, but domain0_max_vcpus didn't.

Does someone know if XCP/XenServer is somewhere locking the number of Domain0 vCPUs to only one? Should I try something else?

My main issue is that I have a (very) large number of Networks and VLANs active inside my XCP pools. And because of that, the xapi process in all hosts (control domains) constantly hits 100% of cpu usage and all XCP operations are very slow. Pools may take something close to 3 hours just to boot, because XCP hosts recreate and synchronize all networks and vlans right after boot.

Setting the cpu priority of my control domains to higher values already helped, but I still have many unused cores in my physical machines. Being able to use them in my busy Domain0s would be very good.

Cheers,

-- Fabio Kung
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>