Mailing List Archive

Jeff,

OK - I hadn't realised SuSE were shipping the standard kernel source
package with the xen patches already applied.

I've just tried a build of the tree extracted from that RPM on my FC3 box
- it appears to build fine. I'll check on a SuSe box tomorrow - access
isn't practical right now.

James

On Mon, May 23, 2005 6:01 pm, Jeffrey Buell said:
> James,
>
> Not much chance of insulting my intelligence here. I have been using Xen
> as
> part of the Fedora core 4 development releases, but I'm new to SuSE 9.3.
> In
> FC4 I use the source RPMs (for both the kernel and Xen) as supplied by
> Fedora, and I'd like to do the same with SuSE, using source from the
> installation CDs. I didn't need to install any source RPM in order to
> build
> the regular kernel. Does Xen need something extra not installed by SuSE?
> I'm not sure if I'm "building a xen kernel tree". In FC4 the xen kernels
> are
> built in the same way and same directory as the regular kernel. I just
> need
> ARCH=xen and a xen config file. Is the procedure different in SuSE?
>
> Thanks for your help,
>
> Jeff
>
>>
>> Jeff,
>>
>> Please don't take this the wrong way, I don't mean to insult your
>> intelligence - are you sure you're building a xen kernel tree
>> rather than
>> the native (ARCH=xen will not work on the latter). Presumably
>> this is the
>> SuSE source RPM rather than one of our tarball or BK
>> distributions? Could
>> be an issue with the location that the RPM installs the source to.
>>
>> Regards,
>>
>> James
>> (will be offline from now until tomorrow)
>>
>> On Fri, May 20, 2005 11:03 pm, Jeffrey Buell said:
>> > I installed Suse 9.3 Pro along with all the kernel tools
>> and sources. I
>> > was
>> > easily able to build a new regular kernel, but not a xen0
>> kernel. With
>> > ARCH=xen and using the supplied config file, "make" almost
>> immediately
>> > runs
>> > into problems creating links to various asm directories in the
>> > kernel/build
>> > dir. I fixed this by copying all of /usr/src/linux into
>> kernel/build.
>> > Everything then compiled but I got 2 undefined references:
>> teardown_irq
>> > in
>> > ctrl_if_suspend, and kmap_flush_unused in balloon_process.
>> Presumably
>> > there
>> > is no bug since a working xen0 kernel was supplied in the
>> distro. What do
>> > people do differently when building a xen0 kernel vs. a
>> regular kernel?
>> >
>> > Jeff
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>



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

On Tue, May 24, 2005 1:59 am, James Bulpin said:
> I've just tried a build of the tree extracted from that RPM on my FC3 box
> - it appears to build fine. I'll check on a SuSe box tomorrow - access
> isn't practical right now.

I tried the following on an out-of-the-box SuSE 9.3 install:

rpm --install /tmp/kernel-source-2.6.11.4-20a.i586.rpm
cd /usr/src/linux (symlinks to linux-2.6.11.4-20a)
cp ./arch/i386/defconfig.xen .config
make ARCH=xen oldconfig
make ARCH=xen

It got a good way through the build and only stopped due to an unrelated
problem.

Can you post the actual errors you saw?

Regards,

James

> On Mon, May 23, 2005 6:01 pm, Jeffrey Buell said:
>> James,
>>
>> Not much chance of insulting my intelligence here. I have been using
>> Xen
>> as
>> part of the Fedora core 4 development releases, but I'm new to SuSE 9.3.
>> In
>> FC4 I use the source RPMs (for both the kernel and Xen) as supplied by
>> Fedora, and I'd like to do the same with SuSE, using source from the
>> installation CDs. I didn't need to install any source RPM in order to
>> build
>> the regular kernel. Does Xen need something extra not installed by
>> SuSE?
>> I'm not sure if I'm "building a xen kernel tree". In FC4 the xen
>> kernels
>> are
>> built in the same way and same directory as the regular kernel. I just
>> need
>> ARCH=xen and a xen config file. Is the procedure different in SuSE?
>>
>> Thanks for your help,
>>
>> Jeff
>>
>>>
>>> Jeff,
>>>
>>> Please don't take this the wrong way, I don't mean to insult your
>>> intelligence - are you sure you're building a xen kernel tree
>>> rather than
>>> the native (ARCH=xen will not work on the latter). Presumably
>>> this is the
>>> SuSE source RPM rather than one of our tarball or BK
>>> distributions? Could
>>> be an issue with the location that the RPM installs the source to.
>>>
>>> Regards,
>>>
>>> James
>>> (will be offline from now until tomorrow)
>>>
>>> On Fri, May 20, 2005 11:03 pm, Jeffrey Buell said:
>>> > I installed Suse 9.3 Pro along with all the kernel tools
>>> and sources. I
>>> > was
>>> > easily able to build a new regular kernel, but not a xen0
>>> kernel. With
>>> > ARCH=xen and using the supplied config file, "make" almost
>>> immediately
>>> > runs
>>> > into problems creating links to various asm directories in the
>>> > kernel/build
>>> > dir. I fixed this by copying all of /usr/src/linux into
>>> kernel/build.
>>> > Everything then compiled but I got 2 undefined references:
>>> teardown_irq
>>> > in
>>> > ctrl_if_suspend, and kmap_flush_unused in balloon_process.
>>> Presumably
>>> > there
>>> > is no bug since a working xen0 kernel was supplied in the
>>> distro. What do
>>> > people do differently when building a xen0 kernel vs. a
>>> regular kernel?
>>> >
>>> > Jeff
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>



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

James,

I did exactly the same thing as you did, except I skipped your initial rpm
command (but rpm -qa confirms I have the right source). In the end I got the
same undefined references as before. Hopefully you can fix your "unrelated
problems" so we can see if this is a SUSE/Xen problem or not. An unrelated
issue is using the O= option to relocate the build output to a different
directory. Do you ever use this? This works fine for the regular kernel but
causes an immediate failure when building a Xen kernel (missing asm
directories).

Jeff

# rpm -qa | grep source
kernel-source-2.6.11.4-20a
# make ARCH=xen

<everything compiles>

CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
arch/xen/kernel/built-in.o(.text+0x85b): In function `ctrl_if_suspend':
: undefined reference to `teardown_irq'
drivers/built-in.o(.text+0x4b2c7): In function `balloon_process':
balloon.c: undefined reference to `kmap_flush_unused'
make: *** [.tmp_vmlinux1] Error 1


>
> On Tue, May 24, 2005 1:59 am, James Bulpin said:
> > I've just tried a build of the tree extracted from that RPM
> on my FC3 box
> > - it appears to build fine. I'll check on a SuSe box
> tomorrow - access
> > isn't practical right now.
>
> I tried the following on an out-of-the-box SuSE 9.3 install:
>
> rpm --install /tmp/kernel-source-2.6.11.4-20a.i586.rpm
> cd /usr/src/linux (symlinks to linux-2.6.11.4-20a)
> cp ./arch/i386/defconfig.xen .config
> make ARCH=xen oldconfig
> make ARCH=xen
>
> It got a good way through the build and only stopped due to
> an unrelated
> problem.
>
> Can you post the actual errors you saw?
>
> Regards,
>
> James
>
> > On Mon, May 23, 2005 6:01 pm, Jeffrey Buell said:
> >> James,
> >>
> >> Not much chance of insulting my intelligence here. I have
> been using
> >> Xen
> >> as
> >> part of the Fedora core 4 development releases, but I'm
> new to SuSE 9.3.
> >> In
> >> FC4 I use the source RPMs (for both the kernel and Xen) as
> supplied by
> >> Fedora, and I'd like to do the same with SuSE, using
> source from the
> >> installation CDs. I didn't need to install any source RPM
> in order to
> >> build
> >> the regular kernel. Does Xen need something extra not installed by
> >> SuSE?
> >> I'm not sure if I'm "building a xen kernel tree". In FC4 the xen
> >> kernels
> >> are
> >> built in the same way and same directory as the regular
> kernel. I just
> >> need
> >> ARCH=xen and a xen config file. Is the procedure
> different in SuSE?
> >>
> >> Thanks for your help,
> >>
> >> Jeff
> >>
> >>>
> >>> Jeff,
> >>>
> >>> Please don't take this the wrong way, I don't mean to insult your
> >>> intelligence - are you sure you're building a xen kernel tree
> >>> rather than
> >>> the native (ARCH=xen will not work on the latter). Presumably
> >>> this is the
> >>> SuSE source RPM rather than one of our tarball or BK
> >>> distributions? Could
> >>> be an issue with the location that the RPM installs the source to.
> >>>
> >>> Regards,
> >>>
> >>> James
> >>> (will be offline from now until tomorrow)
> >>>
> >>> On Fri, May 20, 2005 11:03 pm, Jeffrey Buell said:
> >>> > I installed Suse 9.3 Pro along with all the kernel tools
> >>> and sources. I
> >>> > was
> >>> > easily able to build a new regular kernel, but not a xen0
> >>> kernel. With
> >>> > ARCH=xen and using the supplied config file, "make" almost
> >>> immediately
> >>> > runs
> >>> > into problems creating links to various asm directories in the
> >>> > kernel/build
> >>> > dir. I fixed this by copying all of /usr/src/linux into
> >>> kernel/build.
> >>> > Everything then compiled but I got 2 undefined references:
> >>> teardown_irq
> >>> > in
> >>> > ctrl_if_suspend, and kmap_flush_unused in balloon_process.
> >>> Presumably
> >>> > there
> >>> > is no bug since a working xen0 kernel was supplied in the
> >>> distro. What do
> >>> > people do differently when building a xen0 kernel vs. a
> >>> regular kernel?
> >>> >
> >>> > Jeff

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

Hi there

I can confirm what Jeff is writing:

Used yast to install the kernel source, online_updated
(still no kernel updates despite the raid problems in
suse :-()

then I did:

cd /usr/src/linux
cp ./arch/i386/defconfig.xen .config
make ARCH=xen menuconfig (changed a few unneeded
features and added an index, saved .config)
make ARCH=xen oldconfig (just to verify)
make ARCH=xen

I did this to overcome problems booting 9.3 from raid
1, which is still not really resolved (see thread "xen
on suse 9.3 and software raid" on xen-user and
xen-devel)

I also tried the KOTD:
ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/kernel-xen-2.6.11.10-20050523173601.i586.rpm
but that dos not solve the issues with raid1 neither.
I think, Suse kernels are broke with the exception of
2.6.8 from http://www.suse.de/~garloff/linux/xen/. but
this has other issues and no source unfortunately to
remove these.

So I am still waiting for the people at suse to
support us. It would just be a great thing though:
Yast to setup your DomU's is just nice!

good luck

chris






___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

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

Following up my previous post and searching around a
bit, Itried the following:

cd /usr/src/linux
make mrproper
./arch/i386/defconfig.xen .config
make ARCH=xen menuconfig (I just change general
setup-> Local version)
make ARCH=xen prepare

make: Zirkuläre Datei
/usr/src/linux-2.6.11.4-20a/include/asm <-
/usr/src/linux-2.6.11.4-20a/include/asm Abhängigkeit
wird nicht verwendet.
SYMLINK /usr/src/linux-2.6.11.4-20a/include/asm ->
include/asm-xen
SYMLINK include/asm -> include/asm-i386
SPLIT include/linux/autoconf.h -> include/config/*
HOSTCC scripts/genksyms/genksyms.o
SHIPPED scripts/genksyms/lex.c
SHIPPED scripts/genksyms/parse.h
SHIPPED scripts/genksyms/keywords.c
HOSTCC scripts/genksyms/lex.o
SHIPPED scripts/genksyms/parse.c
HOSTCC scripts/genksyms/parse.o
HOSTLD scripts/genksyms/genksyms
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
HOSTCC scripts/bin2c
CHK include/linux/version.h
UPD include/linux/version.h
CC arch/i386/kernel/asm-offsets.s
CHK include/asm-i386/asm_offsets.h
UPD include/asm-i386/asm_offsets.h

there are symlinks in ./include which I do not
understand:
~.asm-ignore -> asm-xen (delete or not?)
~asm -> asm-i386 (shouldn't that point to asm-xen?)

nevertheless I continue:
make ARCH=xen
CHK include/linux/version.h
SYMLINK include/asm -> include/asm-i386
make[1]: »arch/i386/kernel/asm-offsets.s« ist bereits
aktualisiert.
...
...
arch/xen/kernel/ctrl_if.c:466: warning: implicit
declaration of function `teardown_irq'
...
-so it uses code from xen, but throws warnings on what
it's gonna fail at the end, meanwhile...
...
CC [M] fs/befs/datastream.o
In file included from fs/befs/befs.h:11,
from fs/befs/datastream.c:18:
fs/befs/befs_fs_types.h:21:1: warning: "PACKED"
redefined
In file included from
include/asm-xen/xen-public/xen.h:13,
...
-lots of similar warnings that do not look
promising:...
include/asm-xen/xen-public/arch-x86_32.h:14:1:
warning: this is the location of the previous
definition
CC [M] fs/reiser4/plugin/item/extent_item_ops.o
In file included from
fs/reiser4/plugin/plugin_header.h:11,
from
fs/reiser4/plugin/item/item.h:17,
from
fs/reiser4/plugin/item/extent_item_ops.c:3:
fs/reiser4/dformat.h:44:1: warning: "PACKED" redefined
In file included from
include/asm-xen/xen-public/xen.h:
...


next I removed support for reiserfs4 and BeFs, same
results

Any hints?

Greets chris








___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

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

Chris Epicier write on Wed, 25 May 2005 11:49:23 +0200 (CEST):
> I also tried the KOTD:
> ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/kernel-xen-2.6.11.10-20050523173601.i586.rpm
> but that dos not solve the issues with raid1 neither.

Have you seen Gert Knorr's reply to Xen-users?
http://lists.xensource.com/archives/html/xen-users/2005-05/msg00443.html

Thank you Gert!

I think you are on the right track using KOTD, but are you aware that
that you need two pieces to get sources that you can build the SuSE
Xen kernel from?


ftp://your.suse.mirror.here/pub/projects/kernel/kotd/i386/HEAD/kernel-xen-2.6.11.10-20050524103609.abuild-extra.tar.gz

ftp://your.suse.mirror.here/pub/projects/kernel/kotd/i386/HEAD/kernel-source-2.6.11.10-20050524103609.src.rpm

In fact I tried using the stuff in following place
instead:
ftp://your.suse.mirror.here/pub/projects/kernel/kotd/9.3-i386/SL93_BRANCH/

i.e. not kernel-source-<version>.i586.rpm
but kernel-source-<version>.src.rpm
and kernel-xen-<version>.abuild-extra.tar.gz

you need to do

rpm -i kernel-source-<version>.src.rpm
cat kernel-xen-<version>.abuild-extra.tar.gz | \
(cd /usr/src/packages/SOURCE/ && tar xf - )

Then either build using rpmbuild and the kernel-xen.spec file
or manually with make ARCH=xen config ; make ARCH=xen

Remember to set CONFIG_BLK_DEV_MD=y

I am busy compiling this at the moment :)

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

Robbie Dinn <robbie@microbus.com> writes:

> In fact I tried using the stuff in following place
> instead:
> ftp://your.suse.mirror.here/pub/projects/kernel/kotd/9.3-i386/SL93_BRANCH/

> Remember to set CONFIG_BLK_DEV_MD=y

Not sure how often this is updated, but I think tomorrow that place
should have binary rpms configured with CONFIG_BLK_DEV_MD=y

Gerd


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

Dear Robbie


> Have you seen Gert Knorr's reply to Xen-users?
Yes, but I could not do anything with it, now I can!

>
>http://lists.xensource.com/archives/html/xen-users/2005-05/msg00443.html
>
> Thank you Gert!
>
> I think you are on the right track using KOTD, but
> are you aware that
> that you need two pieces to get sources that you can
> build the SuSE
> Xen kernel from?

No I was not, so thanks alot!
>
>
ftp://your.suse.mirror.here/pub/projects/kernel/kotd/i386/HEAD/kernel-xen-2.6.11.10-20050524103609.abuild-extra.tar.gz
>
>
ftp://your.suse.mirror.here/pub/projects/kernel/kotd/i386/HEAD/kernel-source-2.6.11.10-20050524103609.src.rpm
>
> In fact I tried using the stuff in following place
> instead:
>
>
ftp://your.suse.mirror.here/pub/projects/kernel/kotd/9.3-i386/SL93_BRANCH/

I just downloaded
kernel-source-2.6.11.4-SL93_BRANCH_20050525084504.src.rpm
kernel-xen-2.6.11.4-SL93_BRANCH_20050525084504.abuild-extra.tar.gz
...

> i.e. not kernel-source-<version>.i586.rpm
> but kernel-source-<version>.src.rpm
> and kernel-xen-<version>.abuild-extra.tar.gz
>
> you need to do
>
> rpm -i kernel-source-<version>.src.rpm
> cat kernel-xen-<version>.abuild-extra.tar.gz | \
> (cd /usr/src/packages/SOURCE/ && tar xf - )

here I am stuck:
1. I only have /usr/src/packages/SOURCES/
^ (typo?)
2. the cat ... command line bails out:
cat kernel-xen-....abuild-extra.tar.gz | (cd
/usr/src/packages/SOURCES/ && tar xf - )
tar: Archive is compressed. Use -z option
tar: Error is not recoverable: exiting now

You might see from this: I am no linux guru
Any help on this?

> Then either build using rpmbuild and the
> kernel-xen.spec file
> or manually with make ARCH=xen config ; make
> ARCH=xen
>
> Remember to set CONFIG_BLK_DEV_MD=y
>
> I am busy compiling this at the moment :)

I'd love to be too!

greets chris and thanks for your and Gerd's help so
far






___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

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

Chris Epicier wrote:
> I just downloaded
> kernel-source-2.6.11.4-SL93_BRANCH_20050525084504.src.rpm
> kernel-xen-2.6.11.4-SL93_BRANCH_20050525084504.abuild-extra.tar.gz
> ...
[snip]
> Robbie Dinn wrote:
>>you need to do
>>
>>rpm -i kernel-source-<version>.src.rpm
>>cat kernel-xen-<version>.abuild-extra.tar.gz | \
>> (cd /usr/src/packages/SOURCE/ && tar xf - )
>
>
> here I am stuck:

Ah sorry, my fault, I gave crap advice.
If you are not desperate to compile a customised
kernel, it might be easier to follow Gerd's advice
and wait for the kernel binary to appear in the place
he described in the sibling thread. It might be
quicker too, it takes several hours to build a kernel
with all the CONFIG options tunred on!

> 1. I only have /usr/src/packages/SOURCES/
> ^ (typo?)
yes typo.

> 2. the cat ... command line bails out:
> cat kernel-xen-....abuild-extra.tar.gz | (cd
> /usr/src/packages/SOURCES/ && tar xf - )
> tar: Archive is compressed. Use -z option
> tar: Error is not recoverable: exiting now
>
Ah, it's a gzip'ed tar file and I forgot to
tell you to uncompress it. I should have said
either to use zcat or specified 'tar zxf'

> You might see from this: I am no linux guru
> Any help on this?
Ok, trying to avoid more errors, here is the command
line again

rpm -i kernel-source-<version>.src.rpm
cat kernel-xen-<version>.abuild-extra.tar.gz | \
(cd /usr/src/packages/SOURCES/ && tar zxf - )

Now you need to learn a little bit about building
rpm files. When you get time, do 'man rpmbuild' and
read up on rpm. Maybe look at a few '.spec' files
which contain the build instruction for making an
rpm binary file.

The spec file we are interested is in
/usr/src/packages/SOURCES/kernel-xen.spec
There are lots of other spec files in the same
directory, although the more usual place to find
them is in /usr/src/packages/SPECS/

Here is a command line that will do a partial
build (called %prep stage) of the rpm build.

rpmbuild -bp /usr/src/packages/SOURCES/kernel-xen.spec

This will unpack the sources, apply any patches that
have been specified and leave a kernel source tree in
/usr/src/packages/BUILD/kernel-xen-2.6.11.4/linux-2.6.11

There will also be a kernel config file in
/usr/src/packages/BUILD/kernel-xen-2.6.11.4/config/i386/xen

you need to copy this config file to the .config file in
the base of the kernel source tree. Then do

make ARCH=xen oldconfig
make ARCH=xen menuconfig
# edit CONFIG variables as you wish
make ARCH=xen

I hope these instructions contain fewer errors that my last
attempt.

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

Dear Robbie
> Ah sorry, my fault, I gave crap advice.
never mind, it helped a lot...

> If you are not desperate to compile a customised
> kernel, it might be easier to follow Gerd's advice
> and wait for the kernel binary to appear in the
> place
> he described in the sibling thread.
To show you how desperate I am :-) :
got
kernel-xen-2.6.11.4-SL93_BRANCH_20050525084504.i586.rpm
did a yast -i with it, booted into xen and
HELL: IT WORKS YIPEE!!

uname -a
Linux julius2 2.6.11.4-SL93_BRANCH_20050525084504-xen
cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 hdb3[1]
54155008 blocks [2/1] [_U]

md0 : active raid1 hdb2[1]
4192896 blocks [2/1] [_U]

(I removed the 2nd disk for the time being)


> It might be
> quicker too, it takes several hours to build a
> kernel
> with all the CONFIG options tunred on!
I'll take the chance anyway, cause I do not need a lot
of features and to get to a higher knwoledge level
too, so thanks for your instructions. I'll report back
when done/doing.

While playing with my xen setup I noticed the
following:
Under default kernel, I could set the nics to a config
of my taste, ie: eth-int (internal) and eth-ext
(exzternal). Booting into xen, yast came up mentioning
ot had found new hardware: the nics, but in reversed
order! So I could not ping or remote ssh into the
xenbox. I had to name the nics eth0 and eth1, other
did not work. like this, it survives a reboot too.

Don't know if this is of interest at all or should go
into a new thread.

Anyway Thanks a lot

chris




___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

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

Chris Epicier <seuchato@yahoo.de> writes:

> While playing with my xen setup I noticed the
> following:
> Under default kernel, I could set the nics to a config
> of my taste, ie: eth-int (internal) and eth-ext
> (exzternal). Booting into xen, yast came up mentioning
> ot had found new hardware: the nics, but in reversed
> order! So I could not ping or remote ssh into the
> xenbox. I had to name the nics eth0 and eth1, other
> did not work. like this, it survives a reboot too.

Hmm, by default the nics are identified by mac address, so the module
load order shouldn't matter ...

You can also explicitly add the nic modules to INITRD_MODULES (in
/etc/sysconfig/kernel), then rerun mkinitrd. That should make sure
the modules loaded by the initrd in the order specified, thus giving
fixed names to the interfaces.

Gerd

--
-mm seems unusually stable at present.
-- akpm about 2.6.12-rc3-mm3

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