Dear All, I want to run the credit scheduler, however I guess it has not been incorporated into the 3.0.2 version. I tried installing the unstable version however that is giving me huge problems with respect to detection of my hard disk! I have no idea how to fix that. Is there any patch for 3.0.2 version to run the credit scheduler in it! I will be greatful if anyone could provide any pointers, I desperately need to get it working for my project! Regards, Hardeep _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear All, I want to run the credit scheduler, however I guess it has not been incorporated into the 3.0.2 version. I tried installing the unstable version however that is giving me huge problems with respect to detection of my hard disk! I have no idea how to fix that. Is there any patch for 3.0.2 version to run the credit scheduler in it! I will be greatful if anyone could provide any pointers, I desperately need to get it working for my project! Regards, Hardeep _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Dear All, I want to run the credit scheduler, however I guess it has not been incorporated into the 3.0.2 version. I tried installing the unstable version however that is giving me huge problems with respect to detection of my hard disk! I have no idea how to fix that. Is there any patch for 3.0.2 version to run the credit scheduler in it! I will be greatful if anyone could provide any pointers, I desperately need to get it working for my project! Regards, Hardeep _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hardeep Singh wrote:> Dear All, > > I want to run the credit scheduler, however I guess it has not been > incorporated into the 3.0.2 version. I tried installing the unstable > version however that is giving me huge problems with respect to > detection of my hard disk! I have no idea how to fix that. > > Is there any patch for 3.0.2 version to run the credit scheduler in it! > I will be greatful if anyone could provide any pointers, I desperately > need to get it working for my project! > > Regards, > Hardeep > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersMaybe you could post again and see if it backports itself into 3.0.2. :) -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 6/29/06, Hardeep Singh <hardeepguru@gmail.com> wrote:> Dear All, > > I want to run the credit scheduler, however I guess it has not been > incorporated into the 3.0.2 version. I tried installing the unstable version > however that is giving me huge problems with respect to detection of my hard > disk! I have no idea how to fix that.Have you tried diffing the working kernel config against the unstable version''s? Perhaps the kernel functionality you need is getting compiled as a module and you need an initrd?> > Is there any patch for 3.0.2 version to run the credit scheduler in it! I > will be greatful if anyone could provide any pointers, I desperately need to > get it working for my project! > > Regards, > Hardeep > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jun 29, 2006 at 06:55:40PM -0500, Hardeep Singh wrote:> I want to run the credit scheduler, however I guess it has not been > incorporated into the 3.0.2 version. I tried installing the unstable version > however that is giving me huge problems with respect to detection of my hard > disk! I have no idea how to fix that. > > Is there any patch for 3.0.2 version to run the credit scheduler in it! I > will be greatful if anyone could provide any pointers, I desperately need to > get it working for my project!It would be more productive that you tell us what''s the problem on unstable with your disks. Cheers, -- Vincent Hanquez _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Thanks a lot with regards to my previous postings. I did a line to line comparison of the .config of the xen3.0 and xen-unstable and found the appropriate disk driver required and managed to boot xen-unstable! However, I need to run the credit scheduler. I am running xen-unstable on ubuntu distribution on a 64bit architecture. Now when I issue xen the following command I get an error as shown below. Can anyone provide any pointers on how to fix this or whether there are any patches. root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10 (XEN) BUG at sched_credit.c:757 (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: e008:[<ff10fc00>] csched_tick+0x420/0x5a0 (XEN) EFLAGS: 00010096 CONTEXT: hypervisor (XEN) eax: 00000000 ebx: 00000000 ecx: 0000000a edx: 00000000 (XEN) esi: ff192080 edi: ff192e08 ebp: ff1646e1 esp: ff19df04 (XEN) cr0: 8005003b cr3: 3e919000 (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff19df04: (XEN) ff16419f ff1646e1 000002f5 ff12517b 00000000 ffffffff 00000246 ff192e00 (XEN) 0000001e 0000000a 00000000 00000000 00000000 ff1a5144 0000000a 00000000 (XEN) ff192080 ff19dfb4 00000075 ff111ef2 00000000 00000005 00000002 ff1a6200 (XEN) ff1a6200 ffbfed80 41438ac2 ff1140f6 00000000 cd123ee8 00000001 ff125317 (XEN) ff17e080 00000000 ff1a7780 00000000 00007ff0 cee6f200 c058b030 ff112f12 (XEN) 00007ff0 cee6f200 ff192080 ff1535d6 cd123edc 00000001 00000000 00007ff0 (XEN) cee6f200 c058b030 00000000 000e0004 c0101347 00000061 00000246 cd123ed8 (XEN) 00000069 0000007b 0000007b 00000000 00000000 00000000 ff192080 (XEN) Xen call trace: (XEN) [<ff10fc00>] csched_tick+0x420/0x5a0 (XEN) [<ff12517b>] process_deferred_ops+0x9b/0x160 (XEN) [<ff111ef2>] t_timer_fn+0x72/0xc0 (XEN) [<ff1140f6>] timer_softirq_action+0xc6/0x120 (XEN) [<ff125317>] do_update_va_mapping+0xd7/0x390 (XEN) [<ff112f12>] do_softirq+0x32/0x50 (XEN) [<ff1535d6>] process_softirqs+0x6/0x10 (XEN) (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ Regards, Hardeep Singh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
That''s not a known issue. I''ll take a look. Is this easily reproduceable? What changeset are you building? What exact sequence of "xm sched-credit" commands are you running to reproduce this? On Fri, Jun 30, 2006 at 09:49:57AM -0500, Hardeep Singh wrote:> Hi, > > Thanks a lot with regards to my previous postings. I did a line to line > comparison of the .config of the xen3.0 and xen-unstable and found the > appropriate disk driver required and managed to boot xen-unstable! > > However, I need to run the credit scheduler. I am running xen-unstable on > ubuntu distribution on a 64bit architecture. Now when I issue xen the > following command I get an error as shown below. Can anyone provide any > pointers on how to fix this or whether there are any patches. > > root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10 > > (XEN) BUG at sched_credit.c:757 > (XEN) ----[ Xen-3.0-unstable Not tainted ]---- > (XEN) CPU: 0 > (XEN) EIP: e008:[<ff10fc00>] csched_tick+0x420/0x5a0 > (XEN) EFLAGS: 00010096 CONTEXT: hypervisor > (XEN) eax: 00000000 ebx: 00000000 ecx: 0000000a edx: 00000000 > (XEN) esi: ff192080 edi: ff192e08 ebp: ff1646e1 esp: ff19df04 > (XEN) cr0: 8005003b cr3: 3e919000 > (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 > (XEN) Xen stack trace from esp=ff19df04: > (XEN) ff16419f ff1646e1 000002f5 ff12517b 00000000 ffffffff 00000246 > ff192e00 > (XEN) 0000001e 0000000a 00000000 00000000 00000000 ff1a5144 0000000a > 00000000 > (XEN) ff192080 ff19dfb4 00000075 ff111ef2 00000000 00000005 00000002 > ff1a6200 > (XEN) ff1a6200 ffbfed80 41438ac2 ff1140f6 00000000 cd123ee8 00000001 > ff125317 > (XEN) ff17e080 00000000 ff1a7780 00000000 00007ff0 cee6f200 c058b030 > ff112f12 > (XEN) 00007ff0 cee6f200 ff192080 ff1535d6 cd123edc 00000001 00000000 > 00007ff0 > (XEN) cee6f200 c058b030 00000000 000e0004 c0101347 00000061 00000246 > cd123ed8 > (XEN) 00000069 0000007b 0000007b 00000000 00000000 00000000 ff192080 > (XEN) Xen call trace: > (XEN) [<ff10fc00>] csched_tick+0x420/0x5a0 > (XEN) [<ff12517b>] process_deferred_ops+0x9b/0x160 > (XEN) [<ff111ef2>] t_timer_fn+0x72/0xc0 > (XEN) [<ff1140f6>] timer_softirq_action+0xc6/0x120 > (XEN) [<ff125317>] do_update_va_mapping+0xd7/0x390 > (XEN) [<ff112f12>] do_softirq+0x32/0x50 > (XEN) [<ff1535d6>] process_softirqs+0x6/0x10 > (XEN) > (XEN) ************************************ > (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT > CONTEXT. > (XEN) System shutting down -- need manual reset. > (XEN) ************************************ > > Regards, > Hardeep Singh> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hardeep, You probably want to post this to xen-devel, rather than xen-users, as it''s probably a bug in the code... -- Mats ________________________________ From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Hardeep Singh Sent: 30 June 2006 15:50 To: xen-users@lists.xensource.com; Vincent Hanquez; John Levin Subject: [Xen-users] Credit Scheduler! Hi, Thanks a lot with regards to my previous postings. I did a line to line comparison of the .config of the xen3.0 and xen-unstable and found the appropriate disk driver required and managed to boot xen-unstable! However, I need to run the credit scheduler. I am running xen-unstable on ubuntu distribution on a 64bit architecture. Now when I issue xen the following command I get an error as shown below. Can anyone provide any pointers on how to fix this or whether there are any patches. root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10 (XEN) BUG at sched_credit.c:757 (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: e008:[<ff10fc00>] csched_tick+0x420/0x5a0 (XEN) EFLAGS: 00010096 CONTEXT: hypervisor (XEN) eax: 00000000 ebx: 00000000 ecx: 0000000a edx: 00000000 (XEN) esi: ff192080 edi: ff192e08 ebp: ff1646e1 esp: ff19df04 (XEN) cr0: 8005003b cr3: 3e919000 (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff19df04: (XEN) ff16419f ff1646e1 000002f5 ff12517b 00000000 ffffffff 00000246 ff192e00 (XEN) 0000001e 0000000a 00000000 00000000 00000000 ff1a5144 0000000a 00000000 (XEN) ff192080 ff19dfb4 00000075 ff111ef2 00000000 00000005 00000002 ff1a6200 (XEN) ff1a6200 ffbfed80 41438ac2 ff1140f6 00000000 cd123ee8 00000001 ff125317 (XEN) ff17e080 00000000 ff1a7780 00000000 00007ff0 cee6f200 c058b030 ff112f12 (XEN) 00007ff0 cee6f200 ff192080 ff1535d6 cd123edc 00000001 00000000 00007ff0 (XEN) cee6f200 c058b030 00000000 000e0004 c0101347 00000061 00000246 cd123ed8 (XEN) 00000069 0000007b 0000007b 00000000 00000000 00000000 ff192080 (XEN) Xen call trace: (XEN) [<ff10fc00>] csched_tick+0x420/0x5a0 (XEN) [<ff12517b>] process_deferred_ops+0x9b/0x160 (XEN) [<ff111ef2>] t_timer_fn+0x72/0xc0 (XEN) [<ff1140f6>] timer_softirq_action+0xc6/0x120 (XEN) [<ff125317>] do_update_va_mapping+0xd7/0x390 (XEN) [<ff112f12>] do_softirq+0x32/0x50 (XEN) [<ff1535d6>] process_softirqs+0x6/0x10 (XEN) (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ Regards, Hardeep Singh _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 30, 2006 at 09:49:57AM -0500, Hardeep Singh wrote:> root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10 > > (XEN) BUG at sched_credit.c:757Ok I found the problem and submitted a fix to the staging tree. It should trickle out to the public tree in a couple hours when it''s gone through the regression tests. In the meantime, here''s a patch if you don''t want to wait. diff -r 3dfc2583a4f1 xen/common/sched_credit.c --- a/xen/common/sched_credit.c Thu Jun 29 16:59:47 2006 +0100 +++ b/xen/common/sched_credit.c Fri Jun 30 16:56:17 2006 +0100 @@ -622,9 +622,12 @@ csched_dom_cntl( if ( cmd->u.credit.weight != 0 ) { - csched_priv.weight -= sdom->weight; + if ( !list_empty(&sdom->active_sdom_elem) ) + { + csched_priv.weight -= sdom->weight; + csched_priv.weight += cmd->u.credit.weight; + } sdom->weight = cmd->u.credit.weight; - csched_priv.weight += sdom->weight; } if ( cmd->u.credit.cap != (uint16_t)~0U ) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, I have tried running that command 3 times and it has cropped up everytime! And I have no idea what changesets are. I am pretty much a newbie to xen and after a long struggle did I manage to get xen-unstable working. I needed the credit scheduler for a part of my project. I had downloaded the tarball of xen-unstable yesterday and compiled it and on running the ''xm sched-credit -d vm1 -w 10'' I got the error! As for the sequence of commands. - On one instance I ran ''xm sched-credit -d vm1'' and that worked fine. It showed me the cap and weight of that domain. After that ''''xm sched-credit -d vm1 -w 10'' gave an error. - On another instance I directly ran ''xm sched-credit -d vm1 -w 10'' and got the same error Please lemme kno if I need to update my unstable version and how to do it. Regards, Hardeep Singh On 6/30/06, Emmanuel Ackaouy <ack@xensource.com> wrote:> > That''s not a known issue. I''ll take a look. > > Is this easily reproduceable? > What changeset are you building? > What exact sequence of "xm sched-credit" commands are you > running to reproduce this? > > On Fri, Jun 30, 2006 at 09:49:57AM -0500, Hardeep Singh wrote: > > Hi, > > > > Thanks a lot with regards to my previous postings. I did a line to > line > > comparison of the .config of the xen3.0 and xen-unstable and found > the > > appropriate disk driver required and managed to boot xen-unstable! > > > > However, I need to run the credit scheduler. I am running > xen-unstable on > > ubuntu distribution on a 64bit architecture. Now when I issue xen the > > following command I get an error as shown below. Can anyone provide > any > > pointers on how to fix this or whether there are any patches. > > > > root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10 > > > > (XEN) BUG at sched_credit.c:757 > > (XEN) ----[ Xen-3.0-unstable Not tainted ]---- > > (XEN) CPU: 0 > > (XEN) EIP: e008:[<ff10fc00>] csched_tick+0x420/0x5a0 > > (XEN) EFLAGS: 00010096 CONTEXT: hypervisor > > (XEN) eax: 00000000 ebx: 00000000 ecx: 0000000a edx: 00000000 > > (XEN) esi: ff192080 edi: ff192e08 ebp: ff1646e1 esp: ff19df04 > > (XEN) cr0: 8005003b cr3: 3e919000 > > (XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008 > > (XEN) Xen stack trace from esp=ff19df04: > > (XEN) ff16419f ff1646e1 000002f5 ff12517b 00000000 ffffffff > 00000246 > > ff192e00 > > (XEN) 0000001e 0000000a 00000000 00000000 00000000 ff1a5144 > 0000000a > > 00000000 > > (XEN) ff192080 ff19dfb4 00000075 ff111ef2 00000000 00000005 > 00000002 > > ff1a6200 > > (XEN) ff1a6200 ffbfed80 41438ac2 ff1140f6 00000000 cd123ee8 > 00000001 > > ff125317 > > (XEN) ff17e080 00000000 ff1a7780 00000000 00007ff0 cee6f200 > c058b030 > > ff112f12 > > (XEN) 00007ff0 cee6f200 ff192080 ff1535d6 cd123edc 00000001 > 00000000 > > 00007ff0 > > (XEN) cee6f200 c058b030 00000000 000e0004 c0101347 00000061 > 00000246 > > cd123ed8 > > (XEN) 00000069 0000007b 0000007b 00000000 00000000 00000000 > ff192080 > > (XEN) Xen call trace: > > (XEN) [<ff10fc00>] csched_tick+0x420/0x5a0 > > (XEN) [<ff12517b>] process_deferred_ops+0x9b/0x160 > > (XEN) [<ff111ef2>] t_timer_fn+0x72/0xc0 > > (XEN) [<ff1140f6>] timer_softirq_action+0xc6/0x120 > > (XEN) [<ff125317>] do_update_va_mapping+0xd7/0x390 > > (XEN) [<ff112f12>] do_softirq+0x32/0x50 > > (XEN) [<ff1535d6>] process_softirqs+0x6/0x10 > > (XEN) > > (XEN) ************************************ > > (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN > INTERRUPT > > CONTEXT. > > (XEN) System shutting down -- need manual reset. > > (XEN) ************************************ > > > > Regards, > > Hardeep Singh > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users >-- hardeep _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Oh! Thanks a lot. I know this sounds lame but can you tell me what do I need to do in order to run the patch :) Regards, Hardeep On 6/30/06, Emmanuel Ackaouy <ack@xensource.com> wrote:> > On Fri, Jun 30, 2006 at 09:49:57AM -0500, Hardeep Singh wrote: > > root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10 > > > > (XEN) BUG at sched_credit.c:757 > > Ok I found the problem and submitted a fix to the staging > tree. It should trickle out to the public tree in a couple > hours when it''s gone through the regression tests. > > In the meantime, here''s a patch if you don''t want to wait. > > diff -r 3dfc2583a4f1 xen/common/sched_credit.c > --- a/xen/common/sched_credit.c Thu Jun 29 16:59:47 2006 +0100 > +++ b/xen/common/sched_credit.c Fri Jun 30 16:56:17 2006 +0100 > @@ -622,9 +622,12 @@ csched_dom_cntl( > > if ( cmd->u.credit.weight != 0 ) > { > - csched_priv.weight -= sdom->weight; > + if ( !list_empty(&sdom->active_sdom_elem) ) > + { > + csched_priv.weight -= sdom->weight; > + csched_priv.weight += cmd->u.credit.weight; > + } > sdom->weight = cmd->u.credit.weight; > - csched_priv.weight += sdom->weight; > } > > if ( cmd->u.credit.cap != (uint16_t)~0U ) >-- hardeep _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Emmanuel,
I modified my sched_credit.c manually and it looks like this right now..
<snip>
if ( cmd->u.credit.weight != 0 )
{
csched_priv.weight -= sdom->weight;
if ( !list_empty(&sdom->active_sdom_elem) )
{
csched_priv.weight -= sdom->weight;
csched_priv.weight += cmd->u.credit.weight;
}
sdom->weight = cmd->u.credit.weight;
csched_priv.weight += sdom->weight;
}
if ( cmd->u.credit.cap != (uint16_t)~0U )
sdom->cap = cmd->u.credit.cap;
</snip>
I futher did a `make clean; make; make install` and tried booting into the
unstable version again. I then tried setting the weight of one of the
domains to 512 and it worked perfectly. The CPU distribution was also as
expected!
However I next tried setting the weight to 20 and got the error shown below!
I booted again in xen and tried setting the weight to 256 and it worked
however when I set it to 255, xen again crashed!
(XEN) BUG at sched_credit.c:764
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: e008:[<ff10fc30>] csched_tick+0x420/0x5a0
(XEN) EFLAGS: 00010096 CONTEXT: hypervisor
(XEN) eax: 00000000 ebx: 00000000 ecx: 0000000a edx: 00000000
(XEN) esi: ff1d7080 edi: ff192e08 ebp: ff164721 esp: ff19def8
(XEN) cr0: 8005003b cr3: 0fcf8000
(XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from esp=ff19def8:
(XEN) ff1641df ff164721 000002fc 00000292 ff16e500 00000020 00000246
ff192e00(XEN) 0000001e 000000ff 00000000 00000000 ff16e500 ff1a5144
000000ff 00000000(XEN) ff1d7080 ff19dfb4 0000002d ff111f22 00000000
00000003 00000001 ff1a6200(XEN) ff1a6200 ffbfed80 33a125ef ff114126
00000000 ff1d7080 0000002d ff11e306(XEN) ff19df7c 00000000 ff1a7780
00000000 00000000 ff1d7080 0000002d ff112f42(XEN) 00f90000 ff11a73e
ff19dfb4 ff11a752 00000001 000002f0 ff19dfb4 00000001(XEN) 00000000
00000000 00000001 c039e000 00000000 00000000 000d0000 c01013a7(XEN)
00000061 00000246 c039ffa4 00000069 0000007b 0000007b 00000000
00000000(XEN) 00000000 ff1d7080
(XEN) Xen call trace:
(XEN) [<ff10fc30>] csched_tick+0x420/0x5a0
(XEN) [<ff111f22>] t_timer_fn+0x72/0xc0
(XEN) [<ff114126>] timer_softirq_action+0xc6/0x120
(XEN) [<ff11e306>] apic_timer_interrupt+0x46/0x50
(XEN) [<ff112f42>] do_softirq+0x32/0x50
(XEN) [<ff11a73e>] idle_loop+0x4e/0x80
(XEN) [<ff11a752>] idle_loop+0x62/0x80
(XEN)
(XEN) ************************************
(XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT
CONTEXT.(XEN) System shutting down -- need manual reset.
(XEN) ************************************
Can you please have a look into it! I guess xen crashes only when weights
less than 256 are set to a particular domain!
Thanks & Regards,
Hardeep Singh
On 6/30/06, Emmanuel Ackaouy <ack@xensource.com>
wrote:>
> On Fri, Jun 30, 2006 at 09:49:57AM -0500, Hardeep Singh wrote:
> > root@pippin:/home/hardeep# xm sched-credit -d vm1 -w 10
> >
> > (XEN) BUG at sched_credit.c:757
>
> Ok I found the problem and submitted a fix to the staging
> tree. It should trickle out to the public tree in a couple
> hours when it''s gone through the regression tests.
>
> In the meantime, here''s a patch if you don''t want to
wait.
>
> diff -r 3dfc2583a4f1 xen/common/sched_credit.c
> --- a/xen/common/sched_credit.c Thu Jun 29 16:59:47 2006 +0100
> +++ b/xen/common/sched_credit.c Fri Jun 30 16:56:17 2006 +0100
> @@ -622,9 +622,12 @@ csched_dom_cntl(
>
> if ( cmd->u.credit.weight != 0 )
> {
> - csched_priv.weight -= sdom->weight;
> + if ( !list_empty(&sdom->active_sdom_elem) )
> + {
> + csched_priv.weight -= sdom->weight;
> + csched_priv.weight += cmd->u.credit.weight;
> + }
> sdom->weight = cmd->u.credit.weight;
> - csched_priv.weight += sdom->weight;
> }
>
> if ( cmd->u.credit.cap != (uint16_t)~0U )
>
--
hardeep
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On 7/1/06, Hardeep Singh <hardeepguru@gmail.com> wrote:> > Can you please have a look into it! I guess xen crashes only when weights > less than 256 are set to a particular domain! >I am using the credit scheduler on a production box and i am able to set weights less than 256 for any domU. The box has centos 4.3 as dom0 and domU''s and is running the 10470 changeset. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hmm... looks like i spoke too soon. I tried to test it again just in case for a domU to assign it 128 weight, the server crashed instantly :( Since this is a remote server i didn''t see what actually happened when i tried to change the weight. After the server reboots, i will try to update to the latest changeset and see if it works properly. On 7/3/06, Anand Gupta <xen.mails@gmail.com> wrote:> > On 7/1/06, Hardeep Singh <hardeepguru@gmail.com> wrote: > > > > Can you please have a look into it! I guess xen crashes only when > > weights less than 256 are set to a particular domain! > > >-- regards, Anand Gupta _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Upgraded to the latest unstable changeset and now weights below 128 work :) On 7/1/06, Hardeep Singh <hardeepguru@gmail.com> wrote:> > > > > > Can you please have a look into it! I guess xen crashes only when > > > weights less than 256 are set to a particular domain! > > > > >-- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
To clarify: The bug was fixed Friday and it had nothing to do with the actual weight being set. The crash happened when setting any weight on an idle domain. This is the changeset that fixes the problem: changeset: 10570:64f9f308e109 user: ack@localhost.localdomain date: Fri Jun 30 17:12:05 2006 +0100 summary: Don''t modify global active weight when changing weight of inactive domain. On Mon, Jul 03, 2006 at 07:24:34PM +0530, Anand Gupta wrote:> Upgraded to the latest unstable changeset and now weights below 128 work > :) > > On 7/1/06, Hardeep Singh <[1]hardeepguru@gmail.com> wrote: > > Can you please have a look into it! I guess xen crashes only when > weights less than 256 are set to a particular domain! > > -- > regards, > > Anand Gupta > > References > > Visible links > 1. mailto:hardeepguru@gmail.com> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Emmanuel! Is it possible to change the default weight and cap on a domU through its config file ? On 7/3/06, Emmanuel Ackaouy <ack@xensource.com> wrote:> > To clarify: > > The bug was fixed Friday and it had nothing to do with the actual > weight being set. The crash happened when setting any weight on an > idle domain. > > This is the changeset that fixes the problem: > > changeset: 10570:64f9f308e109 > user: ack@localhost.localdomain > date: Fri Jun 30 17:12:05 2006 +0100 > summary: Don''t modify global active weight when changing weight of > inactive domain. >-- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jul 04, 2006 at 01:44:53PM +0530, Anand Gupta wrote:> Hi Emmanuel! > > Is it possible to change the default weight and cap on a domU through its > config file ?No. Argueably, we really should add support for this. If someone sends a good patch on xen-devel, I''ll apply it. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hey, Thanks a lot. Everything is perfect now! Sorry cudn''t reply earlier, was out vacationing over the long weekend :D Thanks Emmanuel! Regards, Hardeep On 7/3/06, Emmanuel Ackaouy <ack@xensource.com> wrote:> > To clarify: > > The bug was fixed Friday and it had nothing to do with the actual > weight being set. The crash happened when setting any weight on an > idle domain. > > This is the changeset that fixes the problem: > > changeset: 10570:64f9f308e109 > user: ack@localhost.localdomain > date: Fri Jun 30 17:12:05 2006 +0100 > summary: Don''t modify global active weight when changing weight of > inactive domain. > > > > On Mon, Jul 03, 2006 at 07:24:34PM +0530, Anand Gupta wrote: > > Upgraded to the latest unstable changeset and now weights below 128 > work > > :) > > > > On 7/1/06, Hardeep Singh <[1]hardeepguru@gmail.com> wrote: > > > > Can you please have a look into it! I guess xen crashes only > when > > weights less than 256 are set to a particular domain! > > > > -- > > regards, > > > > Anand Gupta > > > > References > > > > Visible links > > 1. mailto:hardeepguru@gmail.com > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users >-- hardeep _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel