libvirtd doesn't allow mismatching between <uuid> and <sysinfo> sections of xml vm definition.
this prevents me from having a clone of a windows os that needs the exact uuid in <sysinfo> in order to activation to keep working.
this restricts me from running two clones at the same time and even having the clone defined and not running, so I have to go back and forth with defining and undefining the original and the clone, which is time consuming and frustrating.
I fail to understand why upstream has decided in BZ 890494 that this must be the same uuid, since <uuid> section is about how libvirtd identifies the vm while the <sysinfo> is something that only the guest needs!
I wish Ubuntu can revert this decision and allow different uuids in <os> and <sysinfo> sections.
libvirtd doesn't allow mismatching between <uuid> and <sysinfo> sections of xml vm definition.
this prevents me from having a clone of a windows os that needs the exact uuid in <sysinfo> in order to activation to keep working.
this restricts me from running two clones at the same time and even having the clone defined and not running, so I have to go back and forth with defining and undefining the original and the clone, which is time consuming and frustrating.
I fail to understand why upstream has decided in BZ 890494 that this must be the same uuid, since <uuid> section is about how libvirtd identifies the vm while the <sysinfo> is something that only the guest needs!
I wish Ubuntu can revert this decision and allow different uuids in <os> and <sysinfo> sections.
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=890494
thanks