[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] Networking problems on opensuse 10.3 (Closed)
Hi, Finally I got the solution. It is very simple. I just need to update my e1000 driver! The built-in e1000 version 7.6.5 has the problem. So I upgrade it to 7.6.15.4. After reboot, I got peth0, vif0.0, xenbr0 ....everything that didn't come out before. And I can access the Internet now. http://lists.xensource.com/archives/html/xen-users/2007-08/msg00839.html So if you got the similar problem as the above link and mine, you can try to upgrade your driver. That might work. Thanks for all the helps. Regards, - Tommy ---------------------------------------- > From: tommy24@xxxxxxxx > To: xen-users@xxxxxxxxxxxxxxxxxxx > Date: Mon, 22 Sep 2008 19:44:33 -0700 > Subject: [Xen-users] Networking problems on opensuse 10.3 > > > Hi, > > I am still stuck with the network problem. > I searched the archive of maling list and found an user has the same problem. > http://lists.xensource.com/archives/html/xen-users/2007-08/msg00839.html > And the reply suggests to execute "ethtool -K eth0 tx off " > When I executed it, nothing happens. Should I execute this command at boot > time? > How can I do that? > So I didn't get the answer from that thread. > Here is my output of ifconfig: > > eth0 Link encap:Ethernet HWaddr 00:30:48:63:72:76 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:9624 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4042 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:3466249 (3.3 Mb) TX bytes:799201 (780.4 Kb) > Base address:0x2000 Memory:d8020000-d8040000 > > 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:150 errors:0 dropped:0 overruns:0 frame:0 > TX packets:150 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:10904 (10.6 Kb) TX bytes:10904 (10.6 Kb) > > xenbr0 Link encap:Ethernet HWaddr 00:30:48:63:72:76 > inet addr:143.215.206.12 Bcast:143.215.207.255 Mask:25Actually, I > want to make domains can communicate with each other, suck like uploading > files to another domain. I really don't know how to achieve this without > bridging.5.255.252.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:5626 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2024 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0Actually, I want to make domains can > communicate with each other, suck like uploading files to another domain. I > really don't know how to achieve this without bridging. > RX bytes:1621821 (1.5 Mb) TX bytes:399985 (390.6 Kb) > > As you can see, no peth0 and vif0.0. > > The output of brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.003048637276 no eth0 > > No vif interface. > > Does anyone have the same problem? > This problem is quite annoying. > Actually, I want to make domains can communicate with each other, suck like > uploading files from Dom 0 to Dom 1. I really don't know how to achieve this > without bridging. > If you have any workaround solution, please kindly let me know. > I have to use opensuse 10.3 with xen. No other limitations. > Any response is appreciated. Thanks again. > _________________________________________________________________ > Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. > http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008 > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users _________________________________________________________________ See how Windows Mobile brings your life together—at home, work, or on the go. http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/ _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |