We need the UUID to be consistent for all guests running on a particular host for the reasons that Daniel mentions, which the proposed patch would break. I also have concerns about using some format other than an actual UUID, which would be a problem if we just used a hash of the real UUID.
This could be addressed as an OSSN recommending that one generate their own UUID and configure it in /etc/libvirt/libvirtd.conf. I do agree that deployment tools should be responsible for setting these UUIDs instead of putting the burden on the deployer themselves.
We need the UUID to be consistent for all guests running on a particular host for the reasons that Daniel mentions, which the proposed patch would break. I also have concerns about using some format other than an actual UUID, which would be a problem if we just used a hash of the real UUID.
This could be addressed as an OSSN recommending that one generate their own UUID and configure it in /etc/libvirt/ libvirtd. conf. I do agree that deployment tools should be responsible for setting these UUIDs instead of putting the burden on the deployer themselves.