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

[Xen-users] VCPU and CPU Manipulation

To: "xen-users list" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] VCPU and CPU Manipulation
From: "Omer Khalid" <Omer.Khalid@xxxxxxx>
Date: Mon, 6 Oct 2008 10:51:10 +0200
Delivery-date: Mon, 06 Oct 2008 01:51:51 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:x-google-sender-auth; bh=U/9LYFP4ui/YmpODuN+/uvqvCcWqaGf30f+etEqsr7Q=; b=NDye2A1fqcN0Uwr6yC+Kj6lppE9f9PDw8Hi2eO59NZZILazNGTY3ZxEsek2FDubPl3 UX6A+YCf+2TrZh/joSBRnCx88jipKOGfbDgpi94dgkkpRbsBrNbGMWkkM+20fsPUdrlk Xyy+Wyk4hQNWEcIW6QtAkxnymuS/exopoVfRI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=tiolv5V3+oAOLzaUsejtUJSkvmIZKsMFneTzL92z2noLPGkNRyhSHis7MYuqhWCcQv 2GyrD3rtt4F4jW+8rjkL0eSEagTddIxmF3YTHWfz6q2z2RP5U9UM+r85tcwnMs+XIsP7 xPb3mer4TynNrTBWjk9Z/sWADR4a8+/Ux2kQM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hi,

I have a dual core SMP machine ( in total 4 cores). I have been trying to set restrict vcpu/cpus for my domU to one core/one vpcu but it have not fully worked. As there are two commands "xm vcpu-set" and "xm vcpu-pin". By using these commands, i have observed that the sequence in which they are used plays a role. e.g. I have the following state in the beginning:

[root@lxb ~]# xm vcpu-list
Name         ID     VCPUs CPU   State Time(s)      CPU Affinity

====         ==     ===== ====  ==== ======     === =====
Domain-0    0       0          3        r--      5593.4        any cpu
Domain-0    0       1          1        -b-     15361.9      any cpu
Domain-0    0       2          0        -b-     10137.5      any cpu
Domain-0    0       3          -         --p     78.9           any cpu
test_lxb      20     0          2         -b-     21169.0     any cpu

What I want to achieve is that my domU (test_lxb) uses one VCPU pinned to one CPU. In the above state, both my domU and dom0 are using VCPU 0 (which is pinned to use either CPU 3 or 2.) After few "vcpu-set" and "vcpu-pin", I reach the following stage where dom0 is pinned to CPU 3 and domU (test_lxb) is pinned to CPU 2:

[root@lxb ~]# xm vcpu-list
Name ID VCPUs CPU State Time(s) CPU Affinity

Name         ID     VCPUs CPU   State Time(s)      CPU Affinity

====         ==     ===== ====  ==== ======     ========

Domain-0    0       0         3        r--      5600.4            3
Domain-0    0       1         3        -b-     15372.5           3
Domain-0    0       2         3        -b-     10140.0           3
Domain-0    0       3         -         --p     78.9                3
test_lxb      20     0         2         -b-     21169.5           2 

But domU is still using VCPU 0 which is also used by my domU; now i would like to restrict VCPU 0 to CPU 2 only for domU only...I am wondering how to achieve this last mile?

Any ideas? Thanks for you help in advance!

Regards
--
Omer

-------------------------------------------------------
CERN -- European Organization for Nuclear
Research, IT Department, CH-1211,
Geneva 23, Switzerland


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>