It is configurable at the libvirt level, but you have to be careful about
the way in which you do it. The UUID is what identifies the guest from
libvirt POV, so if you change it you have effectively removed the old
guest and created a new guest. It is also exposed the guest OS, so it
could thing it was moved to new hardware which can in turn trigger
Windows license key request. I can understand why virt-manager does
not make it configurable, as there's rarely a strong reason to want to
change it to a particular value.
Daniel,
I dont disagree with you. In my case, I have a registered version of windows (raw disk image file) in which I know what its registered UUID should be. After importing it to virtual-machine-manager, windows forces the guest VM to re-register, which is exactly not what I wanted.
FYI, I am also using Proxmox, and proxmox's web-UI allows users to change the UUID. People should not touch it if they do not know what they are doing. It would be nice to be able to change it from the management tool UI.
FYI, I am also using Proxmox, and proxmox's web-UI allows users to change the UUID. People should not touch it if they do not know what they are doing. It would be nice to be able to change it from the management tool UI.
TP
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
