WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Josip Rodin <joy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sat, 6 Mar 2010 15:27:11 +0200
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 06 Mar 2010 05:27:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100306115833.GA28039@xxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, Mar 06, 2010 at 12:58:33PM +0100, Josip Rodin wrote:
> Hi,
> 
> 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,
but when you update the dom0 kernel to current xen/master 2.6.31.6, it crashes? 

> 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
http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel