From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Michael <jan.michael@cern.ch>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Xen Mailing List <xen-devel@lists.xensource.com>
Subject: Re: Re: [ANNOUNCE] virtbench now has xen support
Date: Tue, 22 May 2007 10:33:34 +0100 [thread overview]
Message-ID: <4652B8EE.6070406@goop.org> (raw)
In-Reply-To: <6C46B0C9-2C62-431F-89C9-21A492E19DAD@cern.ch>
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>".
J
next prev parent reply other threads:[~2007-05-22 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 2:38 [ANNOUNCE] virtbench now has xen support Rusty Russell
2007-05-15 7:44 ` Jan Michael
2007-05-15 19:50 ` Anthony Liguori
2007-05-18 10:14 ` Jan Michael
2007-05-18 11:51 ` Rusty Russell
2007-05-18 17:56 ` Jan Michael
2007-05-21 6:16 ` Rusty Russell
2007-05-21 8:13 ` Jan Michael
2007-05-21 13:13 ` Jeremy Fitzhardinge
2007-05-21 23:45 ` Rusty Russell
2007-05-22 7:33 ` Jan Michael
2007-05-22 9:33 ` Jeremy Fitzhardinge [this message]
2007-05-23 18:05 ` Jan Michael
[not found] ` <157A1A05-C74F-4055-A71B-3068BFECB61E@cern.ch>
2007-05-24 16:11 ` Petersson, Mats
2007-06-09 3:19 ` Rusty Russell
[not found] ` <7C99B109-A4B0-4957-8583-E3C3651BCE1D@cern.ch>
2007-06-09 3:57 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4652B8EE.6070406@goop.org \
--to=jeremy@goop.org \
--cc=aliguori@us.ibm.com \
--cc=jan.michael@cern.ch \
--cc=rusty@rustcorp.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.