From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: missing block script support for qemu in libxl Date: Wed, 18 Nov 2015 10:25:31 +0100 Message-ID: <20151118092531.GA20778@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Why does libxl now allow script= with backend=tap|qdisk? See tools/libxl/libxl_device.c:disk_try_backend. Ideally the script should prepare the backend storage based on info from target=. Then the script should report either the dentry to be used by qemu back to libxl, or it should setup the "physical-device" entry to be used by blkback. Right now the target= info is passed to the script, but its also used as ->pdev_path for qemu. Obvisouly qemu cant possibly make sense of the target= info, because its meant for the script=. tools/libxl/check-xl-disk-parse has some script examples. I think right now its not possible to boot an HVM guest from iscsi, for example. Should the logic in libxl be changed to make scripts= more useful, and let libxl read info for qemu which has to be provided by the script? Olaf