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

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

Hi,

afaik these parameters are not used anymore. You will need to
configure your interfaces inside the domU.

At least these parameters have never worked for.

Greetings,
-timo

On Mon, 24 Apr 2006 18:02:14 +0200
mherrn <mherrn@xxxxxxxxxxxxx> wrote:

> Hi
> 
> I have set up one domU in my xen 3.0 installation. Both, the dom0
> and the domU run under Debian etch.
> 
> I have configured the domU to use a static ip:
> 
>   ip="192.168.38.25"
>   netmask="255.255.255.0"
>   gateway="192.168.38.2"
>   hostname="schicksal"
>   dhcp="off"
> 
> These parameters are also given to the domU kernel on boot, as dmesg
> tells:
> 
>   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 NET: Registered protocol family 2 IP: routing
> cache hash table of 1024 buckets, 8Kbytes TCP established hash
> table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table
> entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured
> (established 8192 bind 8192) NET: Registered protocol family 8
>   NET: Registered protocol family 20
>   NET: Registered protocol family 1
> 
> The only thing I dont understand here is the 1.2.3.4 between the
> domU ip and the gateway ip.
> 
> Then running brctl in dom0 shows, that the network bridge is up:
> 
>   bridge name     bridge id               STP enabled     interfaces
>   xenbr0          8000.feffffffffff       no              vif25.0
>                                                           peth0
>                                                           vif0.0
> 
> 
> But still, domU has no ethX interface:
> 
>   schicksal:~# ifconfig
>   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)
>   
>   schicksal:~# ifup eth0
>   Ignoring unknown interface eth0=eth0.
> 
> Also the hostname (schicksal) is set manually here by setting it in
> /etc/hostname in domU. It is _not_ set automatically.
> 
> So what can be wrong here?
> Regards
> Marco
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 


-- 
Timo Benk
PGP Public Key: http://vs241071.vserver.de/timo_benk_gpg_key.asc


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