Hi, i am running binary Xen 3.0.3 testing on Debian etch and try to boot a sarge-domU. It works all fine now, but eth0 is not brougth up on boot. I have to bring it up manually with ''ifconfig eth0 192.168.1.10 up''. Besides that networking works perfectly. There seems to be no module-loading involved, because with eth0 up are the same modules loaded as before bringing it up. Can you give me a hint, how i can let eth0 bring up automaticlly or where i could look to find out what is going wrong? I think it is a dom0-specific thing, because i used the same image (only with different modules, because of an older dom0-Kernel) with an other dom0 running debian sarge and selfcompiled xen 3.0.2 without any problems. I have no entries in /etc/network/interfaces for eth0. That you be fine, right? Thank you, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
"I have no entries in /etc/network/interfaces for eth0. That you be fine,
right?"
No, I think that''s the problem actually, isn''t it? I think
you definitely
need an entry in /etc/network/interfaces for eth0 for your DomU.
Here''s an example to follow, though you''ll have to change
these numbers for
yourself. I *think* you could also just delete everything but the first two
lines (3 including the comment), and change "static" to
"dhcp". Assuming
you have a dhcp server around.
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.6
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
Hope that helps,
- GM
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com]On Behalf Of Julian Hagenauer
Sent: Monday, October 02, 2006 2:36 PM
To: xen-users@lists.xensource.com
Subject: [Xen-users] eth0 in domU is not brought up on boot
Hi, i am running binary Xen 3.0.3 testing on Debian etch and try to boot
a sarge-domU. It works all fine now, but eth0 is not brougth up on boot.
I have to bring it up manually with ''ifconfig eth0 192.168.1.10
up''.
Besides that networking works perfectly. There seems to be no
module-loading involved, because with eth0 up are the same modules
loaded as before bringing it up.
Can you give me a hint, how i can let eth0 bring up automaticlly or
where i could look to find out what is going wrong?
I think it is a dom0-specific thing, because i used the same image (only
with different modules, because of an older dom0-Kernel) with an other
dom0 running debian sarge and selfcompiled xen 3.0.2
without any problems.
I have no entries in /etc/network/interfaces for eth0. That you be fine,
right?
Thank you,
Julian
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.0.407 / Virus Database: 268.12.11/460 - Release Date: 10/1/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.0.407 / Virus Database: 268.12.11/460 - Release Date: 10/1/2006
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Julian Hagenauer
2006-Oct-03 07:09 UTC
Re: [Xen-users] eth0 in domU is not brought up on boot
Hi, tank you for your answer. I am pretty sure. that there must be no entrys for eth0 in etc/network/interfaces, at least at my old sarge+xen 3.0.2 setup. Sincerely, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julian Hagenauer
2006-Oct-03 12:57 UTC
Re: [Xen-users] eth0 in domU is not brought up on boot
On Tue, 3 Oct 2006 09:09:00 +0200 Julian Hagenauer <chaosbringer@gmx.de> wrote:> Hi, > tank you for your answer. > I am pretty sure. that there must be no entrys for eth0 inetc/network/interfaces, at least at my old sarge+xen 3.0.2 setup.> > Sincerely, > Julian > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Hi, i solved the problem. The problem was, that IP_PNP is not configured by default. So one can either build a new kernel with this option set to yes, or build independent dom0/domU Kernels, where this option is set to yes by default. Sincerely, Julian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users