From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Cannot create domU
Date: Fri, 30 Sep 2005 15:48:01 +0100 [thread overview]
Message-ID: <623652d50509300748w795b76f7n@mail.gmail.com> (raw)
In-Reply-To: <623652d5050927083376275f75@mail.gmail.com>
I finally got it working under Gentoo by abandoning all the hotplug
stuff and just using a few udev rules:
xen udev # cat rules.d/49-xen.rules
SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="online",
RUN+="/etc/xen/scripts/launch up"
SUBSYSTEM=="xen-backend", KERNEL=="vbd*", ACTION=="add",
RUN+="/etc/xen/scripts/vbd-add %k"
SUBSYSTEM=="xen-backend", KERNEL=="vbd*", ACTION=="remove",
RUN+="/etc/xen/scripts/vbd-remove %k"
SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="remove",
RUN+="/etc/xen/scripts/vif-remove %k"
xen udev # cd /etc/xen/scripts/
xen scripts # cat launch
#!/bin/sh
# the script is specified in xend config
# and passed to us. we just call it.
export PATH="/sbin:/bin:/usr/sbin:/usr/bin:$PATH"
#echo "$(date): launch $1"
#env
#echo "Running ${script} $1"
${script} $1
xen scripts # cat vbd-add
#!/bin/sh
t=$(xenstore-read "$XENBUS_PATH"/type)
params=$(xenstore-read "$XENBUS_PATH"/params)
[ -x /etc/xen/scripts/block-"$t" ] && \
/etc/xen/scripts/block-"$t" bind $params
xen scripts # cat vbd-remove
#!/bin/sh
t=$(xenstore-read "$XENBUS_PATH"/type)
node=$(xenstore-read "$XENBUS_PATH"/node)
[ -x /etc/xen/scripts/block-"$t" ] && \
/etc/xen/scripts/block-"$t" unbind $node
# remove device backend store entries
xenstore-rm "$XENBUS_PATH"
xen scripts # cat vif-remove
#!/bin/sh
# remove device backend store entries
xenstore-rm "$XENBUS_PATH"
/sbin/ip link set ${dev} down
/sbin/brctl delif ${bridge} ${dev}
next prev parent reply other threads:[~2005-09-30 14:48 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 [this message]
2005-09-26 14:59 ` Gerd Knorr
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=623652d50509300748w795b76f7n@mail.gmail.com \
--to=chris.bainbridge@gmail.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.