11:54 p.m.
--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--
2:45 a.m.
On 30 Dec 2017, at 06:54, Blaster <blaster(a)556nato.com> wrote:
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?
The guest UUID is configurable per VM in Edit dialog, you can use a custom
value
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:23 a.m.
On Sat, Dec 30, 2017 at 10:45 AM, Michal Skrivanek <
michal.skrivanek(a)redhat.com> wrote:
On 30 Dec 2017, at 06:54, Blaster <blaster(a)556nato.com> wrote:
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?
I think it's the field 'vm_guid' in the table 'vm_static'.
You can restore the backup on a temp vm somewhere - make sure it has no
access to your hosts so that the engine will not start to manage them -
or just look at the db dump. The backup is a tar file, and you can look
at db dumps inside it using 'pg_restore filename | less'.
The guest UUID is configurable per VM in Edit dialog, you can use a custom
value
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Didi
3:38 p.m.
This is a multi-part message in MIME format.
--------------81FD021695565412FC291787
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
On 12/31/2017 1:23 AM, Yedidyah Bar David wrote:
On Sat, Dec 30, 2017 at 10:45 AM, Michal Skrivanek
<michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> wrote:
On 30 Dec 2017, at 06:54, Blaster <blaster(a)556nato.com
<mailto:blaster@556nato.com>> wrote:
> 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?
>
I think it's the field 'vm_guid' in the table 'vm_static'.
You can restore the backup on a temp vm somewhere - make sure it has no
access to your hosts so that the engine will not start to manage them -
or just look at the db dump. The backup is a tar file, and you can look
at db dumps inside it using 'pg_restore filename | less'.
The guest UUID is configurable per VM in Edit dialog, you can use
a custom value
Thank you, I was able to get the UUID back!
--------------81FD021695565412FC291787
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 12/31/2017 1:23 AM, Yedidyah Bar
David wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHRwYXs0ocrMZviOcU80_UfuVWS=cqKKYrxekqCfPUJ_6VvZHg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Sat, Dec 30, 2017 at 10:45 AM,
Michal Skrivanek <span dir="ltr"><<a
href="mailto:michal.skrivanek@redhat.com"
target="_blank"
moz-do-not-send="true">michal.skrivanek(a)redhat.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div>
<div class="gmail-h5">
<div><br>
</div>
<div><br>
On 30 Dec 2017, at 06:54, Blaster <<a
href="mailto:blaster@556nato.com"
target="_blank"
moz-do-not-send="true">blaster(a)556nato.com</a>&gt;
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div bgcolor="#FFFFFF">
<p>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>I have an engine config backup and a backup
of the oVirt storage domain.</p>
<p>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>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I think it's the field 'vm_guid' in the table
'vm_static'.<br>
<br>
</div>
<div>You can restore the backup on a temp vm somewhere -
make sure it has no<br>
</div>
<div>access to your hosts so that the engine will not start
to manage them -<br>
</div>
<div>or just look at the db dump. The backup is a tar file,
and you can look<br>
</div>
<div>at db dumps inside it using 'pg_restore filename |
less'.<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div>
<div class="gmail-h5">
<div><br>
</div>
</div>
</div>
The guest UUID is configurable per VM in Edit dialog,
you can use a custom value</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
Thank you, I was able to get the UUID back!<br>
<p><br>
</p>
</body>
</html>
--------------81FD021695565412FC291787--
2518
days inactive
2522
days old
3 comments
4 participants
participants (4)
-
Blaster -
Blaster
-
Michal Skrivanek -
Yedidyah Bar David