similar to: [PATCH] xl: fix sedf parameters checking

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

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

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

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

Here are some patches I compiled to get sedf_get to the XendClient API... sadly, however, the current xc frontend is missing a variable (weight) and needed to be edited. Below are my "homemade" patches (I did this since my code base is EXTREMELY old... however the code is still valid) tools/python/xen/lowlevel/xc/xc.c line 766 static PyObject *pyxc_sedf_domain_get(PyObject *self,

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 >

Hi all, I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I''ve just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported". I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generating a fast interrupt? Regards.

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

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

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

Hi Ian-s, Two small patches for OSSTest. The first one turns on compiling the Linux modules for MegaRAID SAS, needed for the ultralisk machine in the Cambridge lab. The second adds an entry in the README file about the RebootTimeExtra host property, which I also needed to use for ulttralisk, as scrubbing 368GB of RAM really takes a lot! git://xenbits.xen.org/people/dariof/osstest.git misc Let

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, thanks for your response. i cleaned that above one and installed in this following steps: * sudo apt-get install gcc make pkg-config libxml2-dev libgnutils-dev libdevmapper-dev libcurl4-gnutls-dev python-dev libpciaccess-dev libxen-dev libnl-dev * ./configure = --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-xen=yes --with-libxl=yes * make * make install now i am getting the

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

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