From: Olaf Hering <olaf@aepfle.de>
To: Jim Fehlig <jfehlig@suse.com>
Cc: xen-users@lists.xen.org, xen-devel <xen-devel@lists.xen.org>,
Olaf Hering <OHering@suse.com>,
Ian Campbell <ian.campbell@citrix.com>,
Andreas Pflug <pgadmin@pse-consulting.de>
Subject: Re: Missing libvirt+libxl functionality (Was: Re: [Xen-users] Programmatic administration of Xen machines)
Date: Fri, 8 Jan 2016 07:51:22 +0100 [thread overview]
Message-ID: <20160108065122.GA22648@gmail.com> (raw)
In-Reply-To: <568F4EF9.2090609@suse.com>
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
next prev parent reply other threads:[~2016-01-08 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+v+Np+eT=mmyt-ZicW1uY4358FP5bCmDrivXU=kw2uTL--i0A@mail.gmail.com>
[not found] ` <56812352.8060500@pse-consulting.de>
[not found] ` <1451907382.13361.37.camel@citrix.com>
[not found] ` <568A5BEE.9090808@pse-consulting.de>
[not found] ` <1451909615.13361.46.camel@citrix.com>
[not found] ` <568A6618.5@pse-consulting.de>
2016-01-04 12:37 ` Missing libvirt+libxl functionality (Was: Re: [Xen-users] Programmatic administration of Xen machines) Ian Campbell
2016-01-08 5:54 ` Jim Fehlig
2016-01-08 6:51 ` Olaf Hering [this message]
2016-01-08 12:46 ` Ian Campbell
2016-01-09 1:48 ` Jim Fehlig
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=20160108065122.GA22648@gmail.com \
--to=olaf@aepfle.de \
--cc=OHering@suse.com \
--cc=ian.campbell@citrix.com \
--cc=jfehlig@suse.com \
--cc=pgadmin@pse-consulting.de \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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.