xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Bruce Granger <vivagin@yeah.net>, xen-devel@lists.xensource.com
Subject: Re: How could Xen know a certain GuestOS have already shutdown?
Date: Fri, 21 Sep 2012 09:06:01 +0100	[thread overview]
Message-ID: <CC81DE79.3F4C6%keir.xen@gmail.com> (raw)
In-Reply-To: <1348197814609-5711421.post@n5.nabble.com>


[-- Attachment #1.1: Type: text/plain, Size: 1579 bytes --]

When the guest shuts down, Xen sends VIRQ_DOM0_EXC to dom0. This is picked
up by xenstored which fires the @releaseDomain watch. Anyone in dom0 can
register on that watch. Or see libxl__domaindeathcheck_* functions in
libxl/libxl_event.c for another method to pick up on domain shutdowns.

 -- Keir


On 21/09/2012 04:23, "Bruce Granger" <vivagin@yeah.net> wrote:

> Hi everyone! This is probably a familiar problem, but I haven't found anything
> in the archives or from google yet. I also talked with my parterners but we
> haven't got a sure conclusion. Recently I¹m caring about a question about
> shutdown operation:  When we shutdown a GuestOS by giving the command in its
> terminal, how can hypervisor get to know that this GuestOS is about to
> shutdown and How can hypervisor know that GuestOS has already done the work of
> shutdown?   In other word, is there any signal or something else that GuestOS
> deliver to hypervisor to notice that it will shutdown or it has accomplished
> its shutdown work?  Does anyone know the detailed process? Thanks for your
> help! 
> 
> View this message in context: How could Xen know a certain GuestOS have
> already shutdown?
> <http://xen.1045712.n5.nabble.com/How-could-Xen-know-a-certain-GuestOS-have-al
> ready-shutdown-tp5711421.html> Sent from the Xen - Dev mailing list archive
> <http://xen.1045712.n5.nabble.com/Xen-Dev-f2473738.html>  at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 2471 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-09-21  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  3:23 How could Xen know a certain GuestOS have already shutdown? Bruce Granger
2012-09-21  8:06 ` Keir Fraser [this message]
2012-09-24 13:12 ` Bruce Granger
  -- strict thread matches above, loose matches on Subject: below --
2012-09-24 17:09 Bruce Granger
2012-09-25  8:22 ` 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=CC81DE79.3F4C6%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=vivagin@yeah.net \
    --cc=xen-devel@lists.xensource.com \
    /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).