From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: When is "physical-device" created in xenstore? Date: Tue, 20 Sep 2005 14:12:08 +0100 Message-ID: <20050920131208.GA10070@uk.xensource.com> References: <571ACEFD467F7749BC50E0A98C17CDD802C0686E@pdsmsx403> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <571ACEFD467F7749BC50E0A98C17CDD802C0686E@pdsmsx403> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Sep 20, 2005 at 07:41:09PM +0800, Tian, Kevin wrote: > If making following temp hack in XendDomainInfo.py: > > back = { 'type' : type, > 'params' : params, > 'frontend' : frontpath, > - 'frontend-id' : "%i" % self.domid } > + 'frontend-id' : "%i" % self.domid, > + 'physical-device' : "%li" % blkdev_name_to_number(params) } > xstransact.Write(backpath, back) > > Then physical-device is created under backend and the communication can be > setup. However this hard code definitely breaks existing logical > behind. Should I do any specific configuration? From the Blkctl.py, it said > that "phy" type doesn't require bind/unbind script, but I didn't find the > place to add that item specifically. ;-( Hi Kevin, The key physical-device is created inside the block-phy script, as I think you found. This is called by xen-backend.agent, which in turn is called by the Linux hotplug system (keying off the name 'xen-backend'). The file Blkctl.py is completely unused, AFAICT, and should be removed. The problems that you are having starting your device are probably down to a broken or nonexistent installation of the hotplug system. You should check that first. If your hotplug system is working, then maybe you are failing to find xenstore-write. HTH, Ewan.