Chris Epicier
2005-May-26 10:34 UTC
Re: [Xen-users] Re: Problems building a xen0 kernel on Suse 9.3
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
Gerd Knorr
2005-May-27 09:32 UTC
Re: [Xen-users] Re: Problems building a xen0 kernel on Suse 9.3
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