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] [PATCH] Fix xm start command

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] Fix xm start command
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Wed, 24 Jan 2007 15:33:34 +0900
Delivery-date: Tue, 23 Jan 2007 22:33:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
Hi,

When I tested the xm start command, I found a small bug. 
It's not able to set scheduler parameters (cpu_weight and 
cpu_cap).

# xm new /xen/vm1.conf cpu_weight=512 cpu_cap=150
Using config file "/xen/vm1.conf".
# xm start vm1
# xm sched-credit -d vm1
Name                              ID Weight Cap
vm1                                1    256    0


I fixed it. Test result is as follows. 

# xm new /xen/vm1.conf cpu_weight=512 cpu_cap=150
Using config file "/xen/vm1.conf".
# xm start vm1
# xm sched-credit -d vm1
Name                              ID Weight Cap
vm1                                2    512  150

Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,
 Kan

Attachment: xm_start_weight_and_cap.patch
Description: Binary data

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