[ovirt-users] disk not bootable

[Fernando Fuentes]

Team,

Any more ideas? :(

-- 
Fernando Fuentes
ffuentes at txweather.org
http://www.txweather.org

On Fri, Jul 8, 2016, at 09:36 AM, Melissa Mesler wrote:
> Michal, given what you said, then it has to be template related. We were
> able to create a new vm from scratch and move from the nfs domain to the
> iscsi domain. So where do we go from here?
> 
> On Fri, Jul 8, 2016, at 04:24 AM, Michal Skrivanek wrote:
> > 
> > > On 04 Jul 2016, at 17:43, Francesco Romani <fromani at redhat.com> wrote:
> > > 
> > > ----- Original Message -----
> > >> From: "Nir Soffer" <nsoffer at redhat.com>
> > >> To: "Fernando Fuentes" <ffuentes at darktcp.net>
> > >> Cc: "Francesco Romani" <fromani at redhat.com>, "users" <users at 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 at 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?
> > 
> > Nope, only specific licensing software seem to be checking this
> > 
> > >> 
> > >> 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.
> > 
> > depends on which host the VM is started. It’s the host-derived ID so it’s
> > often different every time you run a VM.
> > So I suppose here it just means the VM was launched on a different host.
> > It shouldn’t be significant to the boot issue.
> > 
> > > 
> > > 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
> > > _______________________________________________
> > > Users mailing list
> > > Users at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > 
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users