From: Josip Rodin <joy@entuzijast.net>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6
Date: Mon, 8 Mar 2010 00:31:47 +0100 [thread overview]
Message-ID: <20100307233147.GA20068@orion.carnet.hr> (raw)
In-Reply-To: <20100306132711.GK2580@reaktio.net>
On Sat, Mar 06, 2010 at 03:27:11PM +0200, Pasi Kärkkäinen wrote:
> On Sat, Mar 06, 2010 at 12:58:33PM +0100, Josip Rodin wrote:
> > I updated the hypervisor from 3.4.0 to 3.4.3rc3, which seemed to go well
> > because it seems to behave as usual, but the dom0 kernel update from an
> > earlier (pre-2009-11-30) xen/master snapshot based on 2.6.31.6 didn't -
> > as soon as it starts, it just instantly reboots, or if noreboot is passed,
> > it gets stuck, with absolutely nothing on the screen.
>
> So the 2009-11-30 xen/master 2.6.31.6 dom0 kernel works with Xen 3.4.3rc3 hypervisor,
Yes.
> but when you update the dom0 kernel to current xen/master 2.6.31.6, it crashes?
When I update it to current xen/stable 2.6.32.9. (I put that bit in the
subject only, sorry.)
> > I tried adding loglvl=all guest_loglvl=all sync_console console_to_ring
> > to the hypervisor options, and console=hvc0 earlyprintk=xen initcall_debug
> > to the kernel options, to no avail. The hypervisor showed the sync console
> > warning, but the dom0 kernel didn't change its behaviour.
>
> You should set up a serial console so you can capture the boot/error logs,
> and we can analyze them to troubleshoot the problem, see:
>
> http://wiki.xensource.com/xenwiki/XenSerialConsole
The machine has iLO VSP, so I'll try that next time I have a debugging
time slot, thanks.
--
2. That which causes joy or happiness.
next parent reply other threads:[~2010-03-07 23:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100306115833.GA28039@orion.carnet.hr>
[not found] ` <20100306132711.GK2580@reaktio.net>
2010-03-07 23:31 ` Josip Rodin [this message]
2010-03-08 23:16 ` current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6 Jeremy Fitzhardinge
2010-03-09 9:01 ` Josip Rodin
2010-03-11 23:25 ` Yasir Assam
2010-03-11 23:40 ` Boris Derzhavets
2010-03-12 2:22 ` Yasir Assam
2010-03-12 7:14 ` Pasi Kärkkäinen
2010-03-12 11:28 ` Boris Derzhavets
2010-03-12 21:41 ` Yasir Assam
2010-03-11 15:08 ` Josip Rodin
2010-03-11 19:24 ` Pasi Kärkkäinen
2010-03-12 11:41 ` Josip Rodin
2010-03-12 12:09 ` Josip Rodin
2010-03-23 23:18 ` Josip Rodin
2010-03-23 23:22 ` Josip Rodin
2010-03-24 5:10 ` Jeremy Fitzhardinge
2010-03-24 8:37 ` Josip Rodin
2010-03-12 13:02 ` Pasi Kärkkäinen
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=20100307233147.GA20068@orion.carnet.hr \
--to=joy@entuzijast.net \
--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).