From: "Jan Beulich" <JBeulich@novell.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Debian Lenny 2.6.26-2-xen-686 crashing as multi-vcpu domU, stack trace
Date: Fri, 05 Mar 2010 13:00:39 +0000 [thread overview]
Message-ID: <4B910E870200007800032F92@vpn.id2.novell.com> (raw)
In-Reply-To: <20100305124709.GA2580@reaktio.net>
>>> Pasi Kärkkäinen<pasik@iki.fi> 05.03.10 13:47 >>>
>Basicly the guest get stuck somehow, and starts to consume all the CPU time it can get.
Would seem like you posted the xenctx output only for one of the two
vCPU-s (which isn't able to acquire xtime_lock as it seems) - the
question is what the other vCPU is doing then.
Jan
next prev parent reply other threads:[~2010-03-05 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 12:47 Debian Lenny 2.6.26-2-xen-686 crashing as multi-vcpu domU, stack trace Pasi Kärkkäinen
2010-03-05 13:00 ` Jan Beulich [this message]
2010-03-05 13:12 ` Pasi Kärkkäinen
2010-03-07 15:52 ` Pasi Kärkkäinen
2010-03-08 8:05 ` Jan Beulich
2010-03-08 8:36 ` Pasi Kärkkäinen
2010-03-08 8:54 ` Jan Beulich
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=4B910E870200007800032F92@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=pasik@iki.fi \
--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).