From: Ian Campbell <ian.campbell@citrix.com>
To: Sylvain Munaut <s.munaut@whatever-company.com>,
Roger Pau Monne <roger.pau@citrix.com>
Cc: "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: Thu, 8 Nov 2012 09:26:12 +0100 [thread overview]
Message-ID: <1352363172.12977.87.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <CAF6-1L51R5yMBNO1wQe7YWoeGoM_bFJcAb0XN0cVg6cm7+Kzaw@mail.gmail.com>
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?
Ian.
>
> Cheers,
>
> Sylvain
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-11-08 8:26 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 [this message]
2012-11-09 15:36 ` Roger Pau Monné
2012-11-09 15:46 ` Ian Campbell
2012-11-13 16:49 ` Roger Pau Monné
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=1352363172.12977.87.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=roger.pau@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).