From: Michael Mey <michael.mey@to.com>
To: xen-devel@lists.xensource.com
Subject: Re: register new block device script
Date: Mon, 24 Oct 2005 17:34:54 +0200 [thread overview]
Message-ID: <200510241734.54606.michael.mey@to.com> (raw)
In-Reply-To: <20051024145941.GF11545@leeni.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2202 bytes --]
The hotplug/udev infrastructure support is for Xen 3.0, right? Because I
downloaded the latest sources of Xen-stable last week.
After rechecking all of my steps, it finally works fine :)
Regards,
Mike
On Monday 24 October 2005 16:59, Ewan Mellor wrote:
> On Mon, Oct 24, 2005 at 04:38:39PM +0200, Michael Mey wrote:
> > Hi all,
> >
> > I'd like to develop a new script for block-devices.
> > Where do I have to register it?
> >
> > It's for DRBD block devices. It's called 'block-drbd' .
> > I tried the following steps:
> >
> > 1) copy it in /etc/xen/scripts
> > 2) register it in /etc/xen/xend-config.sxp :
> > # Setup script for drbd block devices
> > (block-drbd block-drbd)
>
> There's no need to do this. This is out-of-date stuff from the pre-hotplug
> days. I removed these examples last week, in fact, so you may want to
> update your config file.
>
> These scripts are now called by the hotplug/udev infrastructure. There
> should be no need to register the script as such -- xen-backend.agent
> should be called by udev, and then that will call /etc/xen/scripts/block,
> which in turn will call /etc/xen/scripts/block-drdb.
>
> Have a look in your syslog files (particularly the debug level one,
> e.g. /var/log/debug) and maybe add some tracing to those files, to see
> where it gets stuck.
>
> You might also want to try
>
> PYTHONPATH=/usr/lib/python python /usr/lib/python/xen/util/diagnose.py
> <dom>
>
> which at least will tell you whether the store entries for the device have
> been created correctly.
>
> Cheers,
>
> Ewan.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
----------------------------------------------------------------------------------------
Michael Mey
Thinking Objects Software GmbH | mailto: michael.mey@to.com
Lilienthalstrasse 2/1 | phone: +49 711 88770-147
70825 Stuttgart-Korntal, Germany | fax: +49 711 88770-449
----------------------------------------------------------------------------------------
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2005-10-24 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 14:38 register new block device script Michael Mey
2005-10-24 14:43 ` Mark Williamson
2005-10-24 15:32 ` Michael Mey
2005-10-24 14:59 ` Ewan Mellor
2005-10-24 15:34 ` Michael Mey [this message]
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=200510241734.54606.michael.mey@to.com \
--to=michael.mey@to.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.