This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] current xen/stable failed upgrade from

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] current xen/stable failed upgrade from
From: Josip Rodin <joy@xxxxxxxxxxxxxx>
Date: Mon, 8 Mar 2010 00:31:47 +0100
Delivery-date: Sun, 07 Mar 2010 15:32:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100306132711.GK2580@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100306115833.GA28039@xxxxxxxxxxxxxxx> <20100306132711.GK2580@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
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 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 dom0 kernel works with Xen 3.4.3rc3 
> hypervisor,


> but when you update the dom0 kernel to current xen/master, it 
> crashes? 

When I update it to current xen/stable (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.

Xen-devel mailing list