From: Christian Limpach <christian.limpach@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Xen Tools Developers <xen-tools@lists.xensource.com>,
Dan Smith <danms@us.ibm.com>,
Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: [Xen-tools] Re: [PATCH] Make xend reject duplicates and rename zombies
Date: Fri, 16 Sep 2005 22:48:06 +0100 [thread overview]
Message-ID: <3d8eece2050916144823f8c859@mail.gmail.com> (raw)
In-Reply-To: <432B3B13.4070705@us.ibm.com>
On 9/16/05, Anthony Liguori <aliguori@us.ibm.com> wrote:
> >I think renaming would make sense if a domain is crashed. You might
> >want to keep the domain around to attach a debugger to it but at the
> >same time restart a fresh copy as soon as possible.
>
> As long as you can make sure to rename *after* all of the devices have
> been properly torn down.
>
> Otherwise, we need to make sure to make it well known that restarting a
> domain after a crash can result in very bad things :-)
How so? The crashed domain is certainly not going to do anything with
those devices anymore... Actually, I'm not even sure I buy the
"unsafe to reuse devices" argument if the domain is only hanging
around in an almost dead state -- it's almost dead, it's not going to
do any requests on those devices anymore...
So regarding the check for termination in check_name, if we only
switch the state to terminated once the domain is almost dead, reusing
the name should be fine...
christian
next prev parent reply other threads:[~2005-09-16 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 15:49 [PATCH] Make xend reject duplicates and rename zombies Dan Smith
2005-09-15 18:54 ` Anthony Liguori
2005-09-15 19:16 ` Dan Smith
2005-09-16 14:45 ` Ted Kaczmarek
2005-09-16 19:52 ` [Xen-tools] " Christian Limpach
2005-09-16 21:37 ` Anthony Liguori
2005-09-16 21:48 ` Christian Limpach [this message]
2005-09-16 21:49 ` Anthony Liguori
2005-09-16 22:19 ` Christian Limpach
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=3d8eece2050916144823f8c859@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=aliguori@us.ibm.com \
--cc=danms@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-tools@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 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.