All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Haxby <john.haxby@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Re: xen-unstable on OL6 (RHEL6 clone) problems
Date: Fri, 11 Feb 2011 16:53:14 +0000	[thread overview]
Message-ID: <4D55697A.5060409@oracle.com> (raw)
In-Reply-To: <1297410584.3221.1436.camel@localhost.localdomain>

On 11/02/11 07:49, Ian Campbell wrote:
> The upgrade notes should continue to consistently point to the relevant
> distro documentation and to provide associated guidance.

I hesitate to just say "me too" but but Ian is dead right here.  The
examples in http://wiki.xensource.com/xenwiki/MigrationGuideToXen4.1+
that Dan has just referred me to are exactly what's needed here.  The
real documentation for RHEL et alia
(/usr/share/doc/initscripts-*/sysconfig.txt) are as close as you'll get
to definitive without reading the shell scripts, but the examples are
the perfect start.

While I'm talking about bridges though, RHEL6 (and clones including OL6)
have a problem with brctl.  RHEL6 adds IGMP snooping support for bridges
and this is provided by kernel patches.  If you're using the xen dom0
kernel this support is not present and brctl complains bitterly and
repeatedly that /sys/class/net/xenbr0/bridge (or similar) doesn't
exist.  What is actually means is that a various files in that directory
don't exist.   Luckily, Fedora 14's bridge-utils-1.2-9.fc13 RPM doesn't
expect the IGMP snooping stuff and works perfectly on the dom0 kernel.  
You could also rebuild the RHEL6 bridge-utils RPM and just miss out
bridge-utils-1.2-Add_IGMP_snooping_support.patch

jch

  parent reply	other threads:[~2011-02-11 16:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 22:26 xen-unstable on OL6 (RHEL6 clone) problems Dan Magenheimer
2011-02-09 23:13 ` Todd Deshane
2011-02-09 23:49   ` Dan Magenheimer
2011-02-10  0:22     ` Dan Magenheimer
2011-02-10  1:38       ` Todd Deshane
2011-02-10  1:54         ` Fajar A. Nugraha
2011-02-10  2:15           ` Todd Deshane
2011-02-10  2:38             ` Dan Magenheimer
2011-02-10  3:18               ` Todd Deshane
2011-02-10  8:29                 ` Ian Campbell
2011-02-10 12:53                 ` Ian Jackson
2011-02-10 17:48                 ` Dan Magenheimer
2011-02-10 17:56                   ` Stefano Stabellini
2011-02-11  3:09                     ` Todd Deshane
2011-02-11  7:49                       ` Ian Campbell
2011-02-11 11:44                         ` Stefano Stabellini
2011-02-11 11:57                           ` Ian Campbell
2011-02-11 12:08                             ` Stefano Stabellini
2011-02-11 17:30                               ` Dan Magenheimer
2011-02-11 17:50                                 ` Todd Deshane
2011-02-12 16:03                                 ` John Haxby
2011-02-11 16:53                         ` John Haxby [this message]
2011-02-11 19:17                           ` Pasi Kärkkäinen
2011-02-11 11:42                       ` Stefano Stabellini
2011-02-10  8:32         ` Ian Campbell
2011-02-10 15:19           ` Todd Deshane
2011-02-10  8:30     ` Ian Campbell
2011-02-10 18:07       ` Dan Magenheimer
2011-02-10 19:25         ` Ian Jackson
2011-02-10 19:45           ` Dan Magenheimer
2011-02-11 15:30             ` George Dunlap
2011-02-11  7:48           ` Ian Campbell
2011-02-10  7:18 ` Pasi Kärkkäinen
2011-02-10 17:55   ` Dan Magenheimer
2011-02-10 18:00     ` Pasi Kärkkäinen

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=4D55697A.5060409@oracle.com \
    --to=john.haxby@oracle.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.