From: Tomasz Chmielewski <mangoo@wpkg.org>
To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com
Cc: "Angel L. Mateo" <amateo@um.es>,
"Sébastien CRAMATTE" <s.cramatte@wanadoo.fr>,
"Timo Benk" <timo.benk@gmx.de>,
amartins@crefidis.fr, "Javier Guerra" <javier@guerrag.com>,
"Eli Criffield" <elicriffield@gmail.com>,
kfh.xen@kfh.dk, "Daniele Palumbo" <daniele@retaggio.net>
Subject: bonding + VLANs -> Oops/panic, no VLAN on 100 Mbit cards [SOLVED]
Date: Thu, 24 May 2007 15:23:44 +0200 [thread overview]
Message-ID: <465591E0.3070106@wpkg.org> (raw)
As the issue concerns both the -user (configuration) and -devel (OOPS),
I'm sending this message to both lists.
Some time ago I complained about two problems:
- VLANs are not working on machines with 100 Mbit cards
- I get a kernel Oops (sometimes panic) when I try to use bonding and
VLANs with Xen
The root of the issue is the same in both cases: VLAN interfaces must
*not* be brought up before we start our Xen network scripts.
So have four cases with Xen:
1. Bonding + VLAN leads to an Oops
2. Bonding + VLAN works
3. VLANs don't work with 100 Mbit cards
4. VLANs work with 100 Mbit cards
I use network-bridge script shipped with Xen 3.1.
1. Bonding + VLAN leads to an Oops:
ifup bond0
ifup bond0.100
ifup bond0.200
./network-bridge start vifnum=0 netdev=bond0 bridge=xenbr0
./network-bridge start vifnum=1 netdev=bond0.100 bridge=xenbr100
# Ooops (and/or panic) here!
./network-bridge start vifnum=2 netdev=bond0.200 bridge=xenbr200
2. Bonding + VLAN works - note the "enslave":
ifup bond0
./network-bridge start vifnum=0 netdev=bond0 bridge=xenbr0
ifenslave pbond0 eth0 eth1
ifup bond0.100
ifup bond0.200
./network-bridge start vifnum=1 netdev=bond0.100 bridge=xenbr100
./network-bridge start vifnum=2 netdev=bond0.200 bridge=xenbr200
3. VLANs don't work with 100 Mbit cards (with 1 Gbit will work):
ifup eth0
ifup eth0.100
ifup eth0.200
./network-bridge start vifnum=0 netdev=eth0 bridge=xenbr0
./network-bridge start vifnum=1 netdev=eth0.100 bridge=xenbr100
./network-bridge start vifnum=2 netdev=eth0.200 bridge=xenbr200
4. VLANs work with 100 Mbit cards
ifup eth0
./network-bridge start vifnum=0 netdev=eth0 bridge=xenbr0
ifup eth0.100
ifup eth0.200
./network-bridge start vifnum=1 netdev=eth0.100 bridge=xenbr100
./network-bridge start vifnum=2 netdev=eth0.200 bridge=xenbr200
One more note: to use it in startup scripts, I had to put a couple of
"sleep" commands between each line - otherwise, some peth/pbond
interfaces were missing sometimes.
--
Tomasz Chmielewski
http://wpkg.org
reply other threads:[~2007-05-24 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=465591E0.3070106@wpkg.org \
--to=mangoo@wpkg.org \
--cc=amartins@crefidis.fr \
--cc=amateo@um.es \
--cc=daniele@retaggio.net \
--cc=elicriffield@gmail.com \
--cc=javier@guerrag.com \
--cc=kfh.xen@kfh.dk \
--cc=s.cramatte@wanadoo.fr \
--cc=timo.benk@gmx.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.