Folks,
I would like to make sure that the VMs that use linked clones inside my desktop pool, will not update their UUID every time the linked clone is updated.
Although i used the "uuid.action=keep" parameter, i have noticed a strange behavior. The UUID of the VMs will change if create a new clone, but if i update (recompose) to a snapshot that was already user in past, the UUID of the members of the desktop pool will not change.
Does it make sense? How to avoid the UUID change inside the desktop pool when I perform a recompose action to a new snapshot?
p.s. if we are talking about linked clones already, i have noticed that even if i chose not to have a separate user data disk, D: drive with 2GB is always created - is there a way to overcome it as well?
Thank you and happy new year 2010!