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

Re: [Xen-users] no network interfaces in domU



That setup works without problems here on etch + xen 3.0.2-2

This is my /etc/network/interfaces in the domU's:
---
# 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

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping eth0
        script grep
        map eth0

# The primary network interface
allow-hotplug eth0
---

Seneca


You wrote at Montag, 24. April 2006 18:02:

m> Hi

m> I have set up one domU in my xen 3.0 installation. Both, the dom0 and
m> the domU run under Debian etch.

m> I have configured the domU to use a static ip:

m>   ip="192.168.38.25"
m>   netmask="255.255.255.0"
m>   gateway="192.168.38.2"
m>   hostname="schicksal"
m>   dhcp="off"

m> These parameters are also given to the domU kernel on boot, as dmesg
m> tells:

m>   Kernel command line: 
ip=192.168.38.25:1.2.3.4:192.168.38.2:255.255.255.0:schicksal:eth0öff 
root=/dev/hda1 ro 4
m>   NET: Registered protocol family 2
m>   IP: routing cache hash table of 1024 buckets, 8Kbytes
m>   TCP established hash table entries: 8192 (order: 4, 65536 bytes)
m>   TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
m>   TCP: Hash tables configured (established 8192 bind 8192)
m>   NET: Registered protocol family 8
m>   NET: Registered protocol family 20
m>   NET: Registered protocol family 1

m> The only thing I dont understand here is the 1.2.3.4 between the domU
m> ip and the gateway ip.

m> Then running brctl in dom0 shows, that the network bridge is up:

m>   bridge name     bridge id               STP enabled     interfaces
m>   xenbr0          8000.feffffffffff       no              vif25.0
m>                                                           peth0
m>                                                           vif0.0


m> But still, domU has no ethX interface:

m>   schicksal:~# ifconfig
m>   lo        Link encap:Local Loopback  
m>             inet addr:127.0.0.1  Mask:255.0.0.0
m>             UP LOOPBACK RUNNING  MTU:16436  Metric:1
m>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
m>             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
m>             collisions:0 txqueuelen:0 
m>             RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  
m>   schicksal:~# ifup eth0
m>   Ignoring unknown interface eth0=eth0.

m> Also the hostname (schicksal) is set manually here by setting it in
m> /etc/hostname in domU. It is _not_ set automatically.

m> So what can be wrong here?
m> Regards
m> Marco





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


_______________________________________________
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®.