From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Missing libvirt+libxl functionality (Was: Re: [Xen-users] Programmatic administration of Xen machines) Date: Fri, 8 Jan 2016 07:51:22 +0100 Message-ID: <20160108065122.GA22648@gmail.com> References: <56812352.8060500@pse-consulting.de> <1451907382.13361.37.camel@citrix.com> <568A5BEE.9090808@pse-consulting.de> <1451909615.13361.46.camel@citrix.com> <568A6618.5@pse-consulting.de> <1451911062.13361.60.camel@citrix.com> <568F4EF9.2090609@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <568F4EF9.2090609@suse.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jim Fehlig Cc: xen-users@lists.xen.org, xen-devel , Olaf Hering , Ian Campbell , Andreas Pflug List-Id: xen-devel@lists.xenproject.org On Thu, Jan 07, Jim Fehlig wrote: > The 'iscsi:iqn.2006-09.de.suse@0ac47ee2-216e-452a-a341-a12624cd0225' blob was > passed wholesale to xend, which would eat it and "do the right thing". AFAIK, > libxl is not that forgiving. I've cc'd Olaf on this thread since we recently > discussed how libvirt+libxl might support external block scripts. As I recall, > we didn't have an novel ideas. I think the "raw" string is known to libvirts libxl driver. It could do a strncmp() and fill also ->script. Then libxl would call that thing by itself, libvirt does not need to know about such internals. Of course that would mean an additional "script=$path" is still not supported by libvirt. But thats not a loss because whoever is relying on can just copy its own file into XEN_SCRIPT_DIR. After all only our own dmmd thing requires a script because that is its whole purpose (carry the block configuration along with the vm configuration). Olaf