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

[Xen-devel] [ANNOUNCE] paravirt_ops i686 Fedora rawhide kernel packages

To: fedora-xen@xxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [ANNOUNCE] paravirt_ops i686 Fedora rawhide kernel packages
From: Chris Wright <chrisw@xxxxxxxxxxxx>
Date: Tue, 1 May 2007 17:39:08 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 01 May 2007 17:38:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.2i
If you are interested in trying the new paravirt_ops kernels, I've
created some packages and uploaded them to:

  http://et.redhat.com/~chrisw/paravirt_ops/

There you'll find a yum repo (see yum.README for details) and an
INSTALL file for getting started.  With this package you can use a
single kernel[1] for both native (w/out a hypervisor, or under a full
virt hypervisor), domU paravirt under Xen, and a VMI guest.  There is no
support for dom0 kernels ATM.  Running the kernel native is as simple as
installing and rebooting.  However, it requires some manual intervention
to get a domU started (see INSTALL for details).

thanks,
-chris

[1] It's not quite a single kernel.  It's two separate binaries built from
the identical vmlinux.  This is due to the Xen domain builder's inability
to boot a bzImage format kernel binary.  Fixing this is on the todo list.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [ANNOUNCE] paravirt_ops i686 Fedora rawhide kernel packages, Chris Wright <=