|
xen-devel
Re: [Xen-devel] Networking in dom0
Hi Brian -
You're right that a default route is not required for networking in general.
But it looks like the network-bridge script hasn't been working with no args
and no default route since changeset 8814:
http://xenbits.xensource.com/xen-unstable.hg?cs=d1596fc2cbaa
I guess the script should fall back to guessing eth0/xenbr0 if there
is no default route. I've attached a (completely untested) patch that
does this. Could you give it a try and let me know whether it works
for you? (Apply with 'patch -p1 < network-bridge-fix.patch' run from
the top-level xen-unstable directory.)
Dave
On 5/24/06, Carb, Brian A <Brian.Carb@xxxxxxxxxx> wrote:
Dave,
We get nothing back from 'ip route list default scope global'. You are
correct that we do not define a default gateway, although i don't
believe it is required for linux networking, and we never have defined
one. Xen networking components did get created for us at some previous
changest level, although I'm not sure exactly when they stopped working.
brian carb
unisys corporation - malvern, pa
brian.carb@xxxxxxxxxx
-----Original Message-----
From: Dave Lively [mailto:dave.lively@xxxxxxxxx]
Sent: Wednesday, May 24, 2006 11:14 AM
To: Carb, Brian A
Cc: Krysan, Susan; Puthiyaparambil, Aravindh; Xen devel list
Subject: Re: [Xen-devel] Networking in dom0
[Re-cc'd xen-devel, so they can see what's going on here ...]
Thanks Brian. The 'ip route list' output you helpfully provided shows
the problem: you have no default route. A default route will show up in
'ip route list' as something like:
default via x.x.x.x dev eth0
Since changeset 9995 (roughly a week ago), the network-bridge script has
depended on being able to find the default route from the 'ip route
list'
output (if you don't specify a vifnum explicitly). I didn't make that
change (though I modified it later), so I'm not sure whether your
configuration would have worked 'as is' with the old code or not. Do
you get anything back from: 'ip route list default scope global'?
Dave
On 5/24/06, Carb, Brian A <Brian.Carb@xxxxxxxxxx> wrote:
>
>
> Dave,
>
> I ran the shell lines you suggested and they produce no output.
> However, the result of 'ip route list' is:
>
>
> 169.254.0.0/16 dev eth0 scope link
> 10.0.0.0/15 dev eth0 proto kernel scope link src 10.0.75.1
> 127.0.0.0/8 dev lo scope link
>
>
> brian carb (610-648-2437 or N2 385-2437) unisys corporation - malvern,
> pa brian.carb@xxxxxxxxxx
>
> ________________________________
> From: Dave Lively [mailto:dave.lively@xxxxxxxxx]
> Sent: Tuesday, May 23, 2006 9:00 PM
> To: Carb, Brian A
> Cc: Krysan, Susan; Puthiyaparambil, Aravindh
>
> Subject: Re: [Xen-devel] Networking in dom0
>
>
> I made a recent change (cset 10051) in the default vifnum calculation
> to make someone else's recent change (cset 9981) work with
> less-capable versions of awk (such as the busybox version). So I
> figure there's close to a 50/50 chance I'm the one who broke this for
> you all :-)
>
> To help me get to the bottom of this, could you please send me the
> output of the following dom0 shell command lines (run as root, after
xend started):
> (a) ip route list | awk '/^default / { print $NF }' | sed -r
's/[^0-9]+//'
> (b) ip route list | awk '/^default / { sub(/^(eth|xenbr)/,"",$NF);
> print $NF }'
> (c) ip route list | awk '/^default / { sub(/eth/,"",$NF); print $NF }'
>
> Thanks,
> Dave
>
> On 5/23/06, Carb, Brian A <Brian.Carb@xxxxxxxxxx> wrote:
> > Keir
> >
> > This doesn't seem to be working out of the box. I see this behavior
> > on a
> Dell 2x X86_64 platform, as well as on the Unisys ES7000/one. Any
> ideas on what the problem might be? We've entered bugzilla 656 to
track it. Thanks.
> >
> >
> > brian carb (610-648-2437 or N2 385-2437) unisys corporation -
> > malvern, pa brian.carb@xxxxxxxxxx
> >
> > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
> > PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the
> e-mail and its attachments from all computers.
> >
> > -----Original Message-----
> > From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
> > Sent: Tuesday, May 23, 2006 3:20 AM
> > To: Carb, Brian A
> > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Puthiyaparambil, Aravindh;
> > Krysan,
> Susan
> > Subject: Re: [Xen-devel] Networking in dom0
> >
> >
> > On 22 May 2006, at 20:50, Carb, Brian A wrote:
> >
> > > Hello,
> > >
> > > I'm running xen-unstable, changeset 10058,on sles10RC1-
> > > x86_64.When I build xen-unstable, boot dom0, and type ifconfig, I
> > > only see 2 network interfaces - eth0 and lo. The xen interfaces
> > > such as peth0 and xenbr0 do not show up. However, if I edit
> > > /etc/xen/xend-config.sxp and change the (network-script
> > > network-bridge) statement to (network-script 'network-bridge
> > > vifnum=0') and restart xend, the xen network interfaces are
> > > configured and show up when I type ifconfig. I was under the
> > > impression from the documentation that default values are used in
> > > the network-bridge script, and that no parameters need to be
specified. Can someone clarify this?
> >
> >
> > That's supposed to be the case, yes (ie. yes, it should usually work
> > out
> of the box).
> >
> > -- Keir
> >
> >
> > > brian carb
> > > unisys cmp technology lab
> > > malvern, pa
> > >
> brian.carb@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
>
network-bridge-fix.patch
Description: Text Data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home