From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jim Fehlig <jfehlig@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PATCH: Fix name uniqueness check
Date: Thu, 27 Sep 2007 18:39:15 +0100 [thread overview]
Message-ID: <20070927173915.GM17433@redhat.com> (raw)
In-Reply-To: <46FBE56B.4040708@novell.com>
On Thu, Sep 27, 2007 at 11:16:27AM -0600, Jim Fehlig wrote:
> Daniel P. Berrange wrote:
> > Changeset 15124:f5459c358575 altered check_name() in XendDomainInfo so that
> > it compares domain IDs instead of UUIDs. This breaks a number of things
> >
> > - You can no longer use 'xm new' to define a persistent config file for
> > a running guest. This breaks the key OS provisioning scenario where
> > you boot a kenrel+initrd for the installer, and at the same time define
> > a permanent config with pygrub.
> >
> > - It lets you define multiple inactive guests with different UUIDs, but
> > the same name because all inactive guests have a domid of None. So you
> > can now end up with multiple guests with same name, which is contrary
> > to the goal implied by the patch which was name uniqueness.
> >
> > It is unclear from the original commit logs just what scenario it was trying
> > to protect against, but the original checking of uniqueness based on UUID
> > was correct & is what was used in previous releases XenD.
> >
>
> Yes, I was not sure what this patch was attempting to fix either. There
> was some discussion about the patch in this thread
>
> http://lists.xensource.com/archives/html/xen-devel/2007-05/msg00887.html
Ok, so if I follow that correctly, the crux of the issue is that it was
possible to start 2 unmanaged domains with same name and same uuid. So
I think we can probably address that by checking for UUID, and the only
if both are running, also check for domid match. So really a combo of
both the original & current code.
> At any rate, the patch was giving me some problems with reboot so I
> added to the misery with this
>
> http://xenbits2.xensource.com/xen-unstable.hg?rev/9f4f70233041
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-09-27 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 16:50 PATCH: Fix name uniqueness check Daniel P. Berrange
2007-09-27 17:16 ` Jim Fehlig
2007-09-27 17:39 ` Daniel P. Berrange [this message]
2007-09-27 19:42 ` Jim Fehlig
2007-09-27 20:40 ` Daniel P. Berrange
2007-10-01 5:36 ` Keir Fraser
2007-10-01 13:57 ` Daniel P. Berrange
2007-10-01 18:18 ` Daniel P. Berrange
2007-10-01 22:12 ` Daniel P. Berrange
2007-10-02 13:11 ` Masaki Kanno
2007-10-02 14:47 ` Daniel P. Berrange
2007-10-05 5:19 ` Masaki Kanno
2007-10-05 13:35 ` Daniel P. Berrange
2007-10-05 14:26 ` Masaki Kanno
2007-09-28 3:59 ` Masaki Kanno
2007-09-28 4:56 ` Masaki Kanno
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=20070927173915.GM17433@redhat.com \
--to=berrange@redhat.com \
--cc=jfehlig@novell.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.