From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christian Limpach <christian.limpach@gmail.com>
Subject: Re: [PATCH] Prevent xend from starting duplicate domains
Date: Fri, 16 Sep 2005 20:40:45 +0100
Message-ID: <3d8eece205091612407ddf69a9@mail.gmail.com>
References: <87d5ncsksl.fsf@us.ibm.com>
Reply-To: Christian.Limpach@cl.cam.ac.uk
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_Part_5983_16676030.1126899645938"
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <87d5ncsksl.fsf@us.ibm.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Dan Smith <danms@us.ibm.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

------=_Part_5983_16676030.1126899645938
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 9/13/05, Dan Smith <danms@us.ibm.com> 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.
>=20
> This fixes the problem of getting the following error message from xm
> while creating a domain soon after destroying one with the same name:
>=20
>  xen.xend.XendProtocol.XendError: (3, 'No such process')

There is already a check for domains with the same name in
XendDomainInfo.check_name.  We should fix that check instead of adding
another check.  Could you try the attached patch which removes the
check if a domain "is terminated" and thus allows creation of a domain
with the same name?

It's arguable if this should be allowed or not, but if we allow it,
then we need to find the root cause of the error you're seeing...

    christian

------=_Part_5983_16676030.1126899645938
Content-Type: application/octet-stream; name="fix-name-check.patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="fix-name-check.patch"

ZGlmZiAtciA0NDkwZTM5ZmMzMjIgdG9vbHMvcHl0aG9uL3hlbi94ZW5kL1hlbmREb21haW5JbmZv
LnB5Ci0tLSBhL3Rvb2xzL3B5dGhvbi94ZW4veGVuZC9YZW5kRG9tYWluSW5mby5weQlGcmkgU2Vw
IDE2IDE5OjExOjM5IDIwMDUKKysrIGIvdG9vbHMvcHl0aG9uL3hlbi94ZW5kL1hlbmREb21haW5J
bmZvLnB5CUZyaSBTZXAgMTYgMjA6NDA6MjMgMjAwNQpAQCAtNjM1LDggKzYzNSw2IEBACiAgICAg
ICAgICMgbXkgZG9tYWluIGlkLgogICAgICAgICBpZiBub3QgZG9taW5mbzoKICAgICAgICAgICAg
IHJldHVybgotICAgICAgICBpZiBkb21pbmZvLmlzX3Rlcm1pbmF0ZWQoKToKLSAgICAgICAgICAg
IHJldHVybgogICAgICAgICBpZiBub3Qgc2VsZi5kb21pZCBvciAoZG9taW5mby5kb21pZCAhPSBz
ZWxmLmRvbWlkKToKICAgICAgICAgICAgIHJhaXNlIFZtRXJyb3IoJ3ZtIG5hbWUgY2xhc2g6ICcg
KyBuYW1lKQogICAgICAgICAK
------=_Part_5983_16676030.1126899645938
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

------=_Part_5983_16676030.1126899645938--