From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 1/2] libxl: fix usage of backend parameter and run_hotplug_scripts
Date: Thu, 6 Sep 2012 10:30:30 +0200 [thread overview]
Message-ID: <50485F26.4070400@citrix.com> (raw)
In-Reply-To: <1346916542.10570.18.camel@dagon.hellion.org.uk>
Ian Campbell wrote:
> On Tue, 2012-09-04 at 16:16 +0100, Roger Pau Monne wrote:
>> vif interfaces allows the user to specify the domain that should run
>> the backend (also known as driver domain) using the 'backend'
>> parameter. This is not compatible with run_hotplug_scripts=1, since
>> libxl can only run the hotplug scripts from the Domain 0.
>
> Sorry but I think in the end this has missed the cut-off for 4.2.0 (we
> are cutting the final RC tomorrow).
>
> We should be branching soon after the final RC which means 4.3
> development will open in unstable shortly. We should take this into
> unstable then and consider it for 4.2.1.
>
> In the meantime I suppose we should mention this in the release notes.
Do you think we could commit the docs change
(xl-network-configuration.markdown) only? So people can know that this
won't work in current release.
Sorry for the delay.
next prev parent reply other threads:[~2012-09-06 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 15:16 [PATCH v2 1/2] libxl: fix usage of backend parameter and run_hotplug_scripts Roger Pau Monne
2012-09-04 15:16 ` [PATCH v2 2/2] xl: error if vif backend!=0 is used with run_hotplug_scripts Roger Pau Monne
2012-09-14 9:06 ` Ian Campbell
2012-09-06 7:29 ` [PATCH v2 1/2] libxl: fix usage of backend parameter and run_hotplug_scripts Ian Campbell
2012-09-06 8:30 ` Roger Pau Monne [this message]
2012-09-06 8:48 ` Ian Campbell
2012-09-14 9:06 ` Ian Campbell
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=50485F26.4070400@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).