Hi there got Suse 10.1 RC3, can boot a domU. The problem is, I cannot setup any network inside domU. System: Athlon, 512M Ram, Dom0 on md0, DomU on LVM dmesg | grep eth netfront: Initialising virtual ethernet driver. eth0 renamed to eth5 var/log/messages May 4 10:25:58 base ifstatus: eth5 May 4 10:25:58 base ifstatus: No configuration found for eth5 in the config file for the dom I have: ... vif = [ ''mac=aa:cc:00:00:00:01, bridge=xenbr0'' ] ... There are no other network relevant settings I do have a suse 9.3 server with xen 2.07 and various domUs running. but the way networks needs to be setup in RC3 seems to be different. Did anyone get a DomU''s network up in RC3? 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
Hi, you need to delete all unnecessary lines in \"/etc/udev/rules.d/30-net_persistent_names.rules\" The problem is, that Xen generates a new random MAC if the MAC is not specified in the config file. I assume you started that domain without the MAC Parameter before. SuSE adds a new udev-rule for every MAC. Alternatively you can set the parameter FORCE_PERSISTENT_NAMES in \"/etc/sysconfig/network/config\" to no and delete the file \"/etc/udev/rules.d/30-net_persistent_names.rules\". HTH, -timo On Thu, 4 May 2006 10:49:45 +0200 (CEST), Chris Epicier <seuchato@yahoo.de> wrote:> Hi there > > got Suse 10.1 RC3, can boot a domU. The problem is, I > cannot setup any network inside domU. > > System: Athlon, 512M Ram, Dom0 on md0, DomU on LVM > > dmesg | grep eth > netfront: Initialising virtual ethernet driver. > eth0 renamed to eth5 > > var/log/messages > May 4 10:25:58 base ifstatus: eth5 > May 4 10:25:58 base ifstatus: No > configuration found for eth5 > > in the config file for the dom I have: > ... > vif = [ \''mac=aa:cc:00:00:00:01, bridge=xenbr0\'' ] > ... > There are no other network relevant settings > > I do have a suse 9.3 server with xen 2.07 and various > domUs running. but the way networks needs to be setup > in RC3 seems to be different. > > Did anyone get a DomU\''s network up in RC3? > > 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-- Timo Benk PGP Public Key: http://vs241071.vserver.de/timo_benk_gpg_key.asc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris Epicier
2006-May-04 11:37 UTC
[Xen-users] RE: Suse 10.1 RC3: cannot configure my nics
After digging a bit furthe in the lists here, I tried to look at xennet: lsmod Module Size Used by ipv6 275040 12 apparmor 59928 0 aamatch_pcre 19840 1 apparmor loop 20616 0 dm_mod 64080 0 reiserfs 253696 1 xenblk 20048 1 xennet 24320 0 so xennet is there, but not used. I also added aliases: cat /etc/modprobe.conf | grep eth ... install eth0 /bin/true install eth1 /bin/true install eth5 /bin/true alias eth0 xennet alias eth5 xennet ... still no ping to and from my domU greets chris> Hi there > > got Suse 10.1 RC3, can boot a domU. The problem is, > I > cannot setup any network inside domU. > > System: Athlon, 512M Ram, Dom0 on md0, DomU on LVM > > dmesg | grep eth > netfront: Initialising virtual ethernet driver. > eth0 renamed to eth5 > > var/log/messages > May 4 10:25:58 base ifstatus: eth5 > May 4 10:25:58 base ifstatus: No > configuration found for eth5 > > in the config file for the dom I have: > ... > vif = [ ''mac=aa:cc:00:00:00:01, bridge=xenbr0'' ] > ... > There are no other network relevant settings > > I do have a suse 9.3 server with xen 2.07 and > various > domUs running. but the way networks needs to be > setup > in RC3 seems to be different. > > Did anyone get a DomU''s network up in RC3? > > greets chris > > > > > > > > >___________________________________________________________> > Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher > kostenlos - Hier anmelden: http://mail.yahoo.de >___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris Epicier
2006-May-04 12:10 UTC
[Xen-users] Re: Re: Suse 10.1 RC3: cannot configure my nics
Timo>you need to delete all unnecessary lines in >\"/etc/udev/rules.d/30-net_persistent_names.rules\"Idid that, partial sucess: in yast I see now an interface which I can configure. but when I do actually configure it, yast says "das Gerät hat kein Treibermodul" (device has no driver module) As I continue, assign it an ip, still no ping to and from. I did add / remove the alias eth0 xennet in /ets/modprobe.conf: no success. I believe lsmod should count 1 for xennet and not 0. Thus my assumtion is: although the virtual nich is now seen, it is without a driver and thus must fail. Any idea? Chris ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users