From: Anthony Wright <anthony@overnetdata.com>
To: xen-devel@lists.xen.org
Subject: First DomU started goes into a busy loop
Date: Mon, 24 Sep 2012 16:31:27 +0100 [thread overview]
Message-ID: <50607CCF.9050904@overnetdata.com> (raw)
On a 32 bit Xen 4.20 system with a 3.5.4 kernel around 40% of the time
when the system starts up the first DomU to be started goes into a busy
loop (always in state r----- which CPU constantly increasing) with no
console output. If I destroy the DomU and restart it with identical
settings, it starts correctly. I got the same happening with Xen 4.1
with a 3.5.3 kernel, but tried upgrading to see if that fixed it, but it
didn't.
If I connect to the console there's no output, and I can't get find any
useful information in the logs or xl dmesg. The DomU is running a 3.3.2
32 bit linux kernel.
Can you give me any suggestions how I might diagnose what's going on ?
thanks,
Anthony
next reply other threads:[~2012-09-24 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 15:31 Anthony Wright [this message]
2012-09-24 17:18 ` First DomU started goes into a busy loop Andrew Cooper
2012-09-25 8:20 ` Ian Campbell
2012-09-25 16:30 ` Anthony Wright
2012-09-25 16:33 ` Ian Campbell
2012-09-25 16:35 ` Andrew Cooper
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=50607CCF.9050904@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.