[Xen-users] Re: Re: Suse 10.1 RC3: cannot configure my nics: now solved!

[Chris Epicier <seuchato@xxxxxxxx>]

Hi Shimizu
--- Shimizu Miki <> schrieb:

> Hello,
> 
> Doesn't the vircual nic work at all?

After the hint of Timo
(http://lists.xensource.com/archives/html/xen-users/2006-05/msg00091.html)

I got the virtual xen network card show up in yast.
However, when I configured it, yast came up with an
error message that'no driver module for the device
found' (message loosely translated from german).

Now in DomU eth0 (no longer eth5) shows up and
ifconfig
returns:
eth0      Link encap:Ethernet  HWaddr
AA:CC:00:00:00:01
          inet addr:192.168.0.101  Bcast:192.168.0.255
 Mask:255.255.255.0
....

So one should expect pings to work but no:
base:~ # ping 192.168.0.99
PING 192.168.0.99 (192.168.0.99) 56(84) bytes of data.
>From 192.168.0.101: icmp_seq=1 Destination Host
Unreachable

At this stage I did disable firewalling completely.

I think, lsmod | grep xennet should return a module
count >= 1 but:
base:~ # lsmod | grep xen
xenblk                 20048  1
xennet                 24320  0

So my conclusion is: xennet is loaded but no instance
initialised, hence the yast error message.

could the error be in dom0?
brctl show
brctl show
bridge name     bridge id               STP enabled   
 interfaces
xenbr0          8000.feffffffffff       no            
 vif1.0

whereas in my suse 9.3 dom0
brctl show
bridge name     bridge id               STP enabled   
 interfaces
xen-br0         8000.000c76550535       no            
 eth0
                                                      
 vif1.0
                                                      
 vif4.0

So the eth0 is missing in the bridge

How can I fix this?
rcxend stop
ifdown vif1.0
ifdown xenbr0
brctl delif xenbr0 vif1.0
brctl delbr xenbr0
rcxend start
ifconfig now shows peth0, vif0.0 ... all as it should
dep breath and fire 
xm create base
ping 192.168.0.101 
PING 192.168.0.101 (192.168.0.101) 56(84) bytes of
data.
64 bytes from 192.168.0.101: icmp_seq=1 ttl=64
time=3.62 ms
64 bytes from 192.168.0.101: icmp_seq=2 ttl=64
time=0.214 ms

Yipee ai yeah!!!

I don't know whay I had to manually bring down the
bridge and connetcted if's and whay it does not work
when rebooting. But since its a server supposed to run
forever :-), I don't care too much.


> For example, how is it if you temporary configure it
> by
> 
> #ifconfig eth5 192.168.0.2
> 
> And for pinging, how is your firewall conditions?

thanks to all for your help. 


        

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

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