All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Nivedita Singhvi <nsnix@comcast.net>,
	Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, "Zhai,
	Edwin" <edwin.zhai@intel.com>
Subject: RE: RE: new /etc/xen/network script
Date: Wed, 17 Aug 2005 13:17:49 -0500	[thread overview]
Message-ID: <1124302669.9013.10.camel@localhost.localdomain> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282BB0@liverpoolst.ad.cl.cam.ac.uk>

On Wed, 2005-08-17 at 17:34 +0100, Ian Pratt wrote:
>  > > Thanks, Ian. We'll test later today.
> > I am assuming the new network-bridge script is in the latest 
> > hg pull as of this morning. It seems to have fixed the 
> > problems on the SLES 9 boxes; however, I seem to be having 
> > trouble on the FC3/4 boxes; the domUs on those boxes cannot 
> > connect to the network, even though they seem to be setup 
> > correctly and both worked previously. One has a static IP 
> > address, and the other is setup for dhcp.
> 
> It works on FC3 OK for me.
Well, on the FC4 box, I rebooted Dom0 and created a DomU without
changing anything, and now DomU has network working. Don't know what was
different this time, but it is working. So, I have 2 SLES 9 SP2 boxes
and an FC4 box booted to Dom0 and with functional DomUs now. The FC3 is
the dhcp box, and maybe the dhcp server is out of addresses. 
> 
> Please post the xend.log
> 
> Ian
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides

  reply	other threads:[~2005-08-17 18:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 16:34 RE: new /etc/xen/network script Ian Pratt
2005-08-17 18:17 ` David F Barrera [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-14 18:53 Stephan Böni
2005-10-14 23:23 ` Ewan Mellor
2005-10-14 18:29 Stephan Böni
2005-10-14 18:22 Stephan Böni
2005-10-14 17:16 Stephan Böni
2005-10-14 17:55 ` David F Barrera
2005-08-17 13:30 Zhai, Edwin
2005-08-17 12:47 Zhai, Edwin
2005-08-17 12:34 Ian Pratt
2005-08-17 12:37 ` Nivedita Singhvi
2005-08-17 16:31   ` David F Barrera
2005-08-17 12:19 Zhai, Edwin
2005-08-17 12:34 ` Nivedita Singhvi
2005-08-17 11:44 Ian Pratt
2005-08-17 12:12 ` Nivedita Singhvi
2005-08-17 11:32 Ian Pratt
2005-08-17 11:43 ` Nivedita Singhvi
2005-08-16 16:51 Ian Pratt
2005-08-16 18:53 ` David F Barrera
2005-08-16 16:27 Ian Pratt
2005-08-16 16:41 ` David F Barrera
2005-08-17 10:02 ` Nivedita Singhvi
2005-08-17 11:21   ` Nivedita Singhvi
2005-08-17 11:34     ` Nivedita Singhvi

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=1124302669.9013.10.camel@localhost.localdomain \
    --to=dfbp@us.ibm.com \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=edwin.zhai@intel.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=nsnix@comcast.net \
    --cc=xen-devel@lists.xensource.com \
    /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.