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] Re: [ANNOUNCE] virtbench now has xen support

To: Jan Michael <jan.michael@xxxxxxx>
Subject: Re: [Xen-devel] Re: [ANNOUNCE] virtbench now has xen support
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 22 May 2007 10:33:34 +0100
Cc: Anthony Liguori <aliguori@xxxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 May 2007 02:31:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <6C46B0C9-2C62-431F-89C9-21A492E19DAD@xxxxxxx>
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>
References: <1179196706.27304.22.camel@xxxxxxxxxxxxxxxxxxxxx> <B8C22E46-2962-4702-A4DF-7A02CC576F5E@xxxxxxx> <464A0F01.5030900@xxxxxxxxxx> <B560AF89-CB82-4842-8B36-E2216A0D319D@xxxxxxx> <1179489064.17608.47.camel@xxxxxxxxxxxxxxxxxxxxx> <3C31E727-8C2D-4DBB-A16A-F40ADC0AE62A@xxxxxxx> <1179728188.20705.13.camel@xxxxxxxxxxxxxxxxxxxxx> <DB1C98A8-CBEE-44E3-99D5-BD74A413BB04@xxxxxxx> <1179791128.20705.30.camel@xxxxxxxxxxxxxxxxxxxxx> <6C46B0C9-2C62-431F-89C9-21A492E19DAD@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20070302)
Jan Michael wrote:
> I can say that we are using a kernel builf from the attached kernel
> config and a special initrd image for our domUs.
> The initrd image contains the modules xenblk.ko and xennet.ko. So
> netfront and blkfront are not compiled into the kernel.

Modular is OK if they're in the initrd you're using.

> Our linux gurus made the kernel and the initrd image. I think I have
> to integrate those modules into the initrd image you are using and
> have to load them. But at this point I have no knowledge how to do
> this...

It's distro-dependent, but mkinitrd works for RH-type systems. 
Something like "mkinitrd --with=xenblk --with=xennet -v my-initrd.img
<kernel version>".


Xen-devel mailing list