All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <christian.limpach@gmail.com>
To: Dan Smith <danms@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] Prevent xend from starting duplicate domains
Date: Wed, 14 Sep 2005 18:15:58 +0100	[thread overview]
Message-ID: <3d8eece2050914101511890182@mail.gmail.com> (raw)
In-Reply-To: <87u0gnrcu4.fsf@us.ibm.com>

On 9/14/05, Dan Smith <danms@us.ibm.com> wrote:
> IP> That way, even if something has gone wrong and we're left with a
> IP> shell domain we'll still be able to restart one with the same
> IP> name. (obviously we should only do the rename once)
> 
> In xm-test, this problem starts showing up towards the end of the test
> run, and increases in frequency.  My guess is that if we were to do
> the rename once, it would occasionally allow another domain to be
> created, but under high load, would not help that much.

How about we rename the domain to its uuid[1][2] and don't display
those in xm list unless a verbose option is given?

    christian

[1] <name>-zombie-<domid> could work as well...
[2] or clear the name and change list to supply the uuid if there's no name...

  reply	other threads:[~2005-09-14 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 12:04 [PATCH] Prevent xend from starting duplicate domains Ian Pratt
2005-09-14 13:36 ` Dan Smith
2005-09-14 17:15   ` Christian Limpach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 20:50 Ian Pratt
2005-09-14 21:03 ` Dan Smith
2005-09-13 21:46 Dan Smith
2005-09-13 23:20 ` David Hopwood
2005-09-14  0:06   ` Dan Smith
2005-09-14  4:32     ` Anthony Liguori
2005-09-16 19:40 ` Christian Limpach
2005-09-16 22:49   ` Dan Smith
2005-09-16 23:47     ` 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=3d8eece2050914101511890182@mail.gmail.com \
    --to=christian.limpach@gmail.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=danms@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.