RE: [Xen-users] dom0 networking not working, but domUs are!

["Kriz, Mike" <Mike_Kriz@xxxxxxx>]

 Have the same problem as Andrew with my Xen install: dom0 can not connect to other machine son the network, but the DomUs can.  The Domus and 0 can communicate

 

I’ve been trying to figure this out for a couple weeks with no luck.  We found that Andrew and I both have NetXtremeII based NICs, and I’ve read of other issues with those ICS, but the firmware upgrade did not help me.  Does anyone have any ideas on where to go next?

 

Here is my ifconfig:

 

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:14:5E:5A:28:B0

          inet addr:10.10.6.35  Bcast:0.0.0.0  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:536 errors:0 dropped:0 overruns:0 frame:0

          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:103587 (101.1 Kb)  TX bytes:10486 (10.2 Kb)

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:2 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:198 (198.0 b)  TX bytes:198 (198.0 b)

 

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:568 errors:0 dropped:0 overruns:0 frame:0

          TX packets:104 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:109118 (106.5 Kb)  TX bytes:13962 (13.6 Kb)

          Interrupt:21 Memory:e2000000-e2011100

 

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:78 errors:0 dropped:0 overruns:0 frame:0

          TX packets:543 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:12534 (12.2 Kb)  TX bytes:104049 (101.6 Kb)

 

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:182 errors:0 dropped:0 overruns:0 frame:0

          TX packets:610 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:32

          RX bytes:20448 (19.9 Kb)  TX bytes:116120 (113.3 Kb)

 

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:440 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:88129 (86.0 Kb)  TX bytes:0 (0.0 b)

 

---

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Andrew Ragusa
Sent: Wednesday, January 03, 2007 11:15 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] dom0 networking not working, but domUs are!

 

I've been playing with this for days, and searching around trying to figure out why this is not working.

 

I'm running redhat-4.4 with the 2.6.16-29-xen_3.0.3 kernel for dom0

 

when I installed I got an error saying that it was incompatable with lksctp-tools, but I went ahead and forced the install, everything seemed to work until I noticed dom0 networking was down.

 

The domU's can communicate with dom0, and the domUs can communicate with other machines on the network as I expected.  dom0 can only communicate within the domUs.

 

In my trouble shooting I managed to find that eth0 in dom0 has noqueue set when using the ip addr show eth0, I set it to qdisc pfifo and tried again still nothing.  

 

Is there something I am missing?

 

Andrew Ragusa

aragusa@xxxxxxxxxxx

 

---

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.

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