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] xen 3.0.3

To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Subject: Re: [Xen-users] xen 3.0.3
From: "Fong Vang" <sudoyang@xxxxxxxxx>
Date: Thu, 19 Oct 2006 11:22:27 -0700
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx, Jaume Sabater <jsabater@xxxxxxxxxxxxx>
Delivery-date: Thu, 19 Oct 2006 11:23:12 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BP/m+XAWKMSiNYUp7wgTSORsdwQUwPFxXOxsTnU0Nwi6MRaV5O25QiqfZwSZvesZ8Akqnok0YgooDe/v3OF0mMCfWUEOIMa+K7Q27vZZcJLkowvTgGTKK3i/s6OjcKlJQtauFt9lxuGJffX4glrFLuSta2lPNCStWqATubnt7Y4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E1643@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4f52331f0610180924l44606b7eod78e2330be2398bc@xxxxxxxxxxxxxx> <907625E08839C4409CE5768403633E0B018E1643@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I'm experience something strange in the new domU running Xen 3.0.3.  I
cannot install some packages, even when trying to force an rpm install
using --force and --nodeps.

# rpm -Uvh --force --nodeps
'http://10.1.34.99/L1/IBM_db2cliv81-8.1.0-89.i386.rpm'
Retrieving http://10.1.34.99/L1/IBM_db2cliv81-8.1.0-89.i386.rpm
Preparing...                ########################################### [100%]
error: %pre(IBM_db2cliv81-8.1.0-89.i386) scriptlet failed, exit status 255
error:   install: %pre scriptlet failed (2), skipping IBM_db2cliv81-8.1.0-89

This same command works fine on a system outside of Xen.  As you can
see, it fails during the %pre section which only sets a variable:

preinstall scriptlet (using /bin/sh):

DB2DIR="/opt/IBM/db2/V8.1"


exit 0
postinstall scriptlet (using /bin/sh):

DB2DIR="/opt/IBM/db2/V8.1"
SPBDIR="${DB2DIR?}/spb"
DOCDIR="${DB2DIR?}/doc"
DQPDIR="${DB2DIR?}/qp"


Could this be that vtpm is disabled?  This works fine on a xen 3.0.2
system with vtpm enabled.


On 10/18/06, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:


> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Fong Vang
> Sent: 18 October 2006 17:24
> To: Jaume Sabater
> Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] xen 3.0.3
>
> On 10/18/06, Jaume Sabater <jsabater@xxxxxxxxxxxxx> wrote:
> > Fong Vang wrote:
> >
> > > I have several systems running Xen 3.0.2 on Fedora Core 5.
> > >
> > > Today, I started playing with Xen 3.0.3 also on FC5.
> dom0 starts up
> > > fine without any problem.  However, I cannot create any
> domU's (domU =
> > > CentOS 4.4).  This is the error being reported:
> > >
> > >
> > > [root@xenmgt ~]# xm create -c meta
> > > Using config file "/etc/xen/meta".
> > > Error: Device 0 (vtpm) could not be connected. Backend
> device not found.
> >
> > Same happened to me on Debian with 3.0.3 RCs. Didn't manage
> to fix it,
> > so I am still using version 3.0.2.
>
> Thanks for the input.  The list is kinda quiet.  Unfortunately, with
> the newer hardware I've been getting, dom0 running 3.0.2 kernel panics
> all the time (consistently across multiple hardware so memory or other
> hardware problem is unlikely).  The good news is that 3.0.3 appears to
> be running very stable on the new hardware, except that I cannot
> create any domU's.

(vtpm) indicates that you're using the virtual TPM. Is this something
you wanted to do, or just accidentally switched on (or didn't switch
off?). Check the latest config files and see if they say anything on how
to switch this off if you can live without a virtual TPM...

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




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