From: "guilherme m. schroeder" <guialemas@gmail.com>
To: xen-devel@lists.xensource.com
Subject: dom0 crash on csched_acct
Date: Thu, 29 Dec 2011 09:15:14 -0200 [thread overview]
Message-ID: <CAPxDueV_2oNTFQocbGY67Y9Cq2=wwX7VGL7+WayeSxu6Y_L1Nw@mail.gmail.com> (raw)
Hi,
I'm having some random crashes with XenServer 5.6 SP2 (Xen 3.4.2).
I thought that it was a problem with Xen 3.4 and tried XenServer 6.0
(Xen 4.1.1), but no luck.
I know that this list is about XenSource and (maybe) doesn't cover it,
but i'm trying to understand
what is happening.
All i have is this crash.log: http://cpro3845.publiccloud.com.br/crash.log
Kdump segfaults on XenServer, so no core to help.
I took a look on sched_credit.c +978 and this is what triggering the crash:
BUG_ON( (sdom->weight * sdom->active_vcpu_count) > weight_left );
We have some VM's that have different vCPU priority values. Could be
this that is triggering the problem?
Also, there is a limit for vcpu_count on a host?
I'm still trying to reproduce the crash, but it's totally random.
Does anyone have an idea or where to start?
If more details are needed, let me know.
Thanks.
next reply other threads:[~2011-12-29 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 11:15 guilherme m. schroeder [this message]
2012-01-03 10:19 ` dom0 crash on csched_acct Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPxDueV_2oNTFQocbGY67Y9Cq2=wwX7VGL7+WayeSxu6Y_L1Nw@mail.gmail.com' \
--to=guialemas@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).