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@lists.xensource.com
http://lists.xensource.com/xen-users
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@sourcepark.de> 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@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com
m> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
m> Also the hostname (schicksal) is set manually here by setting it in m> /etc/hostname in domU. It is _not_ set automatically. Delete /etc/hostname from the domU''s, then it should work. -- Seneca _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Apr 24, 2006 at 06:59:14PM +0200, Seneca wrote:> m> Also the hostname (schicksal) is set manually here by setting it in > m> /etc/hostname in domU. It is _not_ set automatically. > > Delete /etc/hostname from the domU''s, then it should work.No, it doesn''t. When /etc/hostname doesn''t exist, the hostname isn''t set at all. Also my network is down. This is my /etc/network/interfaces: # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0> > -- > Seneca > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- ------------------------------------------------------- SOURCEPARK mbH Gesellschaft für Softwareentwicklung Marco Herrn Helmholtzstr. 2 - 9, Gebäude 6 (M) 10587 Berlin Tel.: +49 (0) 30 / 39 80 68 30 Fax: +49 (0) 30 / 39 80 68 39 e-mail: marco.herrn@sourcepark.de www: www.sourcepark.de ------------------------------------------------------ Diese Email kann vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn sie nicht der richtige Adressat sind oder diese E-Mail irr- tümlich erhalten haben, informieren Sie bitte sofort den Absender und ver- nichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Apr 24, 2006 at 06:09:55PM +0200, Timo Benk wrote:> afaik these parameters are not used anymore. You will need to > configure your interfaces inside the domU.Well, when doing this, I have an interface in the domU, but that interface doesn''t work. I am not able to ping the dom0 from domU and vice versa. Regards Marco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users