[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Not able to get eth0 up on domU.


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Atul Dambalkar" <atul_dambalkar@xxxxxxxxxxxx>
  • Date: Mon, 17 Oct 2005 17:41:02 -0700
  • Delivery-date: Tue, 18 Oct 2005 00:38:28 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcXTfJqeJhzHFevmR/elotVieLkswA==
  • Thread-topic: Not able to get eth0 up on domU.

I am using ttylinux-xen file system image a a loopback device for the domain. I am mostly using the default configuration. I am not able to get networking on the domU. Are kernel "vmlinuz-2.6-xenU" as well as "2.6.11.12-xen0" both compiled w/o loadable module support? I guess it fails when it tries to initialize the iptables on the domU when it tries to do "modprobe". I do have connectivity on dom0. Am I doing anything wrong?
 
-Atul
 
Here are all the details about domU:
 
==============domain configuration file==============
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 64
name = "ttylinux"
nics=1
vif = [ 'mac=aa:01:02:05:0B:11, bridge=xen-br0' ]
disk = [ 'phy:/dev/loop0,sda1,w' ]
dhcp="dhcp"
root = "/dev/sda1 ro"
=============================================
 
 
========== Output of 'ifconfig -a' on "ttylinux" domain ====================================
eth0      Link encap:Ethernet  HWaddr AA:01:02:05:0B:11 
          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:1000
          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
          UP LOOPBACK RUNNING  MTU:16436  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)
============================================
 
Error message while starting the domain "ttylinux"
============================================
Running local start scripts.
Starting basic firewall: modprobe: could not parse modules.dep
 
iptables v1.2.11: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
modprobe: could not parse modules.dep
===============================================
 
 
Here are details about the dom0:
 
# uname -a
Linux localhost.localdomain 2.6.11.12-xen0 #1 Thu Aug 4 00:45:12 BST 2005 i686 i686 i386 GNU/Linux
If I try to set iptable rules on the Host OS I get following:
==============================================
iptables -A FORWARD -m physdev --physdev-in eth0 --physdev-out '!' eth0  -j ACCEPT
modprobe: QM_MODULES: Function not implemented
 
modprobe: QM_MODULES: Function not implemented
 
modprobe: Can't locate module ip_tables
iptables v1.2.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
==================================================
 
File: xend.log (partial)
=======================================
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c033bb84
 Init. ramdisk: c033c000->c033c000
 Phys-Mach map: c033c000->c034c000
 Page tables:   c034c000->c034e000
 Start info:    c034e000->c034f000
 Boot stack:    c034f000->c0350000
 TOTAL:         c0000000->c0400000
 ENTRY ADDRESS: c0100000
vif-bridge up vif=vif35.0 domain=ttylinux mac=aa:01:02:05:0b:11 bridge=xen-br0
recv_fe_driver_status> {'status': 1}
 
recv_fe_driver_status>
 
recv_fe_interface_connect {'tx_shmem_frame': 4571, 'rx_shmem_frame': 4570, 'handle': 0}
=========================================
 
 
Output of ifconfig on dom0:
==================================================
eth0      Link encap:Ethernet  HWaddr 00:0E:0C:51:AC:EE 
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9288 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16448 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1737109 (1.6 Mb)  TX bytes:1389582 (1.3 Mb)
          Base address:0xdf20 Memory:fcea0000-fcec0000
 
eth1      Link encap:Ethernet  HWaddr 00:0F:1F:80:4C:7C 
          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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0xdf40 Memory:fcee0000-fcf00000
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:20332 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20332 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1850852 (1.7 Mb)  TX bytes:1850852 (1.7 Mb)
 
vif7.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:8 errors:0 dropped:111 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:538 (538.0 b)
 
xen-br0   Link encap:Ethernet  HWaddr 00:0E:0C:51:AC:EE 
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7993 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14742 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:895909 (874.9 Kb)  TX bytes:1152226 (1.0 Mb)
 
===========================================================
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.