WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 363] New: Network on domU does not work on blades (dom0

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 363] New: Network on domU does not work on blades (dom0 uses physical nic eth1)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 25 Oct 2005 19:48:21 +0000
Delivery-date: Tue, 25 Oct 2005 19:48:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=363

           Summary: Network on domU does not work on blades (dom0 uses
                    physical nic eth1)
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: lge@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx,pl@xxxxxxxxxx


I have seen this problem on all of my blades which dom0 use physical nic eth1
instead of eth0 since yesterday (changeset: 7481). None of the domU's network
can reach anywhere.

Here are some info from Dom0 after xend starts:
bl2-2:~ # ifconfig
eth1      Link encap:Ethernet  HWaddr 00:11:25:9D:63:19
          inet addr:9.3.192.195  Bcast:9.3.192.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:582 errors:0 dropped:0 overruns:0 frame:0
          TX packets:253 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:69466 (67.8 Kb)  TX bytes:25465 (24.8 Kb)
          Interrupt:78
 
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:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1512 (1.4 Kb)  TX bytes:1512 (1.4 Kb)
 
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP 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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:77
 
vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING 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)
 
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING 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)
          collisions:0 txqueuelen:0
          RX bytes:6800942 (6.4 Mb)  TX bytes:0 (0.0 b)

bl2-2:/etc/xen/scripts # ./network-bridge status
============================================================
5: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:11:25:9d:63:18 brd ff:ff:ff:ff:ff:ff
6: xenbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  
incorrect number of arguments for command

Here are some from domU:

bl2-2-vm1:ß # ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:36:BE:6F
          inet addr:9.3.190.218  Bcast:9.3.190.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1020 (1020.0 b)  TX bytes:2597 (2.5 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:39 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3614 (3.5 Kb)  TX bytes:3614 (3.5 Kb)
 
bl2-2-vm1:ß # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
9.3.190.0       *               255.255.255.0   U     0      0        0 eth0
link-local      *               255.255.0.0     U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        0 lo
default         9.3.190.1       0.0.0.0         UG    0      0        0 eth0
bl2-2-vm1:ß # ping 9.3.190.1
PING 9.3.190.1 (9.3.190.1) 56(84) bytes of data.
>From 9.3.190.218: icmp_seq=1 Destination Host Unreachable
>From 9.3.190.218 icmp_seq=1 Destination Host Unreachable
>From 9.3.190.218 icmp_seq=2 Destination Host Unreachable
>From 9.3.190.218 icmp_seq=3 Destination Host Unreachable
 
--- 9.3.190.1 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4028ms
, pipe 3

I am not quite sure if this problem is caused by something in the network-bridge
script that I need to modify to make eth1 work which I did not do. I tried
change vifnum from 0 to 1 in the script. But it did not help.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 363] New: Network on domU does not work on blades (dom0 uses physical nic eth1), bugzilla-daemon <=