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] Incomplete 3.2 binary packages

To: Chris Lalancette <clalance@xxxxxxxxxx>
Subject: Re: [Xen-devel] Incomplete 3.2 binary packages
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 27 Feb 2008 15:30:57 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 27 Feb 2008 07:33:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47C5778A.9080806@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <47C5778A.9080806@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Chris Lalancette writes ("[Xen-devel] Incomplete 3.2 binary
> packages"): I went to: http://xen.org/download/dl_32rhel5.html and
> downloaded the binary RPMS for 3.2 to do a quick test.  However, it
> seems that the binary RPMS don't include the qemu device model, so
> fully virt guests have no chance of starting.  It's not a huge deal
> for me, since I can recompile from source; however, for those who
> don't want to do that, or who want to save a little time (my
> original goal), it might be nice to include everything needed in
> those binary RPMS.  Just FYI.

xen-3.2.0-0xs.centos5.i386.rpm contains /usr/lib/xen/bin/qemu-dm.

When I built the Xen 3.2 binary packages I did check that they
contained roughly the same things in the same places as the upstream
packages, but in general my (very light) testing did not include
starting an HVM guest.  So there may well be a bug here.

Can you confirm that qemu-dm is on your system ?  If not do you know
why not ?  If you have some more information (for example, actual
error messages which show where it is looking for which file) I might
be able to fix it up if indeed it's a bug in the package.


Xen-devel mailing list

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