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-users

Re: [Xen-users] DomU kernel-xen upgade from 2.6.31 - 2.6.32 causes Gues

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] DomU kernel-xen upgade from 2.6.31 - 2.6.32 causes Guest boot to fail. known issue?
From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
Date: Sun, 24 Jan 2010 09:06:45 -0800
Cc: Xen User-List <Xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 24 Jan 2010 09:07:23 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ytQBg8R7WNdGH9O9wZjMJ6WmGE246cApQ/2p78Loe1k=; b=rHqjZSPeszeU3+vgFFdOFaMu9IeCcSGdS7Uzdm5N3fLWrnt3b5+BHbPCpBaTP9Og8Z ErrT3VmQaU4dN/zLG07LFfK8FpoJmudiQjfgs1aMvKjSHT3Cfg79ZQW3I7qtTRAvK96e ngMhSbebU41OohH8MxVmG0oREpa9oNAYE+5Ms=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YFfIpMRH7eZ1kWcLqx3GzPDSksbq0NqQ3klJYRAACcYrmcjoGaqsBD7VqQnEnhVmO8 gETvEhjAjI8hgT1OWlJETd0g70szJ2uiBKCNzQ0F2H+NDiwWIrzUYNwdOJKCqR8s+ESh qe0ZdGKrf1TiTK6WNaVAUJEECsQUDLT6z9/hs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100124115511.GC2861@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <c67eed301001231807q18e923c5p91ac23aee94d25d@xxxxxxxxxxxxxx> <20100124115511.GC2861@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, Jan 24, 2010 at 3:55 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> to 2.6.32-41-xen (opensuse KOTD), no problems at the upgrade or with 
>> mkinitrd,
>>
>
> Did you try 2.6.32-41.1 ?


trying now in the DomU ... does NOT look good :-/

The following NEW package is going to be installed:
  kernel-xen  2.6.32-41.1  x86_64  KOTD  obs://build.opensuse.org/Kernel

The following package is not supported by its vendor:
  kernel-xen  2.6.32-41.1  x86_64  KOTD  obs://build.opensuse.org/Kernel

1 new package to install.
Overall download size: 32.8 MiB. After the operation, additional 119.5
MiB will be used.
Continue? [y/n/?] (y): y
...

Installing: kernel-xen-2.6.32-41.1 [error]
Installation of kernel-xen-2.6.32-41.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
rpmdb: PANIC: Invalid argument
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) storing record �▒-0������Z@����j into Filedigests
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "(��       �]�ȴ�-�
                                               %���j" records from
Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
Q��>V� error(-30977) getting "(�rKaÃ)��U��y���j" records from
Filedigests index
rpmdb:g������j" records from Filedigests index recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal
error, run database recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "��yx��\;�����Fy���j" records from
Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "���7�F��@� A      �j" records from
Filedigests index
rpmdb: PANIC: fatal region error detected; run recoveryfrom
Filedigests index
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "����[��$�-��0"��j" records from
Filedigests index database recovery
rpmdb: PANIC: fatal region error detected; run recoveryds from
Filedigests index
...
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal
error, run database recovery

Abort, retry, ignore? [a/r/i] (a):


I think maybe I'll wait a bit   ;-)

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

<Prev in Thread] Current Thread [Next in Thread>