similar to: (xm sched-credit) Error: cap is out of range

Currently with the credit scheduler, cpu_weight cannot be assigned to guest domains at boot time.(it can be set with xm sched-weight after booting) This patch allows CPU weight, and CAP to be set by the Xen configuration files. Specification: The following can be added to the Xen configuration files. 1.CPU WEIGHT [OPTIONAL] cpu_weight = cpu weight value -sets the cpu time ratio to be

On a 8 Core system only dom0 can set cap > 100 and vcpus > 1. On a domU ''xm sched-credit -d <domU> -c 200'' says "Error: cap is out of range". Vcpu cannot be set higher than 1 - regardless of boot/config/command line. Low performance is equivalent to the cap setting. See ''xm list --long'': (domain (domid 0) (uuid

Hi Everyone, How can I make use of xm sched-credit in a VPS hosting environment? Can I use "xm sched-credit -d <domain>" in a script at system startup, or does this have to be run after the respective guest has been started? Also, what happens when the guest is shutdown then restarted, or rebooted? Do I need to run that command again? If so, how would I automate this process?

Hi all, I''ve a linux dom0, a dom1 winxp sp2 (WinXP) and another winxp sp2 with 2 vcpu (WinXP_02) Dom2 uses all the dom0 idle: I mean this vm uses too much resources, it seems something wrong in configuration. This is strange because the other win xp uses very few resources I''ll attach some useful output.. Suggestions? (domain (domid 4) (on_crash restart) (uuid

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, Is there any specific good weight and cap value for Dom-0 which keep more stable the Dom-0? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hi Everyone, What''s the parameter in the DomU config file to cap the CPU on the domain? I tried using "cap = 20". While the VM booted ok, doing a "xm sched-credit -d </domain/>" showed the cap as being 0 Any ideas? Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, This patch fixes the Bug:835 issue. # xm create /home/kanno/smp-domU.conf cpu_weight=512 cpu_cap=150 Using config file "/home/kanno/smp-domU.conf". Started domain vm1-smp # xm sched-credit -d vm1-smp {''cap'': 150, ''weight'': 512} Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan

Add "xl domid" command, a clone of "xm domid". Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com> diff -r ccae861f52f7 -r 1d00cee69621 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Thu May 06 11:59:55 2010 +0100 +++ b/tools/libxl/xl_cmdimpl.c Fri May 07 19:35:40 2010 +0800 @@ -1221,6 +1221,9 @@ printf(" -d DOMAIN, --domain=DOMAIN Domain to

Hi all, The xen documentation at http://wiki.xensource.com/xenwiki/CreditSchedulerstates that the max weight you can set for a domU is 65535. To verify this I decided to try setting 65535 to my dom0 which had no domUs running at the time. I was unable to set a weight of 65535. The server is a duel quad core (8 cores) with 32GB RAM running Centos 5.4/xen-3.0.3-94.el5_4.3 . The maximum weight I was

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

Modified function runq_candidate in the credit 2 scheduler to have it consider hard and soft affinity when choosing the next vCPU from the run queue to run on the given pCPU. Function now chooses the vCPU with the most credit that has hard affinity and maybe soft affinity for the given pCPU. If it does not have soft affinity and there is another vCPU that prefers to run on the given pCPU, then as

Hi! I`m using xen 3.0.2 on a Debian Sarge 3,1 (XEON machine)! By default my scheduler is "sedf", ok?! I would like to change it to the "credit"! I tried to set the parameter "sched=credit" in my grub config, but when I try to use the command "xm sched-credit -d <domain>" and others, it doesn`t work! But if I try "xm sched-sedf -l" it

Hi, I have Xen (unstable) on two Debian Sarge 2.4.27 systems, one of which is an nfs server and the other the nfs client. I am trying to set up NFS root so that I can live migrate my domains from one to another. My /etc/exports on N1(10.5.144.29) /myfs1/foo 10.5.144.27(rw,sync,no_root_squash) 10.5.144.29(rw,sync,no_root_squash) 10.5.144.30(rw,sync,no_root_squash) My /hosts.allow on N1

Hi, I don''t want to hijack this thread. But as I lately posted a question which mainly was about weight and cap and this fits in perfectly (and also you seem to be an expert here), I repeat it below. In the meantime I saw an academic article Ludmilla Cherkasova et al. from which I understood that you have to careful that a Dom0 doesn''t get too much weight, as otherwise

This patch -Displays[1] current parameters for running domains ala xm list -Allow users to set[2] one or more parameters[3] without having to provide values for parameters they do not wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for

Implements tool interfaces for scheduling domains. libxenctrl, xm, and xend. signed-off-by: Mike D. Day <ncmike@us.ibm.com> -- libxc/xc_domain.c | 85 +++++++++++++++++++++++++++++++++--- libxc/xenctrl.h | 43 ++++++++++++++++-- python/xen/xend/XendDomain.py | 78 +++++++++++++++++++++++++++++++++ python/xen/xend/server/SrvDomain.py |

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

Hello, I''m using the following configuration on 8 different servers: xen 4.1.2 from opensuse 12.1 with Kernel 3.1.10-1.9-xen AMD Phenom(tm) II X6 1075T 8GB ram Dom0 : 1GB memory and 2 vcpus on core 0 (via boot option dom0_mem=1024M dom0_max_vcpus=2) DomU : 1 PV guest (opensuse12.1) 1GB memory 2 vcpus on core 1 to 5 1 PV guest (opensuse12.1) 1GB memory 3 vcpus on core 1 to 5