Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Mar 2016 10:08:14 +0100
From:      =?UTF-8?Q?Gustau_P=c3=a9rez?= <gustau.perez@gmail.com>
To:        =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>, FreeBSD XEN <freebsd-xen@freebsd.org>
Subject:   Re: Porting the block-iscsi hotplug script
Message-ID:  <56D7FEFE.9050000@gmail.com>
In-Reply-To: <56D6B68D.8080809@citrix.com>
References:  <553DEB97.5000300@entel.upc.edu> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com> <555EF542.3090002@citrix.com> <555F9B3F.1000600@entel.upc.edu> <55602512.1090702@citrix.com> <56C6FA2F.8040900@gmail.com> <56CAC8CB.8030107@gmail.com> <56CADEDA.4050007@citrix.com> <56CB0057.1060509@gmail.com> <56CB041E.1020009@citrix.com> <56CB2D90.5080809@gmail.com> <56CB34BA.6060809@citrix.com> <56CC24BD.6050609@gmail.com> <56CC32E5.5010101@citrix.com> <56CC7637.3080408@gmail.com> <56CF5668.6090605@citrix.com> <56D0091F.80408@gmail.com> <56D02863.7040100@citrix.com> <56D03D95.9090509@gmail.com> <56D04E5F.8070901@citrix.com> <56D42A28.8050701@gmail.com> <56D434FC.8030905@citrix.com> <56D57110.2060406@gmail.com> <56D587D8.6030702@citrix.com> <56D590EA.609@gmail.com> <56D591BA.4020303@gmail.com> <56D5929F.7040001@citrix.com> <56D5C722.3080205@gmail.com> <56D6B68D.8080809@citrix.com>

next in thread | previous in thread | raw e-mail | index | archive | help


El 2/03/16 a les 10:46, Roger Pau Monné ha escrit:
>
> There's a little shortcut in libxl to deal with disks that are using the
> default hotplug script, see:
>
> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/libxl/libxl.c;h=4cdc1690c4d5e5d5b66c896e4c11e813be92b468;hb=HEAD#l2451
>
> libxl does the hotplug script job and already writes the xenstore
> "physical-device" node on behalf of the hotplug script. This is done to
> speed up domain creation.
>
> You can disable this shortcut by spelling out the hotplug script on each
> disks configuration line. Using the configuration file you posted in [2]
> as an example, you will need to change your disk configuration lines so
> they look like:
>
> disk = [
>     'vdev=xvda,access=rw,script=block,target=/dev/zvol/dades/debian',
>     'vdev=xvdb,access=rw,script=block,target=/dev/zvol/dades/debian_1',
>         ]
>
> This will prevent libxl from writing the "physical-device" node.

   Thank you. That makes it. I'm using a simpler form like:

           phy:/dev/zvol/dades/debian,xvda,rw,script=block',

   which behaves in the same way.
>
>>    On the other hand, if I attach two disks[2], the xenstored again
>> complains about one of the disks already declared in the xenstore.
>> However the store seem to be fine [3].  If I remove that disk from the
>> definition the domain boots just fine.
> According to [2], you are assigning the same vdev to both disks (xvda).
> This is not possible, you should change the second disk definition to:
>
> 'phy:/dev/zvol/dades/debian_1,xvdb,rw'
>
> Or any other xvd* value that's not xvda.

    Ah, you're right. Cut and paste betrayed me :) However perhaps the
error message may be misleading (it made me think the error was the
volume, no the given virtual disk).

> http://www.informit.com/articles/article.aspx?p=1160234 

   Very  interesting. I'd need some time to read it through.

   I'm checking the libxl code and I'd like to pass more arguments to
the script. I'll modify libxl/libxl_freebsd.c to do so. I'll let you
know my experiments.

   Thank you,

   Gustau

  




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56D7FEFE.9050000>