Hi List, I face troubles while just using the xen-enabled kernel in Kubuntu Hardy (8.04). I just don''t have no network at all. If I run ifconfig I see the peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one called "tempbr0" or so. But all of them are down. I can''t tell exactly as I have to reboot and use another kernel to get network access back... peth0 has got my 192.168.1.2 address and is set up as default gateway. But no ping and telnet works. It just doesn''t forward my packets to the router as it seems... Any ideas? Cheers, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Spies pisze:> Hi List, > > I face troubles while just using the xen-enabled kernel in Kubuntu Hardy > (8.04). I just don''t have no network at all. If I run ifconfig I see the > peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one > called "tempbr0" or so. But all of them are down. I can''t tell exactly as I > have to reboot and use another kernel to get network access back... > > peth0 has got my 192.168.1.2 address and is set up as default gateway. But no > ping and telnet works. It just doesn''t forward my packets to the router as it > seems... > > Any ideas? > > Cheers, > Daniel > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Hi Try used this kernel -> http://downloads.howtoforge.com/ubuntu_8.04_server_xen_from_repositories/ Albert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, May 10, 2008 at 11:23 AM, Daniel Spies <daniel.spies@fuceekay.com> wrote:> Hi List, > > I face troubles while just using the xen-enabled kernel in Kubuntu Hardy > (8.04). I just don''t have no network at all. If I run ifconfig I see the > peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one > called "tempbr0" or so. But all of them are down. I can''t tell exactly as I > have to reboot and use another kernel to get network access back... > > peth0 has got my 192.168.1.2 address and is set up as default gateway. But > no > ping and telnet works. It just doesn''t forward my packets to the router as > it > seems... > > Any ideas? >Try running /etc/xen/scripts/network-bridge start manually. You may need to clean out the tmpbr0 manually. to do that use: brctl show ifconfig tmpbr0 down brctl delif <any interface on that bridge> brctl delbr tmpbr0 Albert''s suggest is a good one since you will run into the domU network problem at some point if you don''t use those fixed kernels Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 10 May 2008 17:27:41 Albert wrote:> Daniel Spies pisze: > > Hi List, > > > > I face troubles while just using the xen-enabled kernel in Kubuntu Hardy > > (8.04). I just don''t have no network at all. If I run ifconfig I see the > > peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one > > called "tempbr0" or so. But all of them are down. I can''t tell exactly as > > I have to reboot and use another kernel to get network access back... > > > > peth0 has got my 192.168.1.2 address and is set up as default gateway. > > But no ping and telnet works. It just doesn''t forward my packets to the > > router as it seems... > > > > Any ideas? > > > > Cheers, > > Daniel > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > Hi > > Try used this kernel -> > http://downloads.howtoforge.com/ubuntu_8.04_server_xen_from_repositories/ > > Albert > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersDid that, no change... Thanks anyway, as Todd said it will prevent domU networking problems... Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 10 May 2008 17:30:51 Todd Deshane wrote:> On Sat, May 10, 2008 at 11:23 AM, Daniel Spies <daniel.spies@fuceekay.com> > > wrote: > > Hi List, > > > > I face troubles while just using the xen-enabled kernel in Kubuntu Hardy > > (8.04). I just don''t have no network at all. If I run ifconfig I see the > > peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one > > called "tempbr0" or so. But all of them are down. I can''t tell exactly as > > I have to reboot and use another kernel to get network access back... > > > > peth0 has got my 192.168.1.2 address and is set up as default gateway. > > But no > > ping and telnet works. It just doesn''t forward my packets to the router > > as it > > seems... > > > > Any ideas? > > Try running /etc/xen/scripts/network-bridge start manually. > > You may need to clean out the tmpbr0 manually. > > to do that use: > brctl show > ifconfig tmpbr0 down > brctl delif <any interface on that bridge> > brctl delbr tmpbr0 > > Albert''s suggest is a good one since you will > run into the domU network problem at some > point if you don''t use those fixed kernels > > Cheers, > ToddWhat I did before was trying the /etc/xen/scripts/network-bridge restart and it tells me somehting about "device busy" and "peth0 not configured". If I do a "ifconfig peth0 down" and rerun the script it doesn''t output anything. But if I rerun it again, the same error appears... I''ll try the second part in a minute, need to reboot again :( Cheers, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 10 May 2008 17:49:40 Daniel Spies wrote:> > > > Try running /etc/xen/scripts/network-bridge start manually. > > > > You may need to clean out the tmpbr0 manually. > > > > to do that use: > > brctl show > > ifconfig tmpbr0 down > > brctl delif <any interface on that bridge> > > brctl delbr tmpbr0 > > > > Albert''s suggest is a good one since you will > > run into the domU network problem at some > > point if you don''t use those fixed kernels > > > > Cheers, > > Todd > > What I did before was trying the /etc/xen/scripts/network-bridge restart > and it tells me somehting about "device busy" and "peth0 not configured". > If I do a "ifconfig peth0 down" and rerun the script it doesn''t output > anything. But if I rerun it again, the same error appears... > > I''ll try the second part in a minute, need to reboot again :(Okay, now I have the local network back, but what now? This is the current state: irrlicht@home:~$ ifconfig -a 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:55 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4155 (4.0 KB) TX bytes:4155 (4.0 KB) peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:20196 errors:0 dropped:0 overruns:0 frame:0 TX packets:14388 errors:0 dropped:0 overruns:0 carrier:2 collisions:0 txqueuelen:1000 RX bytes:21625055 (20.6 MB) TX bytes:1178441 (1.1 MB) veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) If I start /etc/xen/scripts/network-bridge start I get back the "tmpbridge" and the messages: irrlicht@home:~$ sudo /etc/xen/scripts/network-bridge start ifdown: interface peth0 not configured RTNETLINK answers: Device or resource busy That doesn''t kill my network anymore, but what to do next? THanks, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Okay, now I have the local network back, but what now? This is the current > state: > > irrlicht@home:~$ ifconfig -a > 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:55 errors:0 dropped:0 overruns:0 frame:0 > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4155 (4.0 KB) TX bytes:4155 (4.0 KB) > > peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:20196 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14388 errors:0 dropped:0 overruns:0 carrier:2 > collisions:0 txqueuelen:1000 > RX bytes:21625055 (20.6 MB) TX bytes:1178441 (1.1 MB) > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > If I start /etc/xen/scripts/network-bridge start I get back the "tmpbridge" > and the messages: > irrlicht@home:~$ sudo /etc/xen/scripts/network-bridge start > ifdown: interface peth0 not configured > RTNETLINK answers: Device or resource busy > > That doesn''t kill my network anymore, but what to do next? >Are you using network manager? Did you try putting a manual entry in your /etc/network/interfaces file? See: http://ubuntuforums.org/showthread.php?t=651078 and also only similar problem that should already be fixed: https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/192294 Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > > There was a post somewhere about deleting the xen state directory. This > got rid of my tmpbridge . > > Which state directory? do you have a link to the post by chance?Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 10 May 2008 19:39:30 Todd Deshane wrote:> > Okay, now I have the local network back, but what now? This is the > > current state: > > > > irrlicht@home:~$ ifconfig -a > > 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:55 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:4155 (4.0 KB) TX bytes:4155 (4.0 KB) > > > > peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 > > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > > inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:20196 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:14388 errors:0 dropped:0 overruns:0 carrier:2 > > collisions:0 txqueuelen:1000 > > RX bytes:21625055 (20.6 MB) TX bytes:1178441 (1.1 MB) > > > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > If I start /etc/xen/scripts/network-bridge start I get back the > > "tmpbridge" and the messages: > > irrlicht@home:~$ sudo /etc/xen/scripts/network-bridge start > > ifdown: interface peth0 not configured > > RTNETLINK answers: Device or resource busy > > > > That doesn''t kill my network anymore, but what to do next? > > Are you using network manager?Yes, KNetworkManager, may that be a problem?> Did you try putting a manual entry in your /etc/network/interfaces file? > > See: > http://ubuntuforums.org/showthread.php?t=651078I don''t have the lines discussed in the thread, probably because I use the KNetworkManager: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 up ethtool -K eth0 tx off The last line doesn''t change the behavior, but I found that somewhere in the net to help out of networking troubles with some newer cards...> and also only similar problem that should already be fixed: > https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/192294That''s fixed for me...> > Cheers, > ToddCheers, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 10 May 2008 19:39:30 Todd Deshane wrote:> > Okay, now I have the local network back, but what now? This is the > > current state: > > > > irrlicht@home:~$ ifconfig -a > > 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:55 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:4155 (4.0 KB) TX bytes:4155 (4.0 KB) > > > > peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 > > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > > inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:20196 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:14388 errors:0 dropped:0 overruns:0 carrier:2 > > collisions:0 txqueuelen:1000 > > RX bytes:21625055 (20.6 MB) TX bytes:1178441 (1.1 MB) > > > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > > > If I start /etc/xen/scripts/network-bridge start I get back the > > "tmpbridge" and the messages: > > irrlicht@home:~$ sudo /etc/xen/scripts/network-bridge start > > ifdown: interface peth0 not configured > > RTNETLINK answers: Device or resource busy > > > > That doesn''t kill my network anymore, but what to do next? > > Are you using network manager?Yes, KNetworkManager, may that be a problem?> Did you try putting a manual entry in your /etc/network/interfaces file? > > See: > http://ubuntuforums.org/showthread.php?t=651078I don''t have the lines discussed in the thread, probably because I use the KNetworkManager: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 up ethtool -K eth0 tx off The last line doesn''t change the behavior, but I found that somewhere in the net to help out of networking troubles with some newer cards...> and also only similar problem that should already be fixed: > https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/192294That''s fixed for me...> > Cheers, > ToddCheers, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday 10 May 2008 21:50:50 Todd Deshane wrote:> > There was a post somewhere about deleting the xen state directory. This > > got rid of my tmpbridge . > > > > Which state directory? do you have a link to the post by chance? > > Cheers, > ToddThat didn''t help for me... :( tmpbridge still there... (I removed /var/lib/xend/state/ which was created again after /etc/init.d/xend restart) Cheers, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Ubuntu hardy has a fatal bug in it''s networking kernel. https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010 The kernel of "HIRANO Takahito" (comment 47) works for me. Regards, Steffen> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Daniel Spies > Sent: Sunday, May 11, 2008 1:30 PM > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] No network at all in Kubuntu 8.04 > > On Saturday 10 May 2008 21:50:50 Todd Deshane wrote: > > > There was a post somewhere about deleting the xen state > directory. > > > This got rid of my tmpbridge . > > > > > > Which state directory? do you have a link to the post by chance? > > > > Cheers, > > Todd > > That didn''t help for me... :( tmpbridge still there... > (I removed /var/lib/xend/state/ which was created again after > /etc/init.d/xend > restart) > > Cheers, > Daniel > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Doesn''t work for me... :( It''s really weird, cause when I run
"sudo brctl
delif eth0 peth0" nothing in "ifconfig -a" changed, but the
network is back.
What interfaces should be there normally? This is my "ifconfig -a"
after the
delete of the peth0 interface (Which is not deleted):
irrlicht@home:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
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:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3958 (3.8 KB) TX bytes:3958 (3.8 KB)
peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1336 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:80681 (78.7 KB) TX bytes:8798 (8.5 KB)
veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
On Sunday 11 May 2008 15:06:13 Steffen Heil wrote:> Hi
>
> Ubuntu hardy has a fatal bug in it''s networking kernel.
> https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010
>
> The kernel of "HIRANO Takahito" (comment 47) works for me.
>
> Regards,
> Steffen
>
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com
> > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
> > Daniel Spies
> > Sent: Sunday, May 11, 2008 1:30 PM
> > To: xen-users@lists.xensource.com
> > Subject: Re: [Xen-users] No network at all in Kubuntu 8.04
> >
> > On Saturday 10 May 2008 21:50:50 Todd Deshane wrote:
> > > > There was a post somewhere about deleting the xen state
> >
> > directory.
> >
> > > > This got rid of my tmpbridge .
> > > >
> > > > Which state directory? do you have a link to the post by
chance?
> > >
> > > Cheers,
> > > Todd
> >
> > That didn''t help for me... :( tmpbridge still there...
> > (I removed /var/lib/xend/state/ which was created again after
> > /etc/init.d/xend
> > restart)
> >
> > Cheers,
> > Daniel
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Sun, May 11, 2008 at 10:53 AM, Daniel Spies <daniel.spies@fuceekay.com> wrote:> Doesn''t work for me... :( It''s really weird, cause when I run "sudo brctl > delif eth0 peth0" nothing in "ifconfig -a" changed, but the network is > back. > What interfaces should be there normally? This is my "ifconfig -a" after > the > delete of the peth0 interface (Which is not deleted): >That command doesn''t delete the interface, it just removes the interface from the bridge post your /etc/network/interfaces file. Also did you remove network manager and/or disable network manager? have you tried to restart and reload things after fixing the network config? Does the system just have one NIC as shown in the ifconfig -a? Regards, Todd> irrlicht@home:~$ ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > 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:49 errors:0 dropped:0 overruns:0 frame:0 > TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3958 (3.8 KB) TX bytes:3958 (3.8 KB) > > peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:1336 errors:0 dropped:0 overruns:0 frame:0 > TX packets:100 errors:0 dropped:0 overruns:0 carrier:1 > collisions:0 txqueuelen:1000 > RX bytes:80681 (78.7 KB) TX bytes:8798 (8.5 KB) > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.2 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > vif0.3 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B) > > On Sunday 11 May 2008 15:06:13 Steffen Heil wrote: > > Hi > > > > Ubuntu hardy has a fatal bug in it''s networking kernel. > > https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010 > > > > The kernel of "HIRANO Takahito" (comment 47) works for me. > > > > Regards, > > Steffen > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > > Daniel Spies > > > Sent: Sunday, May 11, 2008 1:30 PM > > > To: xen-users@lists.xensource.com > > > Subject: Re: [Xen-users] No network at all in Kubuntu 8.04 > > > > > > On Saturday 10 May 2008 21:50:50 Todd Deshane wrote: > > > > > There was a post somewhere about deleting the xen state > > > > > > directory. > > > > > > > > This got rid of my tmpbridge . > > > > > > > > > > Which state directory? do you have a link to the post by chance? > > > > > > > > Cheers, > > > > Todd > > > > > > That didn''t help for me... :( tmpbridge still there... > > > (I removed /var/lib/xend/state/ which was created again after > > > /etc/init.d/xend > > > restart) > > > > > > Cheers, > > > Daniel > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 12 May 2008 01:44:32 Todd Deshane wrote:> On Sun, May 11, 2008 at 10:53 AM, Daniel Spies <daniel.spies@fuceekay.com> > > wrote: > > Doesn''t work for me... :( It''s really weird, cause when I run "sudo brctl > > delif eth0 peth0" nothing in "ifconfig -a" changed, but the network is > > back. > > What interfaces should be there normally? This is my "ifconfig -a" after > > the > > delete of the peth0 interface (Which is not deleted): > > That command doesn''t delete the interface, it just removes the interface > from > the bridge > > post your /etc/network/interfaces file.As you command: irrlicht@home:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 auto eth0 iface eth0 inet dhcp up ethtool -K eth0 tx off Before disabling the Network Manager the file was like this: [...] # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 up ethtool -K eth0 tx off> Also did you remove network manager and/or disable network manager?Yes, I did, seems not to help. :''-( But one thing changed: The eth0 interface is now up after reboot and additionally I have to "sudo ifdown eth0" it in order to get connectivity back.> have you tried to restart and reload things after fixing the network > config?I did that right now, and a hundred times before...> Does the system just have one NIC as shown in the ifconfig -a?Indeed I have only one NIC, onboard Gigabit LAN eth0, or in this case peth0...> Regards, > Toddfrustrated regards, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Daniel, Daniel Spies schrieb:> I face troubles while just using the xen-enabled kernel in Kubuntu Hardy > (8.04).I am using Ubuntu Server 8.04 with Xen.> I just don''t have no network at all. If I run ifconfig I see the > peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one > called "tempbr0" or so. But all of them are down. I can''t tell exactly as I > have to reboot and use another kernel to get network access back... > > peth0 has got my 192.168.1.2 address and is set up as default gateway.Why does your peth0 has an ip-address? root@deedee:~# ifconfig peth0 peth0 Link encap:Ethernet HWaddr 00:1a:4d:71:5b:03 inet6 addr: fe80::21a:4dff:fe71:5b03/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:119620 errors:0 dropped:0 overruns:0 frame:0 TX packets:162937 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15740780 (15.0 MB) TX bytes:55379023 (52.8 MB) Interrupt:23 Base address:0x2000 My Dom0 has its IP-Address at the bridge: root@deedee:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1a:4d:71:5b:03 inet addr:192.168.172.200 Bcast:192.168.172.255 Mask:255.255.255.0 inet6 addr: fe80::21a:4dff:fe71:5b03/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:112835 errors:0 dropped:0 overruns:0 frame:0 TX packets:130795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:24145645 (23.0 MB) TX bytes:22805689 (21.7 MB) root@deedee:~# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.172.200 netmask 255.255.255.0 network 192.168.172.0 broadcast 192.168.172.255 gateway 192.168.172.254 dns-nameservers 192.168.172.254 dns-search local.net Greetz Age_M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 12 May 2008 11:24:16 Age_M wrote:> Hi Daniel, > > Daniel Spies schrieb: > > I face troubles while just using the xen-enabled kernel in Kubuntu Hardy > > (8.04). > > I am using Ubuntu Server 8.04 with Xen. > > > I just don''t have no network at all. If I run ifconfig I see the > > peth0 and lo is up. ifconfig -a shows all the virtual interfaces and one > > called "tempbr0" or so. But all of them are down. I can''t tell exactly as > > I have to reboot and use another kernel to get network access back... > > > > peth0 has got my 192.168.1.2 address and is set up as default gateway. > > Why does your peth0 has an ip-address? >Good question, I don''t know... What do you suggest me to do? Both, eth0 and peth0 have the very same configuration and IP addresses in "ifconfig -a". irrlicht@home:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 auto eth0 iface eth0 inet dhcp Cheers, Daniel> root@deedee:~# ifconfig peth0 > peth0 Link encap:Ethernet HWaddr 00:1a:4d:71:5b:03 > inet6 addr: fe80::21a:4dff:fe71:5b03/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:119620 errors:0 dropped:0 overruns:0 frame:0 > TX packets:162937 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:15740780 (15.0 MB) TX bytes:55379023 (52.8 MB) > Interrupt:23 Base address:0x2000 > > My Dom0 has its IP-Address at the bridge: > > root@deedee:~# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:1a:4d:71:5b:03 > inet addr:192.168.172.200 Bcast:192.168.172.255 > Mask:255.255.255.0 > inet6 addr: fe80::21a:4dff:fe71:5b03/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:112835 errors:0 dropped:0 overruns:0 frame:0 > TX packets:130795 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:24145645 (23.0 MB) TX bytes:22805689 (21.7 MB) > > root@deedee:~# cat /etc/network/interfaces > auto lo > iface lo inet loopback > > auto eth0 > iface eth0 inet static > address 192.168.172.200 > netmask 255.255.255.0 > network 192.168.172.0 > broadcast 192.168.172.255 > gateway 192.168.172.254 > dns-nameservers 192.168.172.254 > dns-search local.net > > Greetz Age_M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Spies schrieb:> On Monday 12 May 2008 11:24:16 Age_M wrote: > >> Hi Daniel, >> >> Why does your peth0 has an ip-address? >> >> > Good question, I don''t know... What do you suggest me to do? > Both, eth0 and peth0 have the very same configuration and IP addresses > in "ifconfig -a". > > irrlicht@home:~$ cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > address 127.0.0.1 > netmask 255.0.0.0 > auto eth0 > iface eth0 inet dhcp >Try using static ip instead of dhcp in dom0. Maybe this is messing with your interfaces. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Daniel, Age_M schrieb:> Daniel Spies schrieb: >> On Monday 12 May 2008 11:24:16 Age_M wrote: >> >>> Hi Daniel, >>> Why does your peth0 has an ip-address? >>> >>> >> Good question, I don''t know... What do you suggest me to do? >> Both, eth0 and peth0 have the very same configuration and IP >> addresses in "ifconfig -a". >> >> irrlicht@home:~$ cat /etc/network/interfaces >> # This file describes the network interfaces available on your system >> # and how to activate them. For more information, see interfaces(5). >> >> # The loopback network interface >> auto lo >> iface lo inet loopback >> address 127.0.0.1 >> netmask 255.0.0.0 >> auto eth0 >> iface eth0 inet dhcp >> > Try using static ip instead of dhcp in dom0. Maybe this is messing > with your interfaces. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >I recently had a networking problem myself, where only pings came through from domU to the physical network. I had to turn off tx checksum offload with ethtool. I integrated it in the xen-network-common.sh script, so maybe this patch will help you too?! This patch modifies the last line in the "add_to_bridge ()" function: --- scripts/xen-network-common.sh 2008-05-12 15:22:52.000000000 +0200 +++ scripts/xen-network-common.sh.modified 2008-05-12 15:23:41.000000000 +0200 @@ -124,5 +124,6 @@ fi brctl addif ${bridge} ${dev} ip link set ${dev} up + ethtool -K ${dev} tx off } Hope it helps, Greetz Age_M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 12 May 2008 11:58:33 Age_M wrote:> Daniel Spies schrieb: > > On Monday 12 May 2008 11:24:16 Age_M wrote: > >> Hi Daniel, > >> > >> Why does your peth0 has an ip-address? > > > > Good question, I don''t know... What do you suggest me to do? > > Both, eth0 and peth0 have the very same configuration and IP addresses > > in "ifconfig -a". > > > > irrlicht@home:~$ cat /etc/network/interfaces > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > address 127.0.0.1 > > netmask 255.0.0.0 > > auto eth0 > > iface eth0 inet dhcp > > Try using static ip instead of dhcp in dom0. Maybe this is messing with > your interfaces.Okay, I did without success. But therefor I found something else: irrlicht@home:~$ route -vn Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 peth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 peth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 eth0 irrlicht@home:~$ sudo route del -net 0.0.0.0 netmask 0.0.0.0 dev peth0 irrlicht@home:~$ ping google.de PING google.de (216.239.59.104) 56(84) bytes of data. 64 bytes from 216.239.59.104: icmp_seq=1 ttl=245 time=98.7 ms 64 bytes from 216.239.59.104: icmp_seq=2 ttl=245 time=95.5 ms 64 bytes from 216.239.59.104: icmp_seq=3 ttl=245 time=99.7 ms 64 bytes from 216.239.59.104: icmp_seq=4 ttl=245 time=97.6 ms --- google.de ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 45895ms rtt min/avg/max/mdev = 95.598/97.932/99.708/1.575 ms irrlicht@home:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 auto eth0 iface eth0 inet static address 192.168.1.2 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 dns-nameservers 192.168.1.1 As you can see I get the connection as soon I delete the default route via peth0, but I always thought that the metric is better the lower it is, so peth0 should never be used as default... For reference, my peth0 still got that IP addess: irrlicht@home:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4280 errors:0 dropped:0 overruns:0 frame:0 TX packets:1954 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1240921 (1.1 MB) TX bytes:178555 (174.3 KB) irrlicht@home:~$ ifconfig peth0 peth0 Link encap:Ethernet HWaddr 00:1d:60:c3:81:60 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21d:60ff:fec3:8160/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:4560 errors:0 dropped:0 overruns:0 frame:0 TX packets:2178 errors:0 dropped:0 overruns:0 carrier:2 collisions:0 txqueuelen:1000 RX bytes:1320308 (1.2 MB) TX bytes:199415 (194.7 KB) Thanks, Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 12 May 2008 15:34:47 Age_M wrote:> Hi Daniel, > > Age_M schrieb: > > Daniel Spies schrieb: > >> On Monday 12 May 2008 11:24:16 Age_M wrote: > >>> Hi Daniel, > >>> Why does your peth0 has an ip-address? > >> > >> Good question, I don''t know... What do you suggest me to do? > >> Both, eth0 and peth0 have the very same configuration and IP > >> addresses in "ifconfig -a". > >> > >> irrlicht@home:~$ cat /etc/network/interfaces > >> # This file describes the network interfaces available on your system > >> # and how to activate them. For more information, see interfaces(5). > >> > >> # The loopback network interface > >> auto lo > >> iface lo inet loopback > >> address 127.0.0.1 > >> netmask 255.0.0.0 > >> auto eth0 > >> iface eth0 inet dhcp > > > > Try using static ip instead of dhcp in dom0. Maybe this is messing > > with your interfaces. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > I recently had a networking problem myself, where only pings came > through from domU to the physical network. I had to turn off tx checksum > offload with ethtool. I integrated it in the xen-network-common.sh > script, so maybe this patch will help you too?! > > This patch modifies the last line in the "add_to_bridge ()" function: > > --- scripts/xen-network-common.sh 2008-05-12 15:22:52.000000000 +0200 > +++ scripts/xen-network-common.sh.modified 2008-05-12 > 15:23:41.000000000 +0200 > @@ -124,5 +124,6 @@ > fi > brctl addif ${bridge} ${dev} > ip link set ${dev} up > + ethtool -K ${dev} tx off > } > > Hope it helps, > Greetz Age_M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersThis was the first thing I tried, but that doesn''t change things for me. I did it via "up ethtool -K eth0 tx off" in /etc/network/interfaces... Thanks anyway! Daniel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi All, Ubuntu had this "Network Manager" component which messed up things with XEN for me in the past. Could you please remove the network-manager network-manager-gnome packages and try again to give the interface an IP address using the /etc/network/interfaces file? sudo apt-get remove network-manager network-manager-gnome Emre On Mon, May 12, 2008 at 3:44 PM, Daniel Spies <daniel.spies@fuceekay.com> wrote:> On Monday 12 May 2008 15:34:47 Age_M wrote: > > Hi Daniel, > > > > Age_M schrieb: > > > Daniel Spies schrieb: > > >> On Monday 12 May 2008 11:24:16 Age_M wrote: > > >>> Hi Daniel, > > >>> Why does your peth0 has an ip-address? > > >> > > >> Good question, I don''t know... What do you suggest me to do? > > >> Both, eth0 and peth0 have the very same configuration and IP > > >> addresses in "ifconfig -a". > > >> > > >> irrlicht@home:~$ cat /etc/network/interfaces > > >> # This file describes the network interfaces available on your system > > >> # and how to activate them. For more information, see interfaces(5). > > >> > > >> # The loopback network interface > > >> auto lo > > >> iface lo inet loopback > > >> address 127.0.0.1 > > >> netmask 255.0.0.0 > > >> auto eth0 > > >> iface eth0 inet dhcp > > > > > > Try using static ip instead of dhcp in dom0. Maybe this is messing > > > with your interfaces. > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > I recently had a networking problem myself, where only pings came > > through from domU to the physical network. I had to turn off tx checksum > > offload with ethtool. I integrated it in the xen-network-common.sh > > script, so maybe this patch will help you too?! > > > > This patch modifies the last line in the "add_to_bridge ()" function: > > > > --- scripts/xen-network-common.sh 2008-05-12 15:22:52.000000000 > +0200 > > +++ scripts/xen-network-common.sh.modified 2008-05-12 > > 15:23:41.000000000 +0200 > > @@ -124,5 +124,6 @@ > > fi > > brctl addif ${bridge} ${dev} > > ip link set ${dev} up > > + ethtool -K ${dev} tx off > > } > > > > Hope it helps, > > Greetz Age_M > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > This was the first thing I tried, but that doesn''t change things for me. I > did > it via "up ethtool -K eth0 tx off" in /etc/network/interfaces... > > Thanks anyway! > Daniel > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
<482814C9.9010800@gmx.de> <48284777.7090904@gmx.de> <200805121544.02186.daniel.spies@fuceekay.com> <fe9771a80805121249m1db7c564l811c3e62db24e16f@mail.gmail.com> Message-ID: <cf9f4e818c7a3815e28395b72ae1bcfd@localhost> X-Sender: daniel.spies@fuceekay.com Received: from 62.159.37.130 [62.159.37.130] with HTTP/1.1 (POST); Tue, 13 May 2008 08:45:35 +0200 User-Agent: RoundCube Webmail/0.1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Hi Emre, I did _disable_ the network manager already (KNetworkManager, as I''m using Kubuntu (Ubuntu with KDE)), do you think I should remove it completely? If yes, I''ll give it a try later when I''m back at home... Thank you! Daniel On Mon, 12 May 2008 21:49:46 +0200, "Emre ERENOGLU" <erenoglu@gmail.com> wrote:> Hi All, > > Ubuntu had this "Network Manager" component which messed up things with > XEN > for me in the past. Could you please remove the network-manager > network-manager-gnome packages and try again to give the interface an IP > address using the /etc/network/interfaces file? > > sudo apt-get remove network-manager network-manager-gnome > > Emre > > On Mon, May 12, 2008 at 3:44 PM, Daniel Spies <daniel.spies@fuceekay.com> > wrote: > >> On Monday 12 May 2008 15:34:47 Age_M wrote: >> > Hi Daniel, >> > >> > Age_M schrieb: >> > > Daniel Spies schrieb: >> > >> On Monday 12 May 2008 11:24:16 Age_M wrote: >> > >>> Hi Daniel, >> > >>> Why does your peth0 has an ip-address? >> > >> >> > >> Good question, I don''t know... What do you suggest me to do? >> > >> Both, eth0 and peth0 have the very same configuration and IP >> > >> addresses in "ifconfig -a". >> > >> >> > >> irrlicht@home:~$ cat /etc/network/interfaces >> > >> # This file describes the network interfaces available on your > system >> > >> # and how to activate them. For more information, see > interfaces(5). >> > >> >> > >> # The loopback network interface >> > >> auto lo >> > >> iface lo inet loopback >> > >> address 127.0.0.1 >> > >> netmask 255.0.0.0 >> > >> auto eth0 >> > >> iface eth0 inet dhcp >> > > >> > > Try using static ip instead of dhcp in dom0. Maybe this is messing >> > > with your interfaces. >> > > >> > > _______________________________________________ >> > > Xen-users mailing list >> > > Xen-users@lists.xensource.com >> > > http://lists.xensource.com/xen-users >> > >> > I recently had a networking problem myself, where only pings came >> > through from domU to the physical network. I had to turn off tx > checksum >> > offload with ethtool. I integrated it in the xen-network-common.sh >> > script, so maybe this patch will help you too?! >> > >> > This patch modifies the last line in the "add_to_bridge ()" function: >> > >> > --- scripts/xen-network-common.sh 2008-05-12 15:22:52.000000000 >> +0200 >> > +++ scripts/xen-network-common.sh.modified 2008-05-12 >> > 15:23:41.000000000 +0200 >> > @@ -124,5 +124,6 @@ >> > fi >> > brctl addif ${bridge} ${dev} >> > ip link set ${dev} up >> > + ethtool -K ${dev} tx off >> > } >> > >> > Hope it helps, >> > Greetz Age_M >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> >> This was the first thing I tried, but that doesn''t change things for me. > I >> did >> it via "up ethtool -K eth0 tx off" in /etc/network/interfaces... >> >> Thanks anyway! >> Daniel >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > > -- > Emre Erenoglu > erenoglu@gmail.com_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Todd, Thanks for your answer! I''m running a Intel E6750 but am using the 32bit edition of Kubuntu. I installed several patched kernels now, non of them changed the bahaviour of the issue. And I tried both: With and without the ethtool command. Currently without it. What about the weird routeing issue? May there be the failure? As I''m not at home I only can only refer to a previous mail from me. If I delte the default route to peth0 (if I remember right) the network is working for dom0 but I cannot create a machine with xm create... Cheers, Daniel On Mon, 12 May 2008 09:48:22 -0400, "Todd Deshane" <deshantm@gmail.com> wrote:> Hi Daniel, > > I think things should work for you. > > Let''s try to find any differences in the setup... > > amd64 or i386? > > I am using amd64 > > Fixed kernel packages from: > downloads.howtoforge.com/ubuntu_8.04_server_xen_from_repositories > > I didn''t need the ethtool command for mine to work, but maybe you > are running into a different case? Have you tried without the ethtool > command? > > Regards, > Todd_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel, the knetwork-manager is only the GUI part of the network-manager, not the core. So if you didn''t yet remove the real core network-manager package, could you please try? Emre On Tue, May 13, 2008 at 8:45 AM, Daniel Spies <daniel.spies@fuceekay.com> wrote:> <482814C9.9010800@gmx.de> <48284777.7090904@gmx.de> > <200805121544.02186.daniel.spies@fuceekay.com> < > fe9771a80805121249m1db7c564l811c3e62db24e16f@mail.gmail.com> > Message-ID: <cf9f4e818c7a3815e28395b72ae1bcfd@localhost> > X-Sender: daniel.spies@fuceekay.com > Received: from 62.159.37.130 [62.159.37.130] with HTTP/1.1 (POST); Tue, 13 > May > 2008 08:45:35 +0200 > User-Agent: RoundCube Webmail/0.1 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: 8bit > > Hi Emre, > > I did _disable_ the network manager already (KNetworkManager, as I''m using > Kubuntu (Ubuntu with KDE)), do you think I should remove it completely? If > yes, I''ll give it a try later when I''m back at home... > > Thank you! > Daniel > > On Mon, 12 May 2008 21:49:46 +0200, "Emre ERENOGLU" <erenoglu@gmail.com> > wrote: > > Hi All, > > > > Ubuntu had this "Network Manager" component which messed up things with > > XEN > > for me in the past. Could you please remove the network-manager > > network-manager-gnome packages and try again to give the interface an IP > > address using the /etc/network/interfaces file? > > > > sudo apt-get remove network-manager network-manager-gnome > > > > Emre > > > > On Mon, May 12, 2008 at 3:44 PM, Daniel Spies <daniel.spies@fuceekay.com > > > > wrote: > > > >> On Monday 12 May 2008 15:34:47 Age_M wrote: > >> > Hi Daniel, > >> > > >> > Age_M schrieb: > >> > > Daniel Spies schrieb: > >> > >> On Monday 12 May 2008 11:24:16 Age_M wrote: > >> > >>> Hi Daniel, > >> > >>> Why does your peth0 has an ip-address? > >> > >> > >> > >> Good question, I don''t know... What do you suggest me to do? > >> > >> Both, eth0 and peth0 have the very same configuration and IP > >> > >> addresses in "ifconfig -a". > >> > >> > >> > >> irrlicht@home:~$ cat /etc/network/interfaces > >> > >> # This file describes the network interfaces available on your > > system > >> > >> # and how to activate them. For more information, see > > interfaces(5). > >> > >> > >> > >> # The loopback network interface > >> > >> auto lo > >> > >> iface lo inet loopback > >> > >> address 127.0.0.1 > >> > >> netmask 255.0.0.0 > >> > >> auto eth0 > >> > >> iface eth0 inet dhcp > >> > > > >> > > Try using static ip instead of dhcp in dom0. Maybe this is messing > >> > > with your interfaces. > >> > > > >> > > _______________________________________________ > >> > > Xen-users mailing list > >> > > Xen-users@lists.xensource.com > >> > > http://lists.xensource.com/xen-users > >> > > >> > I recently had a networking problem myself, where only pings came > >> > through from domU to the physical network. I had to turn off tx > > checksum > >> > offload with ethtool. I integrated it in the xen-network-common.sh > >> > script, so maybe this patch will help you too?! > >> > > >> > This patch modifies the last line in the "add_to_bridge ()" function: > >> > > >> > --- scripts/xen-network-common.sh 2008-05-12 15:22:52.000000000 > >> +0200 > >> > +++ scripts/xen-network-common.sh.modified 2008-05-12 > >> > 15:23:41.000000000 +0200 > >> > @@ -124,5 +124,6 @@ > >> > fi > >> > brctl addif ${bridge} ${dev} > >> > ip link set ${dev} up > >> > + ethtool -K ${dev} tx off > >> > } > >> > > >> > Hope it helps, > >> > Greetz Age_M > >> > > >> > _______________________________________________ > >> > Xen-users mailing list > >> > Xen-users@lists.xensource.com > >> > http://lists.xensource.com/xen-users > >> > >> This was the first thing I tried, but that doesn''t change things for > me. > > I > >> did > >> it via "up ethtool -K eth0 tx off" in /etc/network/interfaces... > >> > >> Thanks anyway! > >> Daniel > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > >> > > > > > > > > -- > > Emre Erenoglu > > erenoglu@gmail.com > >-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
That did the trick! You are my personal hero! :) Thanks so much! Cheers, Daniel On Tuesday 13 May 2008 11:52:23 Emre ERENOGLU wrote:> Daniel, the knetwork-manager is only the GUI part of the network-manager, > not the core. So if you didn''t yet remove the real core network-manager > package, could you please try? > > Emre >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Good to hear that it works now :) Emre On Tue, May 13, 2008 at 9:15 PM, Daniel Spies <daniel.spies@fuceekay.com> wrote:> That did the trick! You are my personal hero! :) > > Thanks so much! > > Cheers, > Daniel > > On Tuesday 13 May 2008 11:52:23 Emre ERENOGLU wrote: > > Daniel, the knetwork-manager is only the GUI part of the > network-manager, > > not the core. So if you didn''t yet remove the real core network-manager > > package, could you please try? > > > > Emre > > >-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users