RE: [Xen-devel] When is "physical-device" created in xenstore?

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

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. ;-(

Thanks,
Kevin

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian, Kevin
>Sent: 2005年9月20日 16:37
>To: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-devel] When is "physical-device" created in xenstore?
>
>Saw a strange problem. When blkfront writes event channel number and
>ring-ref to xenstore, the watch registered by blkback is notified.
>However immediately watch handler in blkback found there's no
>"physical-device" under xenstore which should refer to major/minor
>number of device for domU. Then failed to create vbd and finally the
>connection can't be setup.
>
>So my puzzle is, when should physical-device be created? And who creates
>this item? I searched for name string in whole tools directory to only
>find instance in block-file/block-phy/block-endb. I configured disk
>image by /dev/loop0, so ideally block-phy should be used. However I
>still failed to find where block-phy is invoked.
>
>Any clues?
>
>Thanks,
>Kevin
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel

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