From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: missing block script support for qemu in libxl
Date: Wed, 18 Nov 2015 10:25:31 +0100 [thread overview]
Message-ID: <20151118092531.GA20778@aepfle.de> (raw)
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
next reply other threads:[~2015-11-18 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 9:25 Olaf Hering [this message]
2015-11-18 9:35 ` missing block script support for qemu in libxl George Dunlap
2015-11-18 9:38 ` George Dunlap
2015-11-18 9:45 ` Olaf Hering
2015-11-19 11:30 ` Paul Durrant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151118092531.GA20778@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.