--Apple-Mail=_E9FF7EA0-826C-45A7-AB9C-F7262CD9645B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I need to create an old oVirt Windows VM. The VM has an old licensed = product that we can no longer get a licensed reissued for. It looks = like I need to feed back the original qemu UUID that was used when the = VM was created. I have an engine config backup and a backup of the oVirt storage domain. I viewed the engine backup, but the format as-is doesn't give any = obvious configuration details of the VMs at the time of the backup. Is = the UUID as obvious as the file name of the VM's boot volume UUID name? --Apple-Mail=_E9FF7EA0-826C-45A7-AB9C-F7262CD9645B Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""> <meta http-equiv="content-type" content="text/html; charset=utf-8" class=""> <div text="#000000" bgcolor="#FFFFFF" class=""><p class="">I need to create an old oVirt Windows VM. The VM has an old licensed product that we can no longer get a licensed reissued for. It looks like I need to feed back the original qemu UUID that was used when the VM was created.</p><p class="">I have an engine config backup and a backup of the oVirt storage domain.</p><p class="">I viewed the engine backup, but the format as-is doesn't give any obvious configuration details of the VMs at the time of the backup. Is the UUID as obvious as the file name of the VM's boot volume UUID name?</p><p class=""><br class=""> </p> </div> </body></html> --Apple-Mail=_E9FF7EA0-826C-45A7-AB9C-F7262CD9645B--