xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 5 of 9] libxl: add libxl_domain_preserve
Date: Mon, 26 Jul 2010 16:56:56 +0100	[thread overview]
Message-ID: <1280159816.13417.279.camel@localhost.localdomain> (raw)
In-Reply-To: <19533.43564.160252.987947@mariner.uk.xensource.com>

On Mon, 2010-07-26 at 16:30 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[Xen-devel] [PATCH 5 of 9] libxl: add libxl_domain_preserve"):
> > This method is intended to preserve an existing domain (for debugging
> > purposes) in such a way that the domain can also be restarted.
> 
> This sounds interesting, but I'm not quite sure what the semantics are
> intended to be.  I guess it works on an existing running domain or a
> paused one.  Does it stop the domain's execution ?

It was intended to be used to implement the rename-restart action for
the on_reboot (and on_crash I guess) actions which I introduce in a
later patch.

I only added this option because xend has it -- I'd be just as happy to
only implement simple restart until someone who wants the behaviour
comes along. In the meantime preserve or coredump-restart are pretty
good substitutes for rename-restart. 

Anyhow the actual actual semantics of libxl_domain_preserve is that it
acts on a shutdown (but not destroyed) domain. The name and/or comments
could certainly better reflect this.

> The current code seems mainly to change the name and the uuid in
> xenstore - to a specified new uuid - which seems a strange thing to
> do.

It's (a subset of) what xend does ;-) (For reference its
XendDomainInfo._preserveForRestart from
tools/python/xen/xend/XendDomainInfo.py)

I suspect the reason is something to do with not nuking /vm/<uuid> for a
running domain when destroying a previously preserved instance of that
domain.

Ian.

  reply	other threads:[~2010-07-26 15:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 10:56 [PATCH 0 of 9] xl: handle domain shutdown/reboot/crash in a user configurable way Ian Campbell
2010-07-26 10:56 ` [PATCH 1 of 9] libxl: Add LIBXL_EVENT namespace to enum libxl_event_type Ian Campbell
2010-07-26 10:56 ` [PATCH 2 of 9] libxl: return libxl_dominfo from libxl_event_get_domain_death_info Ian Campbell
2010-07-26 14:32   ` Stefano Stabellini
2010-07-26 14:38     ` Ian Campbell
2010-07-26 14:59       ` Stefano Stabellini
2010-07-26 15:26   ` Ian Jackson
2010-07-26 15:31     ` Ian Campbell
2010-07-26 15:36       ` Ian Jackson
2010-07-26 15:34     ` Stefano Stabellini
2010-07-26 15:41       ` Ian Jackson
2010-07-26 16:23         ` Stefano Stabellini
2010-07-26 16:38           ` Ian Jackson
2010-07-27  9:22             ` Ian Campbell
2010-07-27  9:53             ` Stefano Stabellini
2010-07-26 10:56 ` [PATCH 3 of 9] libxl: signal caller if domain already destroyed on domain death event Ian Campbell
2010-07-26 14:32   ` Stefano Stabellini
2010-07-26 14:41     ` Ian Campbell
2010-07-26 14:58       ` Stefano Stabellini
2010-07-26 15:02         ` Ian Campbell
2010-07-26 15:08           ` Stefano Stabellini
2010-07-26 10:56 ` [PATCH 4 of 9] libxl: should consider shutdown_reason for dying as well as shutdown domains Ian Campbell
2010-07-26 10:56 ` [PATCH 5 of 9] libxl: add libxl_domain_preserve Ian Campbell
2010-07-26 15:30   ` Ian Jackson
2010-07-26 15:56     ` Ian Campbell [this message]
2010-07-26 10:56 ` [PATCH 6 of 9] xl: do not try and auto re-connect console on reboot Ian Campbell
2010-07-26 10:56 ` [PATCH 7 of 9] xl: Add function to generate random uuid and use it Ian Campbell
2010-07-26 10:56 ` [PATCH 8 of 9] xl: Factor out domain death handling into a separate function Ian Campbell
2010-07-26 10:56 ` [PATCH 9 of 9] xl: support on_{poweroff, reboot, crash} domain configuration options 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=1280159816.13417.279.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --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).