From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Pre-domain released event?
Date: Mon, 14 Dec 2015 18:23:38 +0200 [thread overview]
Message-ID: <566EED0A.70709@bitdefender.com> (raw)
Hello,
Currently, all the in-tree examples that figure out that a domain has
been shut down subscribe to xenstore's @releaseDomain combined with an
xs_is_domain_introduced() check. That works fine if you're only
interested that the domain no longer exists. However, I'd like to be
able to do some cleanup before a domain is suspended (on taking a
snapshot, for example).
There are various degrees of tolerability doing this if I subscribe to
various xenstore paths that disappear before @releaseDomain gets fired,
and before the guest disappears, but it looks like it's not always
foolproof.
I've previously asked the question in a somewhat more convoluted manner
here: http://lists.xen.org/archives/html/xen-devel/2015-08/msg00735.html
I'm still interested in what the best solution would be here. A new,
blocking vm_event, that fires from the hypervisor immediately after it's
decided that the guest will be shutdown is what comes to mind, but I'm
not sure where the best place to put it would be. Or indeed if there
another / better way to do this.
Thanks,
Razvan
reply other threads:[~2015-12-14 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=566EED0A.70709@bitdefender.com \
--to=rcojocaru@bitdefender.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 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.