similar to: Performance of Xen VCPU Scheduling

Hello, This small series deals with some weirdness in the mechanism with which the credit scheduler choses what PCPU to tickle upon a VCPU wake-up. Details are available in the changelog of the first patch. The new approach has been extensively benchmarked and proved itself either beneficial or harmless. That means it does not introduce any significant amount of overhead and/or performances

Hi all, This is the second take of a patch that I submitted some time ago for allowing specifying vcpu pinning taking NUMA nodes into account. IOW, something like this: * "nodes:0-3": all pCPUs of nodes 0,1,2,3;  * "nodes:0-3,^node:2": all pCPUS of nodes 0,1,3;  * "1,nodes:1-2,^6": pCPU 1 plus all pCPUs of nodes 1,2    but not pCPU 6; v1 was a single patch, this is

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

About rationale, usage and (some small bits of) API. Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> --- Changes from v7: * avoid referring to 4.2 release as "upcoming". * libxl placement disabling key explicitly mentioned. * Limit of max 16 NUMA nodes explicitly mentioned. Changes from v6: * text updated to

in _csched_cpu_pick(), as not doing so may result in the domain''s node-affinity mask (as retrieved by csched_balance_cpumask() ) and online mask (as retrieved by cpupool_scheduler_cpumask() ) having an empty intersection. Therefore, when attempting a node-affinity load balancing step and running this: ... /* Pick an online CPU from the proper affinity mask */

On Mon, 2012-01-23 at 18:21 +0000, Dario Faggioli wrote: > Allow for "^<cpuid>" syntax while specifying the pCPUs list > during a vcpu-pin. This enables doing the following: > > xl vcpu-pin 1 1 0-4,^2 > > and achieving: > > xl vcpu-list > Name ID VCPU CPU State Time(s) CPU Affinity > ... > Squeeze_pv

On Wed, 2012-01-25 at 14:35 +0000, Dario Faggioli wrote: > Allow for "^<cpuid>" syntax while specifying the pCPUs list > during a vcpu-pin. This enables doing the following: > > xl vcpu-pin 1 1 0-4,^2 > > and achieving: > > xl vcpu-list > Name ID VCPU CPU State Time(s) CPU Affinity > ... > Squeeze_pv

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

Hi all (and Mr. Dunlap in particular), I have a question about the credit (and ultimately credit2) scheduler that I hope you can help me with. I have read the white paper "Scheduler development update" and as much material on the credit scheduler as I can find, but I am still not completely clear on how I should think about the cap. Example scenario: Server hardware: 2

flight 13439 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13439/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl-qemuu-winxpsp3 9 guest-localmigrate fail REGR. vs. 13379 test-amd64-amd64-xl-qemuu-win7-amd64 9 guest-localmigrate fail REGR. vs. 13376 Regressions which are regarded as

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding

On Wed, Nov 23, 2011 at 2:55 PM, Dario Faggioli <raistlin@linux.it> wrote: > Hi everyone, > > This series changes how locks are dealt with while adjusting domains'' > scheduling parameters. > > I''ve done and am still doing tests for credit and credit2, and it''s > surviving to all I threw at it up to now. Unfortunately, I can''t test >

Hello everyone, Reposting with after having applied the (minor) fixes suggested by Wei and Jan. Allen, if you can tell us what you think about this, or suggest someone else to ask some feedback to, if you''re no longer involved with VT-d, that would be great! :-) -- As already discussed here [1], dealing with IOMMU faults in interrupt context may cause nasty things to happen, up to

Hello, I have asked this question in Xen-users mailing list too. But since it involves compiling from source, I realised asking this here makes more sense. Please forgive me for the spam. I am relatively new to Xen and need help compiling and installing Xen from source. Using some tutorials online, I have got Xen working with the ''yum install xen'' method. I used virt-manager

Hi all, These days I installed xen 4.3 unstable from source and recompiled qemu upstream with spice support. After xl create , the windows domU started successfully and spice client can visit the VDI. However, it display blue screen before entering the windows welcome screen. Is it a bug in current upstream qemu support? My domU configuration file is: builder =

flight 13339 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13339/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-sedf-pin 9 guest-start fail REGR. vs. 13025 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf 9 guest-start

Hi, list, A VMM provides a VMCS for each VM. How does the VMM assign system resources for each VM? For example, in a multi-core environment, how can I enable the VMM to run, say, on a two-core intel''s processor while I am able to force a VM to execute only on a specific core upon initializing the Guest OS ? that is to say, how I can assure the VM to believe that there is only one physical

hi i want to install libvirt-1.1.2 in xen -4.2.1. i installed int he following manner: 1. downloaded source from libvirt/org (libvirt-1.1.2) 2. untarred & run ./configure --with-xen=yes --with-libxl=yes 3. then make and make install. i also enabled the (xend-unix-server yes) in xend config file. i run libvirtd -v and getting the followning error: root@boss[libexec]#libvirtd -v

hi i want to install libvirt-1.1.2 in xen -4.2.1. i installed int he following manner: 1. downloaded source from libvirt/org (libvirt-1.1.2) 2. untarred & run ./configure --with-xen=yes --with-libxl=yes 3. then make and make install. i also enabled the (xend-unix-server yes) in xend config file. i run libvirtd -v and getting the followning error: root@boss[libexec]#libvirtd -v