similar to: [PATCH] small format changes in xm.1 to make sedf more readable

This is a resend on the patch from late last week as I haven''t seen it in the changelog yet. Comments welcomed if there is an issue with the patch. -Sean -- __________________________________________________________________ Sean Dague Mid-Hudson Valley sean at dague dot net Linux Users Group http://dague.net

My interest in icalendar is more on the ical generation side instead of the ical parsing side. As such, I did a bit of work on a tzinfo mixin that will generate the timezone rules based on the tzinfo gem. This lets you do the following: estart = DateTime.new(2008, 12, 29, 8, 0, 0) eend = DateTime.new(2008, 12, 29, 11, 0, 0) tstring = "America/Chicago" tz =

This patch changes the device destruction function to one that exists in in the XendDomainInfo class, instead of a non existent method. Signed-off-by: Sean Dague <sean@dague.net> Diffstat output: XendDomain.py | 2 +- 1 files changed, 1 insertion(+), 1 deletion(-) diff -r 41a74438bcba tools/python/xen/xend/XendDomain.py --- a/tools/python/xen/xend/XendDomain.py Fri Sep 9 18:36:48

The following patch adds a section for SHUTDOWN OPTIONS for the xmdomain.cfg man page. It documents the new set of options introduced over the last few weeks. Signed-off-by: Sean Dague <sean@dague.net> Diffstat output: xmdomain.cfg.pod.5 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 51 insertions(+) diff -r 8cc7ce549d00 docs/man/xmdomain.cfg.pod.5 ---

Starting about 2 weeks ago Xend has started to fall over a lot doing what should be normal actions, so much so that our xm-test suite more or less fails all the tests as it keeps apparently knocking over xend on relatively simple operations like create, and list. What is most bizarre now is this "no such process" error generated by Xend. Here is a segment of our xm-test results that

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

I downloaded the ics from http://www.thegreenerleithsocial.org/events/cleanup-the-cycle-path and tried to parse it in my rails app console: ?> cal_file = File.open("/tmp/Clean_up the Cycle Path-1.ics") => #<File:/tmp/Clean_up the Cycle Path-1.ics> >> cals = Icalendar.parse(cal_file) Icalendar::UnknownPropertyMethod: Unknown property type: website from

Hi, I''m currently trying to get icalendar packaged and into Fedora and EPEL, During this process I''ve noticed that you''re currently using Gem::manage_gems in the make Rakefile, this method was depecated in rubygems 1.3.0 them removed in rubygems 1.3.3. The attached patch updates the Rakefile replacing the method with the two require calls required. Mark -- Mark

--- xen-common-3.0.3-0/docs/man/xmdomain.cfg.pod.5 2006-11-02 16:45:36.000000000 +0000 +++ xen-common-3.0.3-0-cjac/docs/man/xmdomain.cfg.pod.5 2007-07-04 20:58:22.000000000 +0000 @@ -274,7 +274,16 @@ =item I<LVM Root> -FIXME: write me + kernel = '/boot/vmlinuz-2.6-xen' + ramdisk = '/boot/initrd.img-2.6.18-4-xen-686' + memory = '16' + root =

sched_sedf.c used o have its own mechanism for producing tracing-alike kind of information (domain block, wakeup, etc.). Nowadays, with an even not so high number of pCPUs/vCPUs, just trying to enable this makes the serial console completely unusable, produces tons of very hard to parse and interpreet logging and can easily livelock Dom0. Moreover, pretty much the same result this is struggling to

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

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:

Is there a way to setup cpu scheduling commands from inside the config file for a domU ? Or it can only be done after the domU has been started ? -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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,

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo xm create breezy -c Using config file "/etc/xen/breezy". Started domain breezy Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 SMP Thu Oct 13 14:56:20 NZDT 2005 kernel direct mapping tables upto 10000000 @ 568000-5ea000 Built 1 zonelists Kernel command line: root=/dev/sda1 ro 4 lockd.udpport=32768

Hi, Dan, This patch fixes strange behavior on IA64, that IDLE is scheduled more than Dom0 with default sEDF scheduler. The key point is reprogram_ac_timer at the end of ac_timer dispatcher, which programs local apic timer with expire of next ac_timer on x86. Higher precision lapic timer can trigger ac_timer more precisely than simply done in PIT interrupt handler. That works perfectly on x86

Anyone from this group in or around Hudson Valley NY? Looking for some local connections or groups to learn with and from. (thanks to Marnen Laibow-Koser for his techvalleyrb suggestion)

Xen patchbot -unstable wrote: > # HG changeset patch > # User emellor@leeni.uk.xensource.com > # Node ID da24df1ea484cf72dc9d367d52e828777e0e20cd > # Parent c1bb4eb565296bdb00aed84fcc877befbcebd8e9 > Improve error handling, in particular fixing the ProtocolError that is thrown > when a domain is specified by the user that does not exist. Added a few > error codes -- many

The Sieve plugin page of Wiki documentation (http://wiki.dovecot.org/LDA/Sieve?highlight=%28filter%29) says: "It's also not a good idea to build the plugin against self-compiled Dovecot sources, but then actually use a prebuilt binary package of Dovecot." Why isn't a good idea? Ciao, luigi -- / +--[Luigi Rosa]-- \ Every time you've heard someone say they saw a

I a have a problem resulting from a neat tool I developed through the use of the "root preexec" option: This is done in the [homes] section of smb.conf. I launch a shell script with the user name (%u) and machine name (%m). The shell calls a C program to check the users quota and returns a code as the percentage of quota used. Meanwhile, all output of the C program has been captured