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-users] xen and Debian kernel package

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen and Debian kernel package
From: Olaf <no_address_here@xxxxxxxxxxxxxxxxx>
Date: Sun, 12 Jun 2005 22:15:38 +0200
Delivery-date: Mon, 13 Jun 2005 09:41:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I'm about to roll a few machines out with xen and it's likely that I have to change the kernel configuration from the stock xenU kernel. What do you reckon, is it more efficient to compile a kernel on every machine using the 2.0.6-src archive or would it make sense to invest the time to figure out how to compile a kernel and modules using Debian's kernel package and deploy the packages? Could be that I'm totally on the wrong track, but I assume that I can use that to deploy modules and header files against the kernel I booted the vm from.

Any input is appreciated.


Xen-users mailing list

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