From: Nivedita Singhvi <niv@us.ibm.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Li Ge <lge@us.ibm.com>, Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: Network script handling changes
Date: Wed, 02 Nov 2005 09:33:08 -0800 [thread overview]
Message-ID: <4368F854.2000402@us.ibm.com> (raw)
In-Reply-To: <20051102171948.GD408@leeni.uk.xensource.com>
Ewan Mellor wrote:
> On Wed, Nov 02, 2005 at 10:50:44AM -0600, Li Ge wrote:
>
>
> No, the settings look right. Of course, I presume that you have noticed that
> my wrapper script is not quite right -- it does not pass the "start" command
> through to network-bridge.
Ewan, there seems to be an underlying problem that some people
are hitting more frequently than others - the virtual interface
just doesn't get created, and it seems to be non-deterministic
(occasionally passes). So we suspect yet another timing hole,
from what I can tell. Will have more for you today, although
there are a couple of other issues we're sidetracked on..
Getting trace output (set -x) from the scripts from everybody
would be good..
thanks,
Nivedita
> Even when you run network-bridge manually, it still hasn't worked though. Do
> you get any error messages in /var/log/debug, /var/log/syslog, etc? One
> obvious problem is that you have no vif0.1 interface, which is the one that
> connects from your new eth1 to xenbr1. I presume that the script is bailing
> out early for some reason -- it would be good if you could figure out where it
> stops, and why.
>
> Could you open a bug, and attach the output of
>
> brctl show
> ifconfig
> route
> iptables -L
>
> before and after running
>
> /etc/xen/scripts/network-bridge vifnum=0 start
> /etc/xen/scripts/network-bridge vifnum=1 start
>
> This should give us good clues to help with the debugging.
>
> Thanks a lot,
>
> Ewan.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-11-02 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 16:52 Network script handling changes Ewan Mellor
2005-10-31 17:05 ` Ewan Mellor
2005-11-02 2:53 ` Greg Brackley
2005-11-03 4:39 ` Greg Brackley
2005-11-02 16:50 ` Li Ge
2005-11-02 17:19 ` Ewan Mellor
2005-11-02 17:33 ` Nivedita Singhvi [this message]
2005-11-02 19:28 ` Li Ge
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=4368F854.2000402@us.ibm.com \
--to=niv@us.ibm.com \
--cc=ewan@xensource.com \
--cc=lge@us.ibm.com \
--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.