From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir@xensource.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace
Date: Tue, 5 Jun 2007 17:36:19 +0100 [thread overview]
Message-ID: <20070605163619.GE15012@redhat.com> (raw)
In-Reply-To: <C28B4B2E.10161%keir@xensource.com>
On Tue, Jun 05, 2007 at 05:17:34PM +0100, Keir Fraser wrote:
> On 4/6/07 15:12, "Gerd Hoffmann" <kraxel@redhat.com> wrote:
>
> > I'd rather name the things what they are. Name the ethernet interface
> > eth0, name the bridge xenbr0 or virtbr0 or just br0. Drop peth0. The
> > only reason for the renaming was to trick the distro setup scripts by
> > doing "ifdown eth0; bridge-setup (with eth0 -> peth0 and veth0 -> eth0);
> > ifup eth0".
>
> That trick still applies though, right? Just with xenbr0->eth0. The decision
> to use or not use this trick seems orthogonal to whether or not we have the
> veth0/vif0.0 loopback.
Yeah, I think the key point was that whatever interface you end up using
to configure the IP addr on should be eth0. So if the scripts configure
the IP on the bridge, then the bridge must be called eth0. This is so
that the admin's post-ifup scripts for eth0 get run correctly. If you
further changed vif-bridge so that it kept the IP addr on the physical
interface instead, you could keep it called eth0 and name the bridge as
something else. Now that netloop isn't involved, either of those two
IP config scenarios should work fine.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-06-05 16:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 4:55 [1/3] [XEN] gnttab: Add new op unmap_and_replace Herbert Xu
2007-05-29 4:55 ` [2/3] [LINUX] gnttab: Add basic DMA tracking Herbert Xu
2007-06-06 6:18 ` Isaku Yamahata
2007-06-06 8:37 ` Herbert Xu
2007-06-06 12:35 ` Herbert Xu
2007-06-07 4:32 ` [LINUX] gnttab: Fix copy_grant_page race with seqlock Herbert Xu
2007-06-07 8:36 ` [2/3] [LINUX] gnttab: Add basic DMA tracking Isaku Yamahata
2007-06-07 8:44 ` Isaku Yamahata
2007-06-07 8:48 ` was " Isaku Yamahata
2007-06-07 8:51 ` Herbert Xu
2007-05-29 4:55 ` [3/3] [NET] back: Add lazy copying Herbert Xu
2007-05-30 11:50 ` [1/3] [XEN] gnttab: Add new op unmap_and_replace Keir Fraser
2007-05-30 13:09 ` Herbert Xu
2007-06-03 2:01 ` Herbert Xu
2007-06-04 12:29 ` Keir Fraser
2007-06-04 12:39 ` Herbert Xu
2007-06-04 13:15 ` Keir Fraser
2007-06-04 13:22 ` Daniel P. Berrange
2007-06-04 13:12 ` Daniel P. Berrange
2007-06-04 13:18 ` Keir Fraser
2007-06-04 13:29 ` Daniel P. Berrange
2007-06-04 14:12 ` Gerd Hoffmann
2007-06-05 16:17 ` Keir Fraser
2007-06-05 16:36 ` Daniel P. Berrange [this message]
2007-06-06 7:54 ` Gerd Hoffmann
2007-06-12 17:10 ` Keir Fraser
2007-06-14 7:41 ` Gerd Hoffmann
2007-06-14 11:01 ` Daniel P. Berrange
2007-06-06 7:50 ` Gerd Hoffmann
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=20070605163619.GE15012@redhat.com \
--to=berrange@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keir@xensource.com \
--cc=kraxel@redhat.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.