https://bugzilla.novell.com/show_bug.cgi?id=392629
User wolfgang@rosenauer.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=392629#c1
--- Comment #1 from Wolfgang Rosenauer 2008-05-20 08:32:58 MST ---
Just found that this got reverted upstream already because of its brokenness:
changeset: 15451:a86cf1d18625
user: Keir Fraser
date: Tue Oct 02 10:04:06 2007 +0100
files: tools/python/xen/xend/XendDomainInfo.py
description:
xend: Fix name/uuid uniqueness checks.
Signed-off-by: Daniel P. Berrange
xen-unstable changeset: 15998:a345f989722649ba01701babf60e49517e910102
xen-unstable date: Tue Oct 02 10:01:10 2007 +0100
changeset: 15450:d92bb1cd352c
user: Keir Fraser
date: Tue Oct 02 10:03:28 2007 +0100
files: tools/python/xen/xend/XendDomainInfo.py
description:
xend: Fix name uniqueness check (revert xen-unstable 15168:a717cb2fac90).
Changeset 15168:a717cb2fac90 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.
Signed-off-by: Daniel P. Berrange
xen-unstable changeset: 15973:8817a53c030f9c2c5f39fafad72aa9502342e7b3
xen-unstable date: Thu Sep 27 18:08:11 2007 +0100
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
