From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Prevent xend from starting duplicate domains
Date: Wed, 14 Sep 2005 00:20:55 +0100 [thread overview]
Message-ID: <43275ED7.2090709@blueyonder.co.uk> (raw)
In-Reply-To: <87d5ncsksl.fsf@us.ibm.com>
Dan Smith wrote:
> The attached patch puts a simple check in domain_create() which
> prevents starting a domain if there is already one of the same name in
> the domain list.
>
> This fixes the problem of getting the following error message from xm
> while creating a domain soon after destroying one with the same name:
>
> xen.xend.XendProtocol.XendError: (3, 'No such process')
>
> Signed-off-by: Dan Smith <danms@us.ibm.com>
Surely there's a race condition here? The hypervisor op that creates a domain
has to fail if it would result in two domains with the same name; this can't
be reliably enforced by a separate check in the Python tools.
--
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
next prev parent reply other threads:[~2005-09-13 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 21:46 [PATCH] Prevent xend from starting duplicate domains Dan Smith
2005-09-13 23:20 ` David Hopwood [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-09-14 12:04 Ian Pratt
2005-09-14 13:36 ` Dan Smith
2005-09-14 17:15 ` Christian Limpach
2005-09-14 20:50 Ian Pratt
2005-09-14 21:03 ` Dan Smith
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=43275ED7.2090709@blueyonder.co.uk \
--to=david.nospam.hopwood@blueyonder.co.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.