I'M usig in my host eth2 as NW Card.
I have modified the xend-config.log file in this way:
[root@ingcsmdb02 /]# vi /etc/xen/xend-config.sxp
# one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
#
# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain. To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as
appropriate.
#
(network-script 'network-bridge netdev=eth2')
# The script used to control virtual interfaces. This can be overridden on
a
# per-vif basis when creating a domain or a configuring a new vif. The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do
the
# same here. The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover
that,
# so there is no need to specify it explicitly.
#
(vif-script vif-bridge)
## Use the following if network traffic is routed, as an alternative to the
# settings for bridged networking given above.
#(network-script network-route)
#(vif-script vif-route)
## Use the following if network traffic is routed with NAT, as an
alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script vif-nat)
# Dom0 will balloon out when needed to free memory for domU.
# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
# If dom0-min-mem=0, dom0 will never balloon out.
(dom0-min-mem 196)
# In SMP system, dom0 will use dom0-cpus # of CPUS
# If dom0-cpus = 0, dom0 will take all cpus available
(dom0-cpus 0)
# Whether to enable core-dumps when domains crash.
#(enable-dump no)
My ifconfig in dom0 has this output:
[root@ingcsmdb02 /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:85:BF:C1:D0
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:86346 errors:0 dropped:0 overruns:0 frame:0
 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:5982498 (5.7 MiB) TX bytes:2436 (2.3 KiB)
eth2 Link encap:Ethernet HWaddr 00:0D:9D:FF:8E:6D
 inet addr:148.191.201.252 Bcast:148.191.201.255
Mask:255.255.254.0
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:3359795 errors:0 dropped:0 overruns:0 frame:0
 TX packets:714655 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:996360859 (950.2 MiB) TX bytes:653759043 (623.4 MiB)
 Interrupt:22
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:128075 errors:0 dropped:0 overruns:0 frame:0
 TX packets:128075 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:135326909 (129.0 MiB) TX bytes:135326909 (129.0 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
 RX packets:102870 errors:0 dropped:0 overruns:0 frame:0
 TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:7350960 (7.0 MiB) TX bytes:45916 (44.8 KiB)
 Interrupt:29
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:8 errors:0 dropped:0 overruns:0 frame:0
 TX packets:86346 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:2436 (2.3 KiB) TX bytes:5982498 (5.7 MiB)
vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:18 errors:0 dropped:0 overruns:0 frame:0
 TX packets:322 errors:0 dropped:14 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:2592 (2.5 KiB) TX bytes:22062 (21.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:86326 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:4774594 (4.5 MiB) TX bytes:0 (0.0 b)
[root@ingcsmdb02 /]#
Thomas Diederich
**************************************************
* Boehringer Ingelheim Pharma GmbH & Co.KG
* A Informationsverarbeitung / Diplomant Systemtechnik
*
* Mail: diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
* Phone: +49 (0)6132/77-98151 
-----Ursprüngliche Nachricht-----
Von: Michael Mey [mailto:michael.mey@xxxxxx] 
Gesendet: Dienstag, 17. Januar 2006 15:33
An: xen-users@xxxxxxxxxxxxxxxxxxx
Cc: DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Betreff: Re: [Xen-users] NO IP!!!! URGEND
On Tuesday 17 January 2006 14:51, DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
wrote:
> Hey.
> I'm running xen3.0, and my biggest problem is up to now that my guest os
> has no IP when i configure it to recieve it via DHCP in the config file.
> When i add the IP an Subnet info to the config file, the network card
> recieves this ip but ping wont work.
> I have rebuilded my domU kernel several times. What did i do wrong?!
> Thanks Thomas
>
> Thomas Diederich
>
> **************************************************
> * Boehringer Ingelheim Pharma GmbH & Co.KG
> * A Informationsverarbeitung / Diplomant Systemtechnik
> *
> * Mail: diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> * Phone: +49 (0)6132/77-98151
Hi, 
what is your network configuration for dom0?
If you have several NICs connected to dom0, maybe you have a bridge for the 
vifs on the wrong NIC. 
Consider to configure /etc/xen/xend-config.sxp properly according to your 
network configuration.
Michael
-- 
----------------------------------------------------------------------------
------------
Michael Mey 
Thinking Objects Software GmbH | mailto: michael.mey@xxxxxx 
Lilienthalstrasse 2/1 | phone: +49 711 88770-147
70825 Stuttgart-Korntal, Germany | fax: +49 711 88770-449
----------------------------------------------------------------------------
------------
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users