From: Ian Campbell <ijc@hellion.org.uk>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>, jeremy@goop.org
Subject: Re: 2.6.34-rc2: xen DomU not booting
Date: Sat, 20 Mar 2010 09:33:22 +0000 [thread overview]
Message-ID: <1269077602.28761.42.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.01.1003200058030.5493@bogon.housecafe.de>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
On Sat, 2010-03-20 at 01:14 -0700, Christian Kujau wrote:
> Hi there,
>
> again a bit late in the game, I tried to upgrade one of my DomUs from
> 2.6.33 to 2.6.34-git (tried -rc1 yesterday, pulled again today, so I'm on
> -rc2 now):
>
> ------
> dom0# xm create sid.cfg -c
> Using config file "/etc/xen/sid.cfg".
> Started domain sid
>
> ------
>
> Then it just "hangs" there:
Can you try this patch please, I think it will resolve the issue you
see.
https://patchwork.kernel.org/patch/87081/
> it won't return to the shellprompt (as if the
> domU crashed) but it won't connect to the domU console either (as it does
> perfectly with 2.6.33). And indeed, the domU is listed as running:
>
> dom0# (xm list sid ; sleep 3; xm list sid) | grep ^sid
> sid 55 256 1 r----- 140.8
> sid 55 256 1 r----- 144.3
>
> Also, "xm dmesg" is blank and netconsole doesn't work inside a domU, IIRC.
>
> Hints how to debug this (besides doing git bisect, again) are very much
> welcome!
>
> Oh, the Dom0 is Ubuntu 8.04 (2.6.24-24, Xen 3.2.0) on a Mac Mini.
>
> Thanks,
> Christian.
--
Ian Campbell
You! What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-20 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 8:14 Christian Kujau
2010-03-20 9:33 ` Ian Campbell [this message]
2010-03-20 10:37 ` Christian Kujau
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=1269077602.28761.42.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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
all inboxes | Powered by JetHome®