From: Ewan Mellor <ewan@xensource.com>
To: xen-devel@lists.xensource.com
Subject: Re: Re: Rename all dying domains to be prefixed with Zombie. This allows a new domain
Date: Thu, 6 Oct 2005 14:57:48 +0100 [thread overview]
Message-ID: <20051006135747.GB21233@uk.xensource.com> (raw)
In-Reply-To: <20051006134723.GC19844@underhill.no-ip.org>
On Thu, Oct 06, 2005 at 09:47:23AM -0400, Sean Dague wrote:
> So what happens if:
>
> * Dom1 is told to die
> * It doesn't because it can't free a physical resource (i.e. disk)
> * It gets renamed to Zombie-Dom1
> * User tries to recreate Dom1
> * New Dom1 grabs physical resource that was keeping Dom1 from dying
>
> Doesn't that provide for the possibility of 2 writers to a device that only
> can support 1, and all heck breaking loose? (Note, I hope I'm wrong here)
If a domain has been destroyed, even if it's a zombie in the dying state, it
will never execute another instruction. Xen may be unable to clean up after
it, but you are guaranteed that it won't write to the filesystem any longer.
Ewan.
next prev parent reply other threads:[~2005-10-06 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1ENSnM-0002c4-RB@xenbits.xensource.com>
2005-10-06 13:47 ` Rename all dying domains to be prefixed with Zombie. This allows a new domain Sean Dague
2005-10-06 13:57 ` Ewan Mellor [this message]
2005-10-06 15:14 ` Anthony Liguori
2005-10-06 17:37 ` harry
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=20051006135747.GB21233@uk.xensource.com \
--to=ewan@xensource.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 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.