[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Status of sedf?
At 07:33 AM 8/18/2005, Stephan Diestelhorst wrote: On Thursday 18 August 2005 03:36, Andy Lee wrote: > At 03:11 PM 8/17/2005, I wrote: > >Sorry to report that the patch didn't work. I applied the patch to my > >Xen-2.0-testing tree and copied xen/common/sched_sedf.c from > >Xen-unstable. When compiling xen, sched_sedf.c generated these types of > >errors: Outch. Now I see... For some reason (forgot to do 'hg add' ) sched_sedf.c wasn't included. You can't use the unstable one, as it has a different naming scheme. Attached is the patch, this time WITH sched_sedf.c Also missing is xen-2.0-testing.hg/tools/libxc/xc_sedf.c - but this time, I was able to use the xc_sedf.c from the unstable tree!!! :-) It compiles, but I encountered this problem: (Xen-2.0-testing) # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 251 0 r---- 14.1 Sarge 1 127 0 -b--- 3.1 9601 # xm sedf 1 0 0 0 1 128 Error: (22, 'Invalid argument') Last night, I also compiled xen-unstable to see how sedf works: (Xen-unstable) # xm sedf 1 0 0 0 1 128 Unexpected error: exceptions.TypeError Please report to xen-devel@xxxxxxxxxxxxxxxxxxx Traceback (most recent call last): File "/usr/sbin/xm", line 10, in ? main.main(sys.argv) File "/usr/lib/python/xen/xm/main.py", line 646, in main rc = cmd(args) File "/usr/lib/python/xen/xm/main.py", line 435, in xm_sedf server.xend_domain_cpu_sedf_set(dom, *v)TypeError: xend_domain_cpu_sedf_set() takes exactly 7 arguments (6 given) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |