Dan Smith wrote:
KR> Adding randomness to the name is a good one. Someone could create KR> a guest with the name TEMPORARY, but if you through some KR> randomness in for good measure, it's unlikely that the InstanceID KR> will collide with the name of a guest.
In that case, their InstanceID would be "Xen:TEMPORARY" or similar, so
Oops - yes, I forgot we prefix the guest name with the virt type.
I don't think that's a problem anyway. However, if a client depends on the VSSD's InstanceID being unique for hashing or something else, then two template VSSDs with the same InstanceID could cause a problem.
True. I can't think of an example where this would be needed, but it's best to avoid a collision if possible. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com