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-users

[Xen-users] No network connectivity for domU in SuSE 10, Xen 3

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
From: Kris Vassallo <kris@xxxxxxxxxxxxxxxxxx>
Date: Mon, 06 Feb 2006 18:16:34 -0800
Delivery-date: Tue, 07 Feb 2006 02:28:01 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hey everyone, I'm asking this question again because 1. I Read as much as I could of the archives and still had no success, and 2. am not sure if the posts that I was reading actually pertained to Xen 2 or Xen 3. Here's what I'm hoping for some help with:

I'm running SuSE 10 (updated) with a SuSE 10 xm with xen-3.0_8259-0.1. The problem that I'm having is that I can get absolutely no network traffic to go from dom0 to domU, or anywhere else for that matter. I have tried using both DHCP and static addressing. The following information will be in regards to the static address scheme I was trying. Basically when domU boots, it doesn't bother to bring up the eth0 interface, bringing the interface up with an ifup will bring the interface up (and with dhcp it fails acquiring an address and backgrounds) but I am unable to ping any device on my network besides the address that is assigned to the domU machine itself. Dom0 networking is just fine. The bridge is up, the vif for the xm is up... something just isn't linking together here. I'll include all of my config information below and would appreciate any help with this. I've been working on this for days and am getting no where with it :(

On domainU I have the following:
linux:~ # brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                                peth0
                                                                vif8.0

linux:~ # ifconfig
(loopback omitted)
eth1      Link encap:Ethernet  HWaddr 00:40:D0:43:A3:DB
          inet addr:192.168.1.35  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::240:d0ff:fe43:a3db/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6927 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4867 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2655951 (2.5 Mb)  TX bytes:611617 (597.2 Kb)
          Base address:0x3400 Memory:fc220000-fc240000

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST 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)
          Base address:0x2000 Memory:fc100000-fc120000

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 MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:9780 (9.5 Kb)

vif8.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:37 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:5 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1554 (1.5 Kb)  TX bytes:0 (0.0 b)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:217 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6076 (5.9 Kb)  TX bytes:378 (378.0 b)

linux:~ # route -n
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 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth1

My XM config file:
disk = [ 'file:/data/xen/otrs2/hda1,hda1,w' ]
memory = 256
kernel = "/boot/vmlinuz-2.6.13-15.7-xen"
ramdisk = "/boot/initrd-2.6.13-15.7-xen"
name = "otrs"
nics=1
vif = [ 'mac=aa:00:00:00:39:01, bridge=xenbr0' ]    <-- I HAVE TRIED: excluding this line, using only the mac argument, and using only the bridge argument... it's no help
ip="192.168.1.39"
netmask="255.255.255.0"
gateway="192.168.1.1"
hostname="pieceofcrap"
root = "hda1"



On DomainU
(loopback omitted)
eth0      Link encap:Ethernet  HWaddr AA:00:00:00:39:01
          inet addr:192.168.1.39  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:1554 (1.5 Kb)

linux:~ # route -n
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
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

NOTE: doing a "route add default gw 192.168.1.1"  here does not fix the problem.

linux:~ # cat /etc/sysconfig/network/ifcfg-eth0
IPADDR=192.168.1.39
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
STARTMODE='auto'    <-- Have also tried 'onboot'
USERCONTROL=no

------------------------
-Kris

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