All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Greg KH <greg@kroah.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Chris Bainbridge <chris.bainbridge@gmail.com>
Subject: Re: Cannot create domU
Date: Mon, 26 Sep 2005 16:59:48 +0200	[thread overview]
Message-ID: <43380CE4.6010909@suse.de> (raw)
In-Reply-To: <fe13108c1a010f99eb1dd063df18e4d9@cl.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

   Hi,

> At the moment, installing our script at /etc/hotplug/xen-backend.agent 
> 'just works' for us.

Doesn't work on SUSE Linux 10.0 as well, as all the agents are gone here 
as well.  The huge stack of shell scripts was replaced with a few udev 
rules, so it's easier to see what's going on and it also is much faster.

I've attached my current configuration.  ifup-xen goes to /sbin, the 
rules file into /etc/udev/rules.d.  With those two files in place 
auto-adding interfaces to the bridge WorksForMe[tm].  The script is sort 
of a hack though, quickly created from the vif-bridge script, with no 
way to configure stuff at the moment.

cheers,

   Gerd

[-- Attachment #2: 32-net-xen.rules --]
[-- Type: text/plain, Size: 74 bytes --]

SUBSYSTEM=="net", KERNEL=="vif*", ACTION=="add", RUN+="/sbin/ifup-xen %k"

[-- Attachment #3: ifup-xen --]
[-- Type: text/plain, Size: 829 bytes --]

#!/bin/sh
netdev="$1"
bridge="${bridge:-xenbr0}"

PATH="/sbin:/bin:/usr/sbin:/usr/bin"

# Usage: create_bridge bridge
create_bridge () {
    local bridge=$1

    # Don't create the bridge if it already exists.
    if brctl show | grep -q ${bridge}; then
	return
    fi

    brctl addbr ${bridge}
    brctl stp ${bridge} off
    brctl setfd ${bridge} 0
    ip link set ${bridge} up
}

# Usage: add_to_bridge bridge dev
add_to_bridge () {
    local bridge=$1
    local dev=$2

    # Don't add $dev to $bridge if it's already on a bridge.
    if brctl show | grep -q ${dev} ; then
	return
    fi

    brctl addif ${bridge} ${dev}
    ip link set ${dev} arp off
    ip link set ${dev} up
}

create_bridge ${bridge}
add_to_bridge ${bridge} ${netdev}

echo "$(date): $0: ${bridge} ${netdev}"		>> /tmp/net-xen
env						>> /tmp/net-xen


[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2005-09-26 14:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23 14:15 Cannot create domU NAHieu
2005-09-23 17:37 ` Michael Vrable
2005-09-23 17:43   ` Michael Vrable
2005-09-23 18:00     ` Michael Vrable
2005-09-23 22:39   ` Chris Bainbridge
2005-09-24  7:38     ` Keir Fraser
2005-09-24 10:54       ` Chris Bainbridge
2005-09-24 13:21         ` Keir Fraser
2005-09-24 17:32           ` NAHieu
2005-09-24 20:00           ` Chris Bainbridge
2005-09-25 10:19             ` Keir Fraser
     [not found]             ` <20050926124707.GA13414@kroah.com>
2005-09-26 13:23               ` Keir Fraser
     [not found]                 ` <20050926141407.GA15384@kroah.com>
2005-09-26 14:41                   ` Keir Fraser
2005-09-26 15:01                     ` Greg KH
2005-09-26 15:41                       ` Keir Fraser
2005-09-26 21:22                         ` Greg KH
2005-09-27 15:33                           ` Chris Bainbridge
2005-09-30 14:48                             ` Chris Bainbridge
2005-09-26 14:59                 ` Gerd Knorr [this message]
2005-09-26 15:54                   ` Chris Bainbridge
2005-10-06 15:54                     ` network & block device setup via udev Gerd Knorr

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=43380CE4.6010909@suse.de \
    --to=kraxel@suse.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=chris.bainbridge@gmail.com \
    --cc=greg@kroah.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.