[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Credit Scheduler!


  • To: xen-users@xxxxxxxxxxxxxxxxxxx, "Vincent Hanquez" <vincent.hanquez@xxxxxxxxxxxx>, "John Levin" <xenjohn@xxxxxxxxx>
  • From: "Hardeep Singh" <hardeepguru@xxxxxxxxx>
  • Date: Fri, 30 Jun 2006 09:49:57 -0500
  • Delivery-date: Fri, 30 Jun 2006 07:50:39 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Q4hN9HS9iUwGkSs+rnpyFyGv6ErNlps7jLuMQarZOdMLgQcYpGTqjltQSV7JLFUpPuLmLPSQeXLwmfnXg5rnP6U8JORxWmjM2mjwQnj1ngjgxBd75uvZ73R5nZpeHUno2AxgPZdkoS74+iTYDhQIFD2MXQkCsLmzj+Y3CC/839I=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.