All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharadwaj Yadavalli <bharadwaj.yadavalli@hp.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: [Q] eth0 not up on dom0
Date: Fri, 25 Mar 2005 11:56:05 -0500	[thread overview]
Message-ID: <20050325165605.GB10609@java.zko.dec.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3855@liverpoolst.ad.cl.cam.ac.uk>

Hi Ian,

Thanks for your reply.

However, I am still unable to get my network interface
up in dom0. Here is what I did:

I created a /etc/sysconfig/network-scripts/ifcfg-xen-br0
as you suggested.

# more /etc/sysconfig/network-scripts/ifcfg-xen-br0
DEVICE=xen-br0
BOOTPROTO=dhcp
ONBOOT=no
TYPE=Ethernet
DHCP_HOSTNAME=<myhostname>
USERCTL=no
PEERDNS=yes
IPV6INIT=no

[I also needed to modify

/etc/sysconfig/network-scripts/network-functions 

so that the device xen-br0 is not picked as xen but as xen-br0.]

Anyway, once dom0 booted, I do the following :

# ifconfig eth0 0.0.0.0 up
# xend start
# ifup xen-br0

I see dhclient running (ps) but I get 

=======
Determining IP information for xen-br0... xen-br0
failed
======

What am I missing? I verified that eth0 interface would come
up as expected and I get an IP address when booted with standard
FC3 Linux kernel.

Thanks for your help once again,

Bharadwaj

On Thu, Mar 24, 2005 at 09:42:44PM -0000, Ian Pratt wrote:
> > [I believe steps 2 amd 3 will be done by executing 
> >  xend start. I verified this by running 'brctl show' 
> >  after I ran 'xend start']
> > 
> > 4. Put up the bridge.
> >       # ifconfig xen-br0 up
> > 
> > Now that I have the bridge up, I tried running 
> > 
> >     ifup eth0
> > 
> > to get an IP address.
> 
> It's 'mybridge' you want to configure with dhcp, not eth0.
> You'll need to create an appropriate ifcfg-mybridge file then 'ifup
> mybridge'.
> 
> Ian 
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-25 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 21:42 [Q] eth0 not up on dom0 Ian Pratt
2005-03-25 16:56 ` Bharadwaj Yadavalli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-24 21:31 Bharadwaj Yadavalli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050325165605.GB10609@java.zko.dec.com \
    --to=bharadwaj.yadavalli@hp.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.