From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: MadLoisae@gmx.net, xen-devel@lists.xensource.com
Subject: Re: on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" [xen 4.0, xen 4.1]
Date: Thu, 14 Apr 2011 09:23:27 -0400 [thread overview]
Message-ID: <20110414132327.GG5548@dumpdata.com> (raw)
In-Reply-To: <C9CBDC64.164E9%keir.xen@gmail.com>
On Wed, Apr 13, 2011 at 11:04:04PM +0100, Keir Fraser wrote:
> On 13/04/2011 22:38, "MadLoisae@gmx.net" <MadLoisae@gmx.net> wrote:
>
> > Hello Keir,
> >
> > thanks for your idea.
> > Have installed xen 4.1 amd64 packages, boots correctly but sadly the
> > same issue.
> > I've attached xm dmesg and dmesg from dom0 (and also attached this time
> > missing logs from my last mail)
> >
> > Thanks in advance for further hints.
>
> The logs don't show much, except that dom0 seems to be losing interrupts
> after the HVM guest starts. Do you get more from 'xm dmesg' if you boot Xen
> with the extra boot parameters "loglvl=all guest_loglvl=all"? What is your
> HVM domain config?
Keir, didn't we have a problem with hvmloader where it would call populate_physmap
and take a very long time when moving the PFNs around? I can't remember the details though :-(
next prev parent reply other threads:[~2011-04-14 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 18:20 on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" [xen 4.0, xen 4.1] MadLoisae
2011-04-13 18:44 ` Keir Fraser
2011-04-13 21:38 ` MadLoisae
2011-04-13 22:04 ` Keir Fraser
2011-04-14 13:23 ` Konrad Rzeszutek Wilk [this message]
2011-04-15 22:11 ` MadLoisae
2011-04-18 21:02 ` Konrad Rzeszutek Wilk
2011-04-18 22:23 ` MadLoisae
2011-04-18 22:35 ` MadLoisae
2011-04-19 13:28 ` Konrad Rzeszutek Wilk
2011-04-19 19:16 ` MadLoisae
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=20110414132327.GG5548@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=MadLoisae@gmx.net \
--cc=keir.xen@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).