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


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

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] current xen/stable failed upgrade from
From: Josip Rodin <joy@xxxxxxxxxxxxxx>
Date: Sat, 6 Mar 2010 12:58:33 +0100
Delivery-date: Sat, 06 Mar 2010 03:59:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)

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.

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.

.config is attached, I can also make the image itself available or whatever.
Please help.

(Please Cc: any responses, I'm not subscribed.)

     2. That which causes joy or happiness.

Attachment: failing.config-
Description: Text document

Xen-devel mailing list