From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Sylvain Munaut <s.munaut@whatever-company.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Custom block script started twice for root block but only stopped once
Date: Tue, 13 Nov 2012 17:49:59 +0100 [thread overview]
Message-ID: <50A27A37.2090506@citrix.com> (raw)
In-Reply-To: <509D22E6.2090005@citrix.com>
On 09/11/12 16:36, Roger Pau Monné wrote:
> On 08/11/12 09:26, Ian Campbell wrote:
>> On Fri, 2012-11-02 at 10:37 +0000, Sylvain Munaut wrote:
>>> Hi,
>>>
>>> I'm using a custom block script in my xen setup and when started, it
>>> creates a new device node pointing to some network resources.
>>>
>>> Now I noticed that the script is called twice for the root block, the
>>> first time for pygrub most likely, but is only stopped once ... I
>>> don't mind creating two devices node, but then I need to destroy both
>>> ...
>>>
>>> Is this a known issue ?
>>
>> Not one I've heard. Running "xl -vvv create" might provide some logs
>> which give an idea what is going on, likewise the logging
>> in /var/log/xen/...
>>
>> Roger -- any ideas?
>
> Yes, I've been able to reproduce the error when using stubdoms, I'm
> currently working on a fix. Have you seen this when using stubdomains
> Sylvain?
I've been thinking about this, and I think it's the right thing to do to
call hotplug scripts twice when using stubdomains. Each script gets
called for the corresponding PV interface of each guest. Here is a
stripped trace of the creation of a guest with a stubdomain:
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 46 - calling hotplug script: /etc/xen/scripts/block add
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 47 - calling hotplug script: /etc/xen/scripts/block add
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 47 - calling hotplug script: /etc/xen/scripts/vif-bridge online
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 46 - calling hotplug script: /etc/xen/scripts/vif-bridge online
[...]
And the destruction:
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 47 - calling hotplug script: /etc/xen/scripts/block remove
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 47 - calling hotplug script: /etc/xen/scripts/vif-bridge offline
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 46 - calling hotplug script: /etc/xen/scripts/block remove
[...]
libxl: debug: libxl_device.c:919:device_hotplug: for-domain: 46 - calling hotplug script: /etc/xen/scripts/vif-bridge offline
[...]
So hotplug script gets called twice for both creation and
destruction. Can you run a guest creation/destruction with
-vvv and provide the output?
next prev parent reply other threads:[~2012-11-13 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 10:37 Custom block script started twice for root block but only stopped once Sylvain Munaut
2012-11-08 8:26 ` Ian Campbell
2012-11-09 15:36 ` Roger Pau Monné
2012-11-09 15:46 ` Ian Campbell
2012-11-13 16:49 ` Roger Pau Monné [this message]
2012-11-26 13:45 ` Sylvain Munaut
2012-12-04 14:21 ` Sylvain Munaut
2012-12-04 15:23 ` Sylvain Munaut
2012-12-04 15:34 ` Roger Pau Monné
2012-12-04 15:28 ` Roger Pau Monné
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=50A27A37.2090506@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=s.munaut@whatever-company.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).