All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Dan Smith <danms@us.ibm.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
Subject: Re: [PATCH] Prevent xend from starting duplicate domains
Date: Tue, 13 Sep 2005 23:32:35 -0500	[thread overview]
Message-ID: <4327A7E3.1090602@us.ibm.com> (raw)
In-Reply-To: <878xy0sebq.fsf@us.ibm.com>

Dan Smith wrote:

>DH> Surely there's a race condition here? The hypervisor op that
>DH> creates a domain has to fail if it would result in two domains
>DH> with the same name; 
>
>With the same domid?  Yes.  Unless I'm completely missing something,
>the hypervisor knows nothing of the *names* of the domains.
>  
>
The hypervisor has no concept of domain names.  That's entirely a Xend 
construct.  The same applies to UUIDs.

Even if there are two domains with the same name, they have different 
domain IDs which is okay from the hypervisor's perspective.

>Am I wrong?
>
>DH> this can't be reliably enforced by a separate check in the Python
>DH> tools.
>
>Going on the assumption that the names are known only to the tools, I
>think the tools are the best place to perform the check.
>
>  
>
Regards,

Anthony Liguori

  reply	other threads:[~2005-09-14  4:32 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
2005-09-14  0:06   ` Dan Smith
2005-09-14  4:32     ` Anthony Liguori [this message]
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=4327A7E3.1090602@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=danms@us.ibm.com \
    --cc=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.