similar to: How to change the scheduler? (credit)

Hi All , I am using older xen version xen-3.0.2 which supports BVT and SEDF scheduler I want to add credit and boost credit scheduler support in xen-3.0.2 . Please let me know if any (Credit scheduler) patch is available for xen-3.0.2 Thanks, Akhilesh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

Hi, I am using Xen 4.2.3 installed on an Intel Atom with a Debian Dom0 and 3 Debian domU''s installed. I am trying to run some benchmarks using the Arinc653 scheduler. I have edited my grub options to boot with ''maxcpus=1 sched=arinc653'' options. I can boot the dom0 and verify that the scheduler is enabled. However when I xl create, the VM is created but I cannot

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 list, I''m using xen 3.0.0 and wonder how to obtain the 6 DOMU scheduling parameters from my DOM0 domain. Sort opposite of the sched-sedf xm sub-command Can someone help me ? Pierre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

As discussed in a previous e-mail, this patch series implements yield for the credit scheduler. This allows a VM to actually yield (give up the cpu to another VM) when it wants to. This has been shown to be effective when used in the spinlock code to avoid wasting time spinning when another vcpu is not currently scheduled. _______________________________________________ Xen-devel mailing list

9d1fd58ff602 was bogous in not letting a new domain being created if its scheduling parameters --when running under the sedf scheduler-- were not fully specified, making creation fail like in this example here below: 2012-06-16 07:37:47 Z executing ssh ... root@10.80.248.105 xl create /etc/xen/debian.guest.osstest.cfg libxl: error: libxl.c:3619:sched_sedf_domain_set: setting domain sched sedf:

Hi, Sorry to insist, but I would really like to be able to use Xen and my zaptel hardware all together in Dom0. I was just wondering if the 3.1 release could contain some changes compared to 3.0.4 related to IRQ handling or scheduling that could workout my problem. Thanks, François. ---- I actually first asked to asterisk mailing lists, and a few persons told me that it was Xen''s

When using sedf scheduler in a cpupool the system might panic when setting sedf scheduling parameters for a domain. Signed-off-by: juergen.gross@ts.fujitsu.com 1 file changed, 4 insertions(+) xen/common/sched_sedf.c | 4 ++++ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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?

Hey George, I was wondering if you could explain in simple terms how the scheduler would handle per-physical CPU when there are say 16 guests (each guest is using one VCPU), 32 physical CPUs and dom0 is not restricted to any CPUs. Would the scheduler per physical CPU schedule: guest, dom0, guest, dom0, and so on; or would it be more random? (I assume that both guest and dom0 would do a hypercall

I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler

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

We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Cannot boot Four VMX at same time on IA32 host - Cannot boot Windows XP SP1/SP2 on IA32e host - Create IA32-PAE VMX on IA32e host will make VMX kernel panic - Create IA32 VMX on IA32e host will make VMX hang - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: -

Prevent xl from doing any operation if xend daemon is running. That prevents bugs that happened when xl and xend raced to close a domain. Changes since v1: * Add documentation to xl man page. * Permit the execution of commands that don''t modify anything. * Indent error message. Cc: george.dunlap@eu.citrix.com Cc: ian.jackson@eu.citrix.com Signed-off-by: Roger Pau Monne

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 |