[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH][XEND]Fix checkname so that it detects duplicate domains.


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Thu, 24 May 2007 11:57:20 +0200
  • Delivery-date: Thu, 24 May 2007 02:56:02 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aced6etScrTUhsnqQ+CeH6LEai4TSA==
  • Thread-topic: [PATCH][XEND]Fix checkname so that it detects duplicate domains.

When using "xm restore" or "xm create" it's possible to create multiple
instances of the same domain. 

With this patch, it is not allowed to have multiple instances with the
same name. This should still work for live migration to localhost, as
the migration-path changes the name of the original domain-name, so the
original domain will not name-clash with the migration-target-domain. 

The previous behaviour was to check that the UUID is different, but for
domains that either have UUID in the config file, or that are the result
of restore, the UUID is definitely going to be the same for multiple
instances, so I believe this isn't a correct behaviour in the first
place. 

There is still a bit of a problem that "xm restore" doesn't report the
error correctly - it does say "Restore failed", but not explicitly that
it was caused by using an already existing name.

Signed off by: Mats Petersson (mats.petersson@xxxxxxx)

--
Mats

Attachment: patch.fix_checkname
Description: patch.fix_checkname

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.