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

To: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [ANNOUNCE] virtbench now has xen support
From: Jan Michael <jan.michael@xxxxxxx>
Date: Tue, 22 May 2007 09:33:45 +0200
Cc: Anthony Liguori <aliguori@xxxxxxxxxx>, Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 May 2007 00:32:26 -0700
Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=cern.ch; q=dns; h=received:message-id:date:from:to:subject:mime-version:content-type; b=IgDoGs2Q7rykIyp8wuBlegDmaqPxzXJPYxMqYp5PKFhIgL5TT+b59FPcu/gYVFSHjt3L01KgSoUOWGZpdcv8zmXjjgxMEcv+bsa1nfhVXXBvwM5bOK7/qgPwR7Mrgtx4;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1179791128.20705.30.camel@xxxxxxxxxxxxxxxxxxxxx>
Keywords: CERN SpamKiller Note: -51 Charset: west-latin
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Rusty,

On 22.05.2007, at 01:45, Rusty Russell wrote:
On Mon, 2007-05-21 at 10:13 +0200, Jan Michael wrote:
Salut Rusty,

On 21.05.2007, at 08:16, Rusty Russell wrote:
Hmm, perhaps your kernel doesn't have INITRD support? The default Xen
kernel works (at least, for me on i386 it does)...

Hm. No. Unfortunately the kernel I'm using has INITRD support,

Hi Jan!

        Hmm, it has found the initrd, and ramdisk seems to be there.  Any
chance you can send your kernel config?  Obviously we want it to "just
work" with whatever configs it can...

Sure. No problem. Please find attached our kernel config for domUs.
Did you see the mail from Jeremy?

On 21.05.2007, at 15:13, Jeremy Fitzhardinge wrote:
    66    XENBUS: Device with no driver: device/vbd/51713
    67    XENBUS: Device with no driver: device/vif/0

looks worrysome. Do you have netfront and blkfront compiled into (your
kernel, either built-in or as modules in your initrd)?

Though it seems you have a more basic problem with mounting the initrd.

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. 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...



Attachment: config-2.6.9-42.0.3.EL.cernxenU
Description: Binary data

Xen-devel mailing list