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

RE: [Xen-users] eth0 in domU is not brought up on boot


  • To: "Julian Hagenauer" <chaosbringer@xxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Grok Mogger <linuximp@xxxxxxxxx>
  • Date: Mon, 2 Oct 2006 17:47:58 -0400
  • Delivery-date: Mon, 02 Oct 2006 14:48:46 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:in-reply-to:importance:x-mimeole:from; b=haUwC/4nLpIRResKMSOLPVJC89fdl6PgLkZfGYBmN7ZjRuOvIq4jLaCW86LYtEq7j2fmzOx+L/5qcdZjfsASAwkbTQ2UfeZXkNSAq+StNmxOBqSBOE19wUzDXJgcWXhgFsAc8dWcbHTGvmtqcRjcHedxUiHI3gu+7OAh7YOdj8E=
  • Importance: Normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

"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@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Julian Hagenauer
Sent: Monday, October 02, 2006 2:36 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx
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@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®.