Re: [ovirt-users] disk not bootable
----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: "Fernando Fuentes" <ffuentes(a)darktcp.net>
Cc: "Francesco Romani" <fromani(a)redhat.com>, "users"
<users(a)ovirt.org>
Sent: Saturday, July 2, 2016 11:18:01 AM
Subject: Re: [ovirt-users] disk not bootable
On Sat, Jul 2, 2016 at 1:33 AM, Fernando Fuentes <ffuentes(a)darktcp.net>
wrote:
> Nir,
>
> Ok I ran another test and this one I moved from NFS domain to iSCSI and
> stop working than I moved it back and still unable to run... Windows VM
> is saying "no available boot disk"
> VM: Win7-Test
> Host: Zeta
> Info as requested: http://pastebin.com/1fSi3auz
We need a working xml to compare to.
[snip expected changes]
<entry name="manufacturer">oVirt</entry>
<entry name="product">oVirt Node</entry>
<entry name="version">6-5.el6.centos.11.2</entry>
- <entry
name="serial">C938F077-55E2-3E50-A694-9FCB7661FD89</entry>
+ <entry
name="serial">735C7A01-1F16-3CF0-AF8C-A99823E95AC0</entry>
Not expected - maybe this is confusing windows?
Francesco, why vm serial has changed after moving disks from one storage
domain
to another?
We put in serial either
1. the UUID Engine send to us
2. the host UUID as returned by our getHostUUID utility function
the latter is unlikely to change, even after this disk move.
So the first suspect in line is Engine
Arik, do you know if Engine is indeed supposed to change the UUID in this flow?
That seems very surprising.
Thanks and bests,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani