Re: [Xen-users] Networks stops after running xend start

[Ryan <niespam@xxxxxxxxx>]

Mike,

I don't have an answer to your question, but you may want to try /etc/rc.d/init.d/network restart instead of rebooting (if you're running redhat, that is). 

Have Fun,
Ryan

On 1/27/07, Mike Lee <cslinuxboy@xxxxxxxxx > wrote:

Hello Everyone,

     I have successfully installed Xen 3.0.3 (x86_64) tar binaries on my Dell 2900 server.  I also have successfully configured and installed a guest domain.  However,  after the 'xend start' script is ran, I lose all networking.  And if I run 'xend stop' all of the devices associated with a bridged setup are still present (xenbr0, peth0, vif0.0, etc.) and my networking is still not working.  The only way to get the network back is to reboot (I don't have xend configured to start on startup).  Below is the output of ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:18:8B:36:98:D1
          inet addr:192.168.50.2  Bcast: 192.168.50.255  Mask:255.255.255.0
          inet6 addr: fe80::218:8bff:fe36:98d1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1018 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:61080 (59.6 KiB)  TX bytes:4004 (3.9 KiB)

lo        Link encap:Local Loopback
          inet addr: 127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1032 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1032 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1201624 (1.1 MiB)  TX bytes:1201624 (1.1 MiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1061 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:69358 (67.7 KiB)  TX bytes:4330 (4.2 KiB)
          Interrupt:16 Memory:f8000000-f8011100

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1018 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4004 (3.9 KiB)  TX bytes:61080 (59.6 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1030 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:47380 (46.2 KiB)  TX bytes:0 ( 0.0 b)

     I have searched hi and low for a solution and cannot get a break.  Like I stated above, my configuration is bridged.  I have read the networking doco on the xen wiki and all looks good.  Also, I have looked at the xen logs and everything looks fine with no errors or warnings.  My network card is a Broadcom NetXtreme II BCM5708 Gigabit.  What am I doing wrong? 
     Another question I have is why does peth0 not have the ethernet address of the actual physical card, but eth0 for dom0 does?  Could this be the cause?  Is the xend script broken?  I installed the bridging tools also. 
     Thanks in advance.

Mike

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

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