From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Mey Subject: Re: register new block device script Date: Mon, 24 Oct 2005 17:34:54 +0200 Message-ID: <200510241734.54606.michael.mey@to.com> References: <200510241638.49481.michael.mey@to.com> <20051024145941.GF11545@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1937877711==" Return-path: In-Reply-To: <20051024145941.GF11545@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1937877711== Content-Type: multipart/signed; boundary="nextPart17666852.SaEtad2mSp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart17666852.SaEtad2mSp Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline The hotplug/udev infrastructure support is for Xen 3.0, right? Because I=20 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-hotpl= ug > 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=3D/usr/lib/python python /usr/lib/python/xen/util/diagnose.py > > > 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 =2D-=20 =2D------------------------------------------------------------------------= =2D-------------- Michael Mey=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0=20 Thinking Objects Software GmbH =A0 |=A0 mailto: michael.mey@to.com=20 Lilienthalstrasse 2/1 =A0 =A0 =A0 =A0 =A0 =A0 | phone: +49 71= 1 88770-147 70825 Stuttgart-Korntal, Germany =A0| =A0fax: +49 711 88770-449 =2D------------------------------------------------------------------------= =2D-------------- --nextPart17666852.SaEtad2mSp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDXP8e3rj8BeD5OvMRAjfmAJ4xpq7LkYYosdHt/6E+Kk1VV5B3XwCeLoXh 7dgyi3t50xoJrjwmDWEFMW8= =jhEU -----END PGP SIGNATURE----- --nextPart17666852.SaEtad2mSp-- --===============1937877711== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1937877711==--