Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

>>> >> >> Fernando Fuentes
> > > >>> >> >> ffuen...@txweather.org
> > > >>> >> >> http://www.txweather.org
> > > >>> >> >>
> > > >>> >> >> On Sat, Jul 16, 2016, at 04:16 PM, Nir Soffer wrote:
> > > >>> >> >> > On Fri, Jul 15, 2016 at 3:50 PM, Fernando Fuentes
> > > >>> >> >> > <ffuen...@darktcp.net>
> > > >>> >> >> > wrote:
> > > >>> >> >> > > Nir,
> > > >>> >> >> > >
> > > >>> >> >> > > I try to follow your steps but I cant seem to find the ID of
> > > >>> >> >> > > the
> > > >>> >> >> > > template.
> > > >>> >> >> >
> > > >>> >> >> > The image-uuid of the template is displayed in the Disks tab 
> > > >>> >> >> > in
> > > >>> >> >> > engine.
> > > >>> >> >> >
> > > >>> >> >> > To find the volume-uuid on block storage, you can do:
> > > >>> >> >> >
> > > >>> >> >> > pvscan --cache
> > > >>> >> >> > lvs -o vg_name,lv_name,tags | grep image-uuid
> > > >>> >> >> >
> > > >>> >> >> > >
> > > >>> >> >> > > Regards,
> > > >>> >> >> > >
> > > >>> >> >> > > --
> > > >>> >> >> > > Fernando Fuentes
> > > >>> >> >> > > ffuen...@txweather.org
> > > >>> >> >> > > http://www.txweather.org
> > > >>> >> >> > >
> > > >>> >> >> > > On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> > > >>> >> >> > >> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler
> > > >>> >> >> > >> <meli...@justmelly.com>
> > > >>> >> >> > >> wrote:
> > > >>> >> >> > >> > All, I did a test for Fernando in our ovirt environment. 
> > > >>> >> >> > >> > I
> > > >>> >> >> > >> > created a vm
> > > >>> >> >> > >> > called win7melly in the nfs domain. I then migrated it to
> > > >>> >> >> > >> > the iscsi
> > > >>> >> >> > >> > domain. It booted without any issue. So it has to be
> > > >>> >> >> > >> > something with the
> > > >>> >> >> > >> > templates. I have attached the vdsm log for the host the 
> > > >>> >> >> > >> > vm
> > > >>> >> >> > >> > resides on.
> > > >>> >> >> > >>
> > > >>> >> >> > >> The log show a working vm, so it does not help much.
> > > >>> >> >> > >>
> > > >>> >> >> > >> I think that the template you copied from the nfs domain to
> > > >>> >> >> > >> the block
> > > >>> >> >> > >> domain is
> > > >>> >> >> > >> corrupted, or the volume metadata are incorrect.
> > > >>> >> >> > >>
> > > >>> >> >> > >> If I understand this correctly, this started when Fernando
> > > >>> >> >> > >> could not copy
> > > >>> >> >> > >> the vm
> > > >>> >> >> > >> disk to the block storage, and I guess the issue was that 
> > > >>> >> >> > >> the
> > > >>> >> >> > >> template
> > > >>> >> >> > >> was missing
> > > >>> >> >> > >> on that storage domain. I assume that he copied the 
> > > >>> >> >> > >> template
> > > >>> >> >

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

;> > MB, 536870912 bytes
> > >>> >> > 255 heads, 63 sectors/track, 65 cylinders
> > >>> >> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > >>> >> > Sector size (logical/physical): 512 bytes / 32768 bytes
> > >>> >> > I/O size (minimum/optimal): 32768 bytes / 1048576 bytes
> > >>> >> > Disk identifier: 0x
> > >>> >> >
> > >>> >> > Disk /dev/mapper/4861322b--352f--41c6--890a--5cbf1c2c1f01-master:
> > >>> >> > 1073
> > >>> >> > MB, 1073741824 bytes
> > >>> >> > 255 heads, 63 sectors/track, 130 cylinders
> > >>> >> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > >>> >> > Sector size (logical/physical): 512 bytes / 32768 bytes
> > >>> >> > I/O size (minimum/optimal): 32768 bytes / 1048576 bytes
> > >>> >> > Disk identifier: 0x
> > >>> >> >
> > >>> >> > Regards,
> > >>> >> >
> > >>> >> > --
> > >>> >> > Fernando Fuentes
> > >>> >> > ffuen...@txweather.org
> > >>> >> > http://www.txweather.org
> > >>> >> >
> > >>> >> > On Sat, Jul 16, 2016, at 04:25 PM, Fernando Fuentes wrote:
> > >>> >> >> Nir,
> > >>> >> >>
> > >>> >> >> Ok ill look for it here in a few.
> > >>> >> >> Thanks for your reply and help!
> > >>> >> >>
> > >>> >> >> --
> > >>> >> >> Fernando Fuentes
> > >>> >> >> ffuen...@txweather.org
> > >>> >> >> http://www.txweather.org
> > >>> >> >>
> > >>> >> >> On Sat, Jul 16, 2016, at 04:16 PM, Nir Soffer wrote:
> > >>> >> >> > On Fri, Jul 15, 2016 at 3:50 PM, Fernando Fuentes
> > >>> >> >> > <ffuen...@darktcp.net>
> > >>> >> >> > wrote:
> > >>> >> >> > > Nir,
> > >>> >> >> > >
> > >>> >> >> > > I try to follow your steps but I cant seem to find the ID of
> > >>> >> >> > > the
> > >>> >> >> > > template.
> > >>> >> >> >
> > >>> >> >> > The image-uuid of the template is displayed in the Disks tab in
> > >>> >> >> > engine.
> > >>> >> >> >
> > >>> >> >> > To find the volume-uuid on block storage, you can do:
> > >>> >> >> >
> > >>> >> >> > pvscan --cache
> > >>> >> >> > lvs -o vg_name,lv_name,tags | grep image-uuid
> > >>> >> >> >
> > >>> >> >> > >
> > >>> >> >> > > Regards,
> > >>> >> >> > >
> > >>> >> >> > > --
> > >>> >> >> > > Fernando Fuentes
> > >>> >> >> > > ffuen...@txweather.org
> > >>> >> >> > > http://www.txweather.org
> > >>> >> >> > >
> > >>> >> >> > > On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> > >>> >> >> > >> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler
> > >>> >> >> > >> <meli...@justmelly.com>
> > >>> >> >> > >> wrote:
> > >>> >> >> > >> > All, I did a test for Fernando in our ovirt environment. I
> > >>> >> >> > >> > created a vm
> > >>> >> >> > >> > called win7melly in the nfs domain. I then migrated it to
> > >>> >> >> > >> > the iscsi
> > >>> >> >> > >> > domain. It booted without any issue. So it has to be
> > >>> >> >> > >> > something with the
> > >>> >> >> > >> > templates. I have attached the vdsm log for the host the vm
> > >>> >> >> > >> > resides on.
> &

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

;> >> >> > On Fri, Jul 15, 2016 at 3:50 PM, Fernando Fuentes
> >>> >> >> > <ffuen...@darktcp.net>
> >>> >> >> > wrote:
> >>> >> >> > > Nir,
> >>> >> >> > >
> >>> >> >> > > I try to follow your steps but I cant seem to find the ID of
> >>> >> >> > > the
> >>> >> >> > > template.
> >>> >> >> >
> >>> >> >> > The image-uuid of the template is displayed in the Disks tab in
> >>> >> >> > engine.
> >>> >> >> >
> >>> >> >> > To find the volume-uuid on block storage, you can do:
> >>> >> >> >
> >>> >> >> > pvscan --cache
> >>> >> >> > lvs -o vg_name,lv_name,tags | grep image-uuid
> >>> >> >> >
> >>> >> >> > >
> >>> >> >> > > Regards,
> >>> >> >> > >
> >>> >> >> > > --
> >>> >> >> > > Fernando Fuentes
> >>> >> >> > > ffuen...@txweather.org
> >>> >> >> > > http://www.txweather.org
> >>> >> >> > >
> >>> >> >> > > On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> >>> >> >> > >> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler
> >>> >> >> > >> <meli...@justmelly.com>
> >>> >> >> > >> wrote:
> >>> >> >> > >> > All, I did a test for Fernando in our ovirt environment. I
> >>> >> >> > >> > created a vm
> >>> >> >> > >> > called win7melly in the nfs domain. I then migrated it to
> >>> >> >> > >> > the iscsi
> >>> >> >> > >> > domain. It booted without any issue. So it has to be
> >>> >> >> > >> > something with the
> >>> >> >> > >> > templates. I have attached the vdsm log for the host the vm
> >>> >> >> > >> > resides on.
> >>> >> >> > >>
> >>> >> >> > >> The log show a working vm, so it does not help much.
> >>> >> >> > >>
> >>> >> >> > >> I think that the template you copied from the nfs domain to
> >>> >> >> > >> the block
> >>> >> >> > >> domain is
> >>> >> >> > >> corrupted, or the volume metadata are incorrect.
> >>> >> >> > >>
> >>> >> >> > >> If I understand this correctly, this started when Fernando
> >>> >> >> > >> could not copy
> >>> >> >> > >> the vm
> >>> >> >> > >> disk to the block storage, and I guess the issue was that the
> >>> >> >> > >> template
> >>> >> >> > >> was missing
> >>> >> >> > >> on that storage domain. I assume that he copied the template
> >>> >> >> > >> to the
> >>> >> >> > >> block storage
> >>> >> >> > >> domain by opening the templates tab, selecting the template,
> >>> >> >> > >> and choosing
> >>> >> >> > >> copy
> >>> >> >> > >> from the menu.
> >>> >> >> > >>
> >>> >> >> > >> Lets compare the template on both nfs and block storage
> >>> >> >> > >> domain.
> >>> >> >> > >>
> >>> >> >> > >> 1. Find the template on the nfs storage domain, using the
> >>> >> >> > >> image uuid in
> >>> >> >> > >> engine.
> >>> >> >> > >>
> >>> >> >> > >> It should be at
> >>> >> >> > >>
> >>> >> >> > >>
> >>> >> >> > >> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
> >&g

Re: [ovirt-users] disk not bootable

[Nir Soffer]

>>> >> >> > >> > called win7melly in the nfs domain. I then migrated it to
>>> >> >> > >> > the iscsi
>>> >> >> > >> > domain. It booted without any issue. So it has to be
>>> >> >> > >> > something with the
>>> >> >> > >> > templates. I have attached the vdsm log for the host the vm
>>> >> >> > >> > resides on.
>>> >> >> > >>
>>> >> >> > >> The log show a working vm, so it does not help much.
>>> >> >> > >>
>>> >> >> > >> I think that the template you copied from the nfs domain to
>>> >> >> > >> the block
>>> >> >> > >> domain is
>>> >> >> > >> corrupted, or the volume metadata are incorrect.
>>> >> >> > >>
>>> >> >> > >> If I understand this correctly, this started when Fernando
>>> >> >> > >> could not copy
>>> >> >> > >> the vm
>>> >> >> > >> disk to the block storage, and I guess the issue was that the
>>> >> >> > >> template
>>> >> >> > >> was missing
>>> >> >> > >> on that storage domain. I assume that he copied the template
>>> >> >> > >> to the
>>> >> >> > >> block storage
>>> >> >> > >> domain by opening the templates tab, selecting the template,
>>> >> >> > >> and choosing
>>> >> >> > >> copy
>>> >> >> > >> from the menu.
>>> >> >> > >>
>>> >> >> > >> Lets compare the template on both nfs and block storage
>>> >> >> > >> domain.
>>> >> >> > >>
>>> >> >> > >> 1. Find the template on the nfs storage domain, using the
>>> >> >> > >> image uuid in
>>> >> >> > >> engine.
>>> >> >> > >>
>>> >> >> > >> It should be at
>>> >> >> > >>
>>> >> >> > >>
>>> >> >> > >> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
>>> >> >> > >>
>>> >> >> > >> 2. Please share the output of:
>>> >> >> > >>
>>> >> >> > >> cat /path/to/volume.meta
>>> >> >> > >> qemu-img info /path/to/volume
>>> >> >> > >> qemu-img check /path/to/volume
>>> >> >> > >>
>>> >> >> > >> 4. Find the template on the block storage domain
>>> >> >> > >>
>>> >> >> > >> You should have an lv using the same volume uuid and the
>>> >> >> > >> image-uuid
>>> >> >> > >> should be in the lv tag.
>>> >> >> > >>
>>> >> >> > >> Find it using:
>>> >> >> > >>
>>> >> >> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
>>> >> >> > >>
>>> >> >> > >> 5. Activate the lv
>>> >> >> > >>
>>> >> >> > >> lvchange -ay vg_name/lv_name
>>> >> >> > >>
>>> >> >> > >> 6. Share the output of
>>> >> >> > >>
>>> >> >> > >> qemu-img info /dev/vg_name/lv_name
>>> >> >> > >> qemu-img check /dev/vg_name/lv_name
>>> >> >> > >>
>>> >> >> > >> 7. Deactivate the lv
>>> >> >> > >>
>>> >> >> > >> lvchange -an vg_name/lv_name
>>> >> >> > >>
>>> >> >> > >> 8. Find the lv metadata
>>> >> >> > >>
>>> >> >> > >> The metadata is stored in /dev/vg_name/metadata. To find the
>>> >> >> > >> correct
>>> >> >> > >> block,
>>> >> >> > >> find the tag named MD_N in the lv tags you found in step 4
>>> >> >> > >>
>>> >> >> > >> The block we need is located at offset N from start of volume.
>>> >> >> > >>
>>> >> >> > >> 9. Share the output of:
>>> >> >> > >>
>>> >> >> > >> dd if=/dev/vg_name/metadata bs=512 skip=N count=1
>>> >> >> > >> iflag=direct
>>> >> >> > >>
>>> >> >> > >> The output of this command should show the image-uuid.
>>> >> >> > >>
>>> >> >> > >> Nir
>>> >> >> > >>
>>> >> >> > >> >
>>> >> >> > >> > - MeLLy
>>> >> >> > >> >
>>> >> >> > >> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
>>> >> >> > >> >> Nir,
>>> >> >> > >> >>
>>> >> >> > >> >> That's exactly how I did it Nir.
>>> >> >> > >> >> I will test tomorrow with a new Windows VM and report back.
>>> >> >> > >> >>
>>> >> >> > >> >> Regards,
>>> >> >> > >> >>
>>> >> >> > >> >> --
>>> >> >> > >> >> Fernando Fuentes
>>> >> >> > >> >> ffuen...@txweather.org
>>> >> >> > >> >> http://www.txweather.org
>>> >> >> > >> >>
>>> >> >> > >> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
>>> >> >> > >> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani
>>> >> >> > >> >> > <from...@redhat.com>
>>> >> >> > >> >> > wrote:
>>> >> >> > >> >> > > - Original Message -
>>> >> >> > >> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
>>> >> >> > >> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
>>> >> >> > >> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users"
>>> >> >> > >> >> > >> <users@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
>>> >> >> > >> >> > >> <ffuen...@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]
>>> >> >> > >> >> > >
>>> >> >> > >> >> > >
>>> >> >> > >> >> > >>   oVirt
>>> >> >> > >> >> > >>   oVirt Node
>>> >> >> > >> >> > >>   6-5.el6.centos.11.2
>>> >> >> > >> >> > >> - >> >> >> > >> >> > >> name="serial">C938F077-55E2-3E50-A694-9FCB7661FD89
>>> >> >> > >> >> > >> + >> >> >> > >> >> > >> name="serial">735C7A01-1F16-3CF0-AF8C-A99823E95AC0
>>> >> >> > >> >> > >>
>>> >> >> > >> >> > >> 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.
>>> >> >> > >> >> >
>>> >> >> > >> >> > Fernando, can you describe exactly how you moved the
>>> >> >> > >> >> > disk?
>>> >> >> > >> >> >
>>> >> >> > >> >> > I assume that you selected the vm in the virtual machines
>>> >> >> > >> >> > tab, then
>>> >> >> > >> >> > selected
>>> >> >> > >> >> > disks from the sub tab, then selected move, and selected
>>> >> >> > >> >> > the target
>>> >> >> > >> >> > storage domain.
>>> >> >> > >> >> >
>>> >> >> > >> >> > Also, can you reproduce this with a new vm? (create vm
>>> >> >> > >> >> > with disk nfs,
>>> >> >> > >> >> > stop vm,
>>> >> >> > >> >> > move disk to iscsi, start vm).
>>> >> >> > >> >> >
>>> >> >> > >> >> > > 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@ovirt.org
>>> >> >> > >> >> http://lists.ovirt.org/mailman/listinfo/users
>>> >> >> > >> >
>>> >> >> > >> > ___
>>> >> >> > >> > Users mailing list
>>> >> >> > >> > Users@ovirt.org
>>> >> >> > >> > http://lists.ovirt.org/mailman/listinfo/users
>>> >> >> > >> >
>>> >> >> ___
>>> >> >> Users mailing list
>>> >> >> Users@ovirt.org
>>> >> >> http://lists.ovirt.org/mailman/listinfo/users
>>> >> > ___
>>> >> > Users mailing list
>>> >> > Users@ovirt.org
>>> >> > http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

gt;> >> >> > Disk identifier: 0x
>> >> >> >
>> >> >> >
>> >> >> > Disk /dev/mapper/3ccb7b67--8067--4315--9656--d68ba10975ba-
>> >> >> > metadata: 536
>> >> >> > MB, 536870912 bytes
>> >> >> > 255 heads, 63 sectors/track, 65 cylinders
>> >> >> > Units = cylinders of 16065 * 512 = 8225280 bytes
>> >> >> > Sector size (logical/physical): 512 bytes / 32768 bytes
>> >> >> > I/O size (minimum/optimal): 32768 bytes / 1048576 bytes
>> >> >> > Disk identifier: 0x
>> >> >> >
>> >> >> > Disk /dev/mapper/4861322b--352f--41c6--890a--5cbf1c2c1f01-
>> >> >> > master: 1073
>> >> >> > MB, 1073741824 bytes
>> >> >> > 255 heads, 63 sectors/track, 130 cylinders
>> >> >> > Units = cylinders of 16065 * 512 = 8225280 bytes
>> >> >> > Sector size (logical/physical): 512 bytes / 32768 bytes
>> >> >> > I/O size (minimum/optimal): 32768 bytes / 1048576 bytes
>> >> >> > Disk identifier: 0x
>> >> >> >
>> >> >> > Regards,
>> >> >> >
>> >> >> > --
>> >> >> > Fernando Fuentes
>> >> >> > ffuen...@txweather.org
>> >> >> > http://www.txweather.org
>> >> >> >
>> >> >> > On Sat, Jul 16, 2016, at 04:25 PM, Fernando Fuentes wrote:
>> >> >> >> Nir,
>> >> >> >>
>> >> >> >> Ok ill look for it here in a few.
>> >> >> >> Thanks for your reply and help!
>> >> >> >>
>> >> >> >> --
>> >> >> >> Fernando Fuentes
>> >> >> >> ffuen...@txweather.org
>> >> >> >> http://www.txweather.org
>> >> >> >>
>> >> >> >> On Sat, Jul 16, 2016, at 04:16 PM, Nir Soffer wrote:
>> >> >> >> > On Fri, Jul 15, 2016 at 3:50 PM, Fernando Fuentes
>> >> >> >> > <ffuen...@darktcp.net>
>> >> >> >> > wrote:
>> >> >> >> > > Nir,
>> >> >> >> > >
>> >> >> >> > > I try to follow your steps but I cant seem to find the
>> >> >> >> > > ID of the
>> >> >> >> > > template.
>> >> >> >> >
>> >> >> >> > The image-uuid of the template is displayed in the Disks
>> >> >> >> > tab in engine.
>> >> >> >> >
>> >> >> >> > To find the volume-uuid on block storage, you can do:
>> >> >> >> >
>> >> >> >> > pvscan --cache
>> >> >> >> > lvs -o vg_name,lv_name,tags | grep image-uuid
>> >> >> >> >
>> >> >> >> > >
>> >> >> >> > > Regards,
>> >> >> >> > >
>> >> >> >> > > --
>> >> >> >> > > Fernando Fuentes
>> >> >> >> > > ffuen...@txweather.org
>> >> >> >> > > http://www.txweather.org
>> >> >> >> > >
>> >> >> >> > > On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
>> >> >> >> > >> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler
>> >> >> >> > >> <meli...@justmelly.com>
>> >> >> >> > >> wrote:
>> >> >> >> > >> > All, I did a test for Fernando in our ovirt
>> >> >> >> > >> > environment. I created a vm
>> >> >> >> > >> > called win7melly in the nfs domain. I then migrated
>> >> >> >> > >> > it to the iscsi
>> >> >> >> > >> > domain. It booted without any issue. So it has to be
>> >> >> >> > >> > something with the
>> >> >> >> > >> > templates. I have attached the vdsm log for the host
>> >> >> >> > >> > the vm resides on.
>> >> >> >> > >>
>> >> >> >> >

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

rds,
> >> >> >
> >> >> > --
> >> >> > Fernando Fuentes
> >> >> > ffuen...@txweather.org
> >> >> > http://www.txweather.org
> >> >> >
> >> >> > On Sat, Jul 16, 2016, at 04:25 PM, Fernando Fuentes wrote:
> >> >> >> Nir,
> >> >> >>
> >> >> >> Ok ill look for it here in a few.
> >> >> >> Thanks for your reply and help!
> >> >> >>
> >> >> >> --
> >> >> >> Fernando Fuentes
> >> >> >> ffuen...@txweather.org
> >> >> >> http://www.txweather.org
> >> >> >>
> >> >> >> On Sat, Jul 16, 2016, at 04:16 PM, Nir Soffer wrote:
> >> >> >> > On Fri, Jul 15, 2016 at 3:50 PM, Fernando Fuentes
> >> >> >> > <ffuen...@darktcp.net>
> >> >> >> > wrote:
> >> >> >> > > Nir,
> >> >> >> > >
> >> >> >> > > I try to follow your steps but I cant seem to find the ID
> >> >> >> > > of the
> >> >> >> > > template.
> >> >> >> >
> >> >> >> > The image-uuid of the template is displayed in the Disks
> >> >> >> > tab in engine.
> >> >> >> >
> >> >> >> > To find the volume-uuid on block storage, you can do:
> >> >> >> >
> >> >> >> > pvscan --cache
> >> >> >> > lvs -o vg_name,lv_name,tags | grep image-uuid
> >> >> >> >
> >> >> >> > >
> >> >> >> > > Regards,
> >> >> >> > >
> >> >> >> > > --
> >> >> >> > > Fernando Fuentes
> >> >> >> > > ffuen...@txweather.org
> >> >> >> > > http://www.txweather.org
> >> >> >> > >
> >> >> >> > > On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> >> >> >> > >> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler
> >> >> >> > >> <meli...@justmelly.com>
> >> >> >> > >> wrote:
> >> >> >> > >> > All, I did a test for Fernando in our ovirt
> >> >> >> > >> > environment. I created a vm
> >> >> >> > >> > called win7melly in the nfs domain. I then migrated it
> >> >> >> > >> > to the iscsi
> >> >> >> > >> > domain. It booted without any issue. So it has to be
> >> >> >> > >> > something with the
> >> >> >> > >> > templates. I have attached the vdsm log for the host
> >> >> >> > >> > the vm resides on.
> >> >> >> > >>
> >> >> >> > >> The log show a working vm, so it does not help much.
> >> >> >> > >>
> >> >> >> > >> I think that the template you copied from the nfs domain
> >> >> >> > >> to the block
> >> >> >> > >> domain is
> >> >> >> > >> corrupted, or the volume metadata are incorrect.
> >> >> >> > >>
> >> >> >> > >> If I understand this correctly, this started when
> >> >> >> > >> Fernando could not copy
> >> >> >> > >> the vm
> >> >> >> > >> disk to the block storage, and I guess the issue was
> >> >> >> > >> that the template
> >> >> >> > >> was missing
> >> >> >> > >> on that storage domain. I assume that he copied the
> >> >> >> > >> template to the
> >> >> >> > >> block storage
> >> >> >> > >> domain by opening the templates tab, selecting the
> >> >> >> > >> template, and choosing
> >> >> >> > >> copy
> >> >> >> > >> from the menu.
> >> >> >> > >>
> >> >> >> > >> Lets compare the template on both nfs and block storage
> >> >> >> > >> do

Re: [ovirt-users] disk not bootable

[Nir Soffer]

m to find the ID of
the
>> >> >> > > template.
>> >> >> >
>> >> >> > The image-uuid of the template is displayed in the Disks tab in
engine.
>> >> >> >
>> >> >> > To find the volume-uuid on block storage, you can do:
>> >> >> >
>> >> >> > pvscan --cache
>> >> >> > lvs -o vg_name,lv_name,tags | grep image-uuid
>> >> >> >
>> >> >> > >
>> >> >> > > Regards,
>> >> >> > >
>> >> >> > > --
>> >> >> > > Fernando Fuentes
>> >> >> > > ffuen...@txweather.org
>> >> >> > > http://www.txweather.org
>> >> >> > >
>> >> >> > > On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
>> >> >> > >> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler <
meli...@justmelly.com>
>> >> >> > >> wrote:
>> >> >> > >> > All, I did a test for Fernando in our ovirt environment. I
created a vm
>> >> >> > >> > called win7melly in the nfs domain. I then migrated it to
the iscsi
>> >> >> > >> > domain. It booted without any issue. So it has to be
something with the
>> >> >> > >> > templates. I have attached the vdsm log for the host the vm
resides on.
>> >> >> > >>
>> >> >> > >> The log show a working vm, so it does not help much.
>> >> >> > >>
>> >> >> > >> I think that the template you copied from the nfs domain to
the block
>> >> >> > >> domain is
>> >> >> > >> corrupted, or the volume metadata are incorrect.
>> >> >> > >>
>> >> >> > >> If I understand this correctly, this started when Fernando
could not copy
>> >> >> > >> the vm
>> >> >> > >> disk to the block storage, and I guess the issue was that the
template
>> >> >> > >> was missing
>> >> >> > >> on that storage domain. I assume that he copied the template
to the
>> >> >> > >> block storage
>> >> >> > >> domain by opening the templates tab, selecting the template,
and choosing
>> >> >> > >> copy
>> >> >> > >> from the menu.
>> >> >> > >>
>> >> >> > >> Lets compare the template on both nfs and block storage
domain.
>> >> >> > >>
>> >> >> > >> 1. Find the template on the nfs storage domain, using the
image uuid in
>> >> >> > >> engine.
>> >> >> > >>
>> >> >> > >> It should be at
>> >> >> > >>
>> >> >> > >>
/rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
>> >> >> > >>
>> >> >> > >> 2. Please share the output of:
>> >> >> > >>
>> >> >> > >> cat /path/to/volume.meta
>> >> >> > >> qemu-img info /path/to/volume
>> >> >> > >> qemu-img check /path/to/volume
>> >> >> > >>
>> >> >> > >> 4. Find the template on the block storage domain
>> >> >> > >>
>> >> >> > >> You should have an lv using the same volume uuid and the
image-uuid
>> >> >> > >> should be in the lv tag.
>> >> >> > >>
>> >> >> > >> Find it using:
>> >> >> > >>
>> >> >> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
>> >> >> > >>
>> >> >> > >> 5. Activate the lv
>> >> >> > >>
>> >> >> > >> lvchange -ay vg_name/lv_name
>> >> >> > >>
>> >> >> > >> 6. Share the output of
>> >> >> > >>
>> >> >> > >> qemu-img info /dev/vg_name/lv_name
>> >> >> > >> qemu-img check /dev/vg_name/lv_name
>> >> >> > >>
>> >> >> > >> 7. Deactivate the lv
>> 

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

gt; >> > >> block storage
> >> >> > >> domain by opening the templates tab, selecting the template, and 
> >> >> > >> choosing
> >> >> > >> copy
> >> >> > >> from the menu.
> >> >> > >>
> >> >> > >> Lets compare the template on both nfs and block storage domain.
> >> >> > >>
> >> >> > >> 1. Find the template on the nfs storage domain, using the image 
> >> >> > >> uuid in
> >> >> > >> engine.
> >> >> > >>
> >> >> > >> It should be at
> >> >> > >>
> >> >> > >> 
> >> >> > >> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
> >> >> > >>
> >> >> > >> 2. Please share the output of:
> >> >> > >>
> >> >> > >> cat /path/to/volume.meta
> >> >> > >> qemu-img info /path/to/volume
> >> >> > >> qemu-img check /path/to/volume
> >> >> > >>
> >> >> > >> 4. Find the template on the block storage domain
> >> >> > >>
> >> >> > >> You should have an lv using the same volume uuid and the image-uuid
> >> >> > >> should be in the lv tag.
> >> >> > >>
> >> >> > >> Find it using:
> >> >> > >>
> >> >> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
> >> >> > >>
> >> >> > >> 5. Activate the lv
> >> >> > >>
> >> >> > >> lvchange -ay vg_name/lv_name
> >> >> > >>
> >> >> > >> 6. Share the output of
> >> >> > >>
> >> >> > >> qemu-img info /dev/vg_name/lv_name
> >> >> > >> qemu-img check /dev/vg_name/lv_name
> >> >> > >>
> >> >> > >> 7. Deactivate the lv
> >> >> > >>
> >> >> > >> lvchange -an vg_name/lv_name
> >> >> > >>
> >> >> > >> 8. Find the lv metadata
> >> >> > >>
> >> >> > >> The metadata is stored in /dev/vg_name/metadata. To find the 
> >> >> > >> correct
> >> >> > >> block,
> >> >> > >> find the tag named MD_N in the lv tags you found in step 4
> >> >> > >>
> >> >> > >> The block we need is located at offset N from start of volume.
> >> >> > >>
> >> >> > >> 9. Share the output of:
> >> >> > >>
> >> >> > >> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
> >> >> > >>
> >> >> > >> The output of this command should show the image-uuid.
> >> >> > >>
> >> >> > >> Nir
> >> >> > >>
> >> >> > >> >
> >> >> > >> > - MeLLy
> >> >> > >> >
> >> >> > >> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
> >> >> > >> >> Nir,
> >> >> > >> >>
> >> >> > >> >> That's exactly how I did it Nir.
> >> >> > >> >> I will test tomorrow with a new Windows VM and report back.
> >> >> > >> >>
> >> >> > >> >> Regards,
> >> >> > >> >>
> >> >> > >> >> --
> >> >> > >> >> Fernando Fuentes
> >> >> > >> >> ffuen...@txweather.org
> >> >> > >> >> http://www.txweather.org
> >> >> > >> >>
> >> >> > >> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> >> >> > >> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani 
> >> >> > >> >> > <from...@redhat.com>
> >> >> > >> >> > wrote:
> >> >> > >> >> > > - Original Message -
> >> >> > >> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
> >> >> > >> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> >> >> > >> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" 
> >> >> > >> >> > >> <users@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 
> >> >> > >> >> > >> <ffuen...@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]
> >> >> > >> >> > >
> >> >> > >> >> > >
> >> >> > >> >> > >>   oVirt
> >> >> > >> >> > >>   oVirt Node
> >> >> > >> >> > >>   6-5.el6.centos.11.2
> >> >> > >> >> > >> -  >> >> > >> >> > >> name="serial">C938F077-55E2-3E50-A694-9FCB7661FD89
> >> >> > >> >> > >> +  >> >> > >> >> > >> name="serial">735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> >> >> > >> >> > >>
> >> >> > >> >> > >> 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.
> >> >> > >> >> >
> >> >> > >> >> > Fernando, can you describe exactly how you moved the disk?
> >> >> > >> >> >
> >> >> > >> >> > I assume that you selected the vm in the virtual machines 
> >> >> > >> >> > tab, then
> >> >> > >> >> > selected
> >> >> > >> >> > disks from the sub tab, then selected move, and selected the 
> >> >> > >> >> > target
> >> >> > >> >> > storage domain.
> >> >> > >> >> >
> >> >> > >> >> > Also, can you reproduce this with a new vm? (create vm with 
> >> >> > >> >> > disk nfs,
> >> >> > >> >> > stop vm,
> >> >> > >> >> > move disk to iscsi, start vm).
> >> >> > >> >> >
> >> >> > >> >> > > 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@ovirt.org
> >> >> > >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> >> > >> >
> >> >> > >> > ___
> >> >> > >> > Users mailing list
> >> >> > >> > Users@ovirt.org
> >> >> > >> > http://lists.ovirt.org/mailman/listinfo/users
> >> >> > >> >
> >> >> ___
> >> >> Users mailing list
> >> >> Users@ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Nir Soffer]

M, Melissa Mesler 
>> >> > >> <meli...@justmelly.com>
>> >> > >> wrote:
>> >> > >> > All, I did a test for Fernando in our ovirt environment. I created 
>> >> > >> > a vm
>> >> > >> > called win7melly in the nfs domain. I then migrated it to the iscsi
>> >> > >> > domain. It booted without any issue. So it has to be something 
>> >> > >> > with the
>> >> > >> > templates. I have attached the vdsm log for the host the vm 
>> >> > >> > resides on.
>> >> > >>
>> >> > >> The log show a working vm, so it does not help much.
>> >> > >>
>> >> > >> I think that the template you copied from the nfs domain to the block
>> >> > >> domain is
>> >> > >> corrupted, or the volume metadata are incorrect.
>> >> > >>
>> >> > >> If I understand this correctly, this started when Fernando could not 
>> >> > >> copy
>> >> > >> the vm
>> >> > >> disk to the block storage, and I guess the issue was that the 
>> >> > >> template
>> >> > >> was missing
>> >> > >> on that storage domain. I assume that he copied the template to the
>> >> > >> block storage
>> >> > >> domain by opening the templates tab, selecting the template, and 
>> >> > >> choosing
>> >> > >> copy
>> >> > >> from the menu.
>> >> > >>
>> >> > >> Lets compare the template on both nfs and block storage domain.
>> >> > >>
>> >> > >> 1. Find the template on the nfs storage domain, using the image uuid 
>> >> > >> in
>> >> > >> engine.
>> >> > >>
>> >> > >> It should be at
>> >> > >>
>> >> > >> 
>> >> > >> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
>> >> > >>
>> >> > >> 2. Please share the output of:
>> >> > >>
>> >> > >> cat /path/to/volume.meta
>> >> > >> qemu-img info /path/to/volume
>> >> > >> qemu-img check /path/to/volume
>> >> > >>
>> >> > >> 4. Find the template on the block storage domain
>> >> > >>
>> >> > >> You should have an lv using the same volume uuid and the image-uuid
>> >> > >> should be in the lv tag.
>> >> > >>
>> >> > >> Find it using:
>> >> > >>
>> >> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
>> >> > >>
>> >> > >> 5. Activate the lv
>> >> > >>
>> >> > >> lvchange -ay vg_name/lv_name
>> >> > >>
>> >> > >> 6. Share the output of
>> >> > >>
>> >> > >> qemu-img info /dev/vg_name/lv_name
>> >> > >> qemu-img check /dev/vg_name/lv_name
>> >> > >>
>> >> > >> 7. Deactivate the lv
>> >> > >>
>> >> > >> lvchange -an vg_name/lv_name
>> >> > >>
>> >> > >> 8. Find the lv metadata
>> >> > >>
>> >> > >> The metadata is stored in /dev/vg_name/metadata. To find the correct
>> >> > >> block,
>> >> > >> find the tag named MD_N in the lv tags you found in step 4
>> >> > >>
>> >> > >> The block we need is located at offset N from start of volume.
>> >> > >>
>> >> > >> 9. Share the output of:
>> >> > >>
>> >> > >> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
>> >> > >>
>> >> > >> The output of this command should show the image-uuid.
>> >> > >>
>> >> > >> Nir
>> >> > >>
>> >> > >> >
>> >> > >> > - MeLLy
>> >> > >> >
>> >> > >> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
>> >> > >> >> Nir

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

gt;
> >> > >> The log show a working vm, so it does not help much.
> >> > >>
> >> > >> I think that the template you copied from the nfs domain to the block
> >> > >> domain is
> >> > >> corrupted, or the volume metadata are incorrect.
> >> > >>
> >> > >> If I understand this correctly, this started when Fernando could not 
> >> > >> copy
> >> > >> the vm
> >> > >> disk to the block storage, and I guess the issue was that the template
> >> > >> was missing
> >> > >> on that storage domain. I assume that he copied the template to the
> >> > >> block storage
> >> > >> domain by opening the templates tab, selecting the template, and 
> >> > >> choosing
> >> > >> copy
> >> > >> from the menu.
> >> > >>
> >> > >> Lets compare the template on both nfs and block storage domain.
> >> > >>
> >> > >> 1. Find the template on the nfs storage domain, using the image uuid 
> >> > >> in
> >> > >> engine.
> >> > >>
> >> > >> It should be at
> >> > >>
> >> > >> 
> >> > >> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
> >> > >>
> >> > >> 2. Please share the output of:
> >> > >>
> >> > >> cat /path/to/volume.meta
> >> > >> qemu-img info /path/to/volume
> >> > >> qemu-img check /path/to/volume
> >> > >>
> >> > >> 4. Find the template on the block storage domain
> >> > >>
> >> > >> You should have an lv using the same volume uuid and the image-uuid
> >> > >> should be in the lv tag.
> >> > >>
> >> > >> Find it using:
> >> > >>
> >> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
> >> > >>
> >> > >> 5. Activate the lv
> >> > >>
> >> > >> lvchange -ay vg_name/lv_name
> >> > >>
> >> > >> 6. Share the output of
> >> > >>
> >> > >> qemu-img info /dev/vg_name/lv_name
> >> > >> qemu-img check /dev/vg_name/lv_name
> >> > >>
> >> > >> 7. Deactivate the lv
> >> > >>
> >> > >> lvchange -an vg_name/lv_name
> >> > >>
> >> > >> 8. Find the lv metadata
> >> > >>
> >> > >> The metadata is stored in /dev/vg_name/metadata. To find the correct
> >> > >> block,
> >> > >> find the tag named MD_N in the lv tags you found in step 4
> >> > >>
> >> > >> The block we need is located at offset N from start of volume.
> >> > >>
> >> > >> 9. Share the output of:
> >> > >>
> >> > >> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
> >> > >>
> >> > >> The output of this command should show the image-uuid.
> >> > >>
> >> > >> Nir
> >> > >>
> >> > >> >
> >> > >> > - MeLLy
> >> > >> >
> >> > >> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
> >> > >> >> Nir,
> >> > >> >>
> >> > >> >> That's exactly how I did it Nir.
> >> > >> >> I will test tomorrow with a new Windows VM and report back.
> >> > >> >>
> >> > >> >> Regards,
> >> > >> >>
> >> > >> >> --
> >> > >> >> Fernando Fuentes
> >> > >> >> ffuen...@txweather.org
> >> > >> >> http://www.txweather.org
> >> > >> >>
> >> > >> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> >> > >> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani 
> >> > >> >> > <from...@redhat.com>
> >> > >> >> > wrote:
> >> > >> >> > > - Original Message -
> >> > >> >> > >> From: "Nir Soffer&

Re: [ovirt-users] disk not bootable

[Nir Soffer]

>> > >> choosing
>> > >> copy
>> > >> from the menu.
>> > >>
>> > >> Lets compare the template on both nfs and block storage domain.
>> > >>
>> > >> 1. Find the template on the nfs storage domain, using the image uuid in
>> > >> engine.
>> > >>
>> > >> It should be at
>> > >>
>> > >> 
>> > >> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
>> > >>
>> > >> 2. Please share the output of:
>> > >>
>> > >> cat /path/to/volume.meta
>> > >> qemu-img info /path/to/volume
>> > >> qemu-img check /path/to/volume
>> > >>
>> > >> 4. Find the template on the block storage domain
>> > >>
>> > >> You should have an lv using the same volume uuid and the image-uuid
>> > >> should be in the lv tag.
>> > >>
>> > >> Find it using:
>> > >>
>> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
>> > >>
>> > >> 5. Activate the lv
>> > >>
>> > >> lvchange -ay vg_name/lv_name
>> > >>
>> > >> 6. Share the output of
>> > >>
>> > >> qemu-img info /dev/vg_name/lv_name
>> > >> qemu-img check /dev/vg_name/lv_name
>> > >>
>> > >> 7. Deactivate the lv
>> > >>
>> > >>     lvchange -an vg_name/lv_name
>> > >>
>> > >> 8. Find the lv metadata
>> > >>
>> > >> The metadata is stored in /dev/vg_name/metadata. To find the correct
>> > >> block,
>> > >> find the tag named MD_N in the lv tags you found in step 4
>> > >>
>> > >> The block we need is located at offset N from start of volume.
>> > >>
>> > >> 9. Share the output of:
>> > >>
>> > >> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
>> > >>
>> > >> The output of this command should show the image-uuid.
>> > >>
>> > >> Nir
>> > >>
>> > >> >
>> > >> > - MeLLy
>> > >> >
>> > >> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
>> > >> >> Nir,
>> > >> >>
>> > >> >> That's exactly how I did it Nir.
>> > >> >> I will test tomorrow with a new Windows VM and report back.
>> > >> >>
>> > >> >> Regards,
>> > >> >>
>> > >> >> --
>> > >> >> Fernando Fuentes
>> > >> >> ffuen...@txweather.org
>> > >> >> http://www.txweather.org
>> > >> >>
>> > >> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
>> > >> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani 
>> > >> >> > <from...@redhat.com>
>> > >> >> > wrote:
>> > >> >> > > - Original Message -
>> > >> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
>> > >> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
>> > >> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" 
>> > >> >> > >> <users@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 
>> > >> >> > >> <ffuen...@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]
>> > >> >> > >
>> > >> >> > >
>> > >> >> > >>   oVirt
>> > >> >> > >>   oVirt Node
>> > >> >> > >>   6-5.el6.centos.11.2
>> > >> >> > >> - > > >> >> > >> name="serial">C938F077-55E2-3E50-A694-9FCB7661FD89
>> > >> >> > >> + > > >> >> > >> name="serial">735C7A01-1F16-3CF0-AF8C-A99823E95AC0
>> > >> >> > >>
>> > >> >> > >> 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.
>> > >> >> >
>> > >> >> > Fernando, can you describe exactly how you moved the disk?
>> > >> >> >
>> > >> >> > I assume that you selected the vm in the virtual machines tab, then
>> > >> >> > selected
>> > >> >> > disks from the sub tab, then selected move, and selected the target
>> > >> >> > storage domain.
>> > >> >> >
>> > >> >> > Also, can you reproduce this with a new vm? (create vm with disk 
>> > >> >> > nfs,
>> > >> >> > stop vm,
>> > >> >> > move disk to iscsi, start vm).
>> > >> >> >
>> > >> >> > > 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@ovirt.org
>> > >> >> http://lists.ovirt.org/mailman/listinfo/users
>> > >> >
>> > >> > ___
>> > >> > Users mailing list
>> > >> > Users@ovirt.org
>> > >> > http://lists.ovirt.org/mailman/listinfo/users
>> > >> >
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

ate on the block storage domain
> > >>
> > >> You should have an lv using the same volume uuid and the image-uuid
> > >> should be in the lv tag.
> > >>
> > >> Find it using:
> > >>
> > >> lvs -o vg_name,lv_name,tags | grep volume-uuid
> > >>
> > >> 5. Activate the lv
> > >>
> > >> lvchange -ay vg_name/lv_name
> > >>
> > >> 6. Share the output of
> > >>
> > >> qemu-img info /dev/vg_name/lv_name
> > >> qemu-img check /dev/vg_name/lv_name
> > >>
> > >> 7. Deactivate the lv
> > >>
> > >> lvchange -an vg_name/lv_name
> > >>
> > >> 8. Find the lv metadata
> > >>
> > >> The metadata is stored in /dev/vg_name/metadata. To find the correct
> > >> block,
> > >> find the tag named MD_N in the lv tags you found in step 4
> > >>
> > >> The block we need is located at offset N from start of volume.
> > >>
> > >> 9. Share the output of:
> > >>
> > >> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
> > >>
> > >> The output of this command should show the image-uuid.
> > >>
> > >> Nir
> > >>
> > >> >
> > >> > - MeLLy
> > >> >
> > >> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
> > >> >> Nir,
> > >> >>
> > >> >> That's exactly how I did it Nir.
> > >> >> I will test tomorrow with a new Windows VM and report back.
> > >> >>
> > >> >> Regards,
> > >> >>
> > >> >> --
> > >> >> Fernando Fuentes
> > >> >> ffuen...@txweather.org
> > >> >> http://www.txweather.org
> > >> >>
> > >> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> > >> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani 
> > >> >> > <from...@redhat.com>
> > >> >> > wrote:
> > >> >> > > - Original Message -
> > >> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
> > >> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> > >> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" 
> > >> >> > >> <users@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 
> > >> >> > >> <ffuen...@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]
> > >> >> > >
> > >> >> > >
> > >> >> > >>   oVirt
> > >> >> > >>   oVirt Node
> > >> >> > >>   6-5.el6.centos.11.2
> > >> >> > >> -  > >> >> > >> name="serial">C938F077-55E2-3E50-A694-9FCB7661FD89
> > >> >> > >> +  > >> >> > >> name="serial">735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> > >> >> > >>
> > >> >> > >> 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.
> > >> >> >
> > >> >> > Fernando, can you describe exactly how you moved the disk?
> > >> >> >
> > >> >> > I assume that you selected the vm in the virtual machines tab, then
> > >> >> > selected
> > >> >> > disks from the sub tab, then selected move, and selected the target
> > >> >> > storage domain.
> > >> >> >
> > >> >> > Also, can you reproduce this with a new vm? (create vm with disk 
> > >> >> > nfs,
> > >> >> > stop vm,
> > >> >> > move disk to iscsi, start vm).
> > >> >> >
> > >> >> > > 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@ovirt.org
> > >> >> http://lists.ovirt.org/mailman/listinfo/users
> > >> >
> > >> > ___
> > >> > Users mailing list
> > >> > Users@ovirt.org
> > >> > http://lists.ovirt.org/mailman/listinfo/users
> > >> >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Nir Soffer]

On Fri, Jul 15, 2016 at 3:50 PM, Fernando Fuentes <ffuen...@darktcp.net> wrote:
> Nir,
>
> I try to follow your steps but I cant seem to find the ID of the
> template.

The image-uuid of the template is displayed in the Disks tab in engine.

To find the volume-uuid on block storage, you can do:

pvscan --cache
lvs -o vg_name,lv_name,tags | grep image-uuid

>
> Regards,
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
> On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
>> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler <meli...@justmelly.com>
>> wrote:
>> > All, I did a test for Fernando in our ovirt environment. I created a vm
>> > called win7melly in the nfs domain. I then migrated it to the iscsi
>> > domain. It booted without any issue. So it has to be something with the
>> > templates. I have attached the vdsm log for the host the vm resides on.
>>
>> The log show a working vm, so it does not help much.
>>
>> I think that the template you copied from the nfs domain to the block
>> domain is
>> corrupted, or the volume metadata are incorrect.
>>
>> If I understand this correctly, this started when Fernando could not copy
>> the vm
>> disk to the block storage, and I guess the issue was that the template
>> was missing
>> on that storage domain. I assume that he copied the template to the
>> block storage
>> domain by opening the templates tab, selecting the template, and choosing
>> copy
>> from the menu.
>>
>> Lets compare the template on both nfs and block storage domain.
>>
>> 1. Find the template on the nfs storage domain, using the image uuid in
>> engine.
>>
>> It should be at
>>
>> 
>> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
>>
>> 2. Please share the output of:
>>
>> cat /path/to/volume.meta
>> qemu-img info /path/to/volume
>> qemu-img check /path/to/volume
>>
>> 4. Find the template on the block storage domain
>>
>> You should have an lv using the same volume uuid and the image-uuid
>> should be in the lv tag.
>>
>> Find it using:
>>
>> lvs -o vg_name,lv_name,tags | grep volume-uuid
>>
>> 5. Activate the lv
>>
>> lvchange -ay vg_name/lv_name
>>
>> 6. Share the output of
>>
>> qemu-img info /dev/vg_name/lv_name
>> qemu-img check /dev/vg_name/lv_name
>>
>> 7. Deactivate the lv
>>
>> lvchange -an vg_name/lv_name
>>
>> 8. Find the lv metadata
>>
>> The metadata is stored in /dev/vg_name/metadata. To find the correct
>> block,
>> find the tag named MD_N in the lv tags you found in step 4
>>
>> The block we need is located at offset N from start of volume.
>>
>> 9. Share the output of:
>>
>> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
>>
>> The output of this command should show the image-uuid.
>>
>> Nir
>>
>> >
>> > - MeLLy
>> >
>> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
>> >> Nir,
>> >>
>> >> That's exactly how I did it Nir.
>> >> I will test tomorrow with a new Windows VM and report back.
>> >>
>> >> Regards,
>> >>
>> >> --
>> >> Fernando Fuentes
>> >> ffuen...@txweather.org
>> >> http://www.txweather.org
>> >>
>> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
>> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani <from...@redhat.com>
>> >> > wrote:
>> >> > > - Original Message -
>> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
>> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
>> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" 
>> >> > >> <users@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 
>> >> > >> <ffuen...@darktcp.net>
>> >> > >> wrote:
>> >> > >> > Nir,
>> >> > >> >
>> >> > >> > Ok I ran another test and this one I moved from NFS domain to 
>> >>

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Nir,

I try to follow your steps but I cant seem to find the ID of the
template.

Regards, 

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler <meli...@justmelly.com>
> wrote:
> > All, I did a test for Fernando in our ovirt environment. I created a vm
> > called win7melly in the nfs domain. I then migrated it to the iscsi
> > domain. It booted without any issue. So it has to be something with the
> > templates. I have attached the vdsm log for the host the vm resides on.
> 
> The log show a working vm, so it does not help much.
> 
> I think that the template you copied from the nfs domain to the block
> domain is
> corrupted, or the volume metadata are incorrect.
> 
> If I understand this correctly, this started when Fernando could not copy
> the vm
> disk to the block storage, and I guess the issue was that the template
> was missing
> on that storage domain. I assume that he copied the template to the
> block storage
> domain by opening the templates tab, selecting the template, and choosing
> copy
> from the menu.
> 
> Lets compare the template on both nfs and block storage domain.
> 
> 1. Find the template on the nfs storage domain, using the image uuid in
> engine.
> 
> It should be at
> 
> 
> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
> 
> 2. Please share the output of:
> 
> cat /path/to/volume.meta
> qemu-img info /path/to/volume
> qemu-img check /path/to/volume
> 
> 4. Find the template on the block storage domain
> 
> You should have an lv using the same volume uuid and the image-uuid
> should be in the lv tag.
> 
> Find it using:
> 
> lvs -o vg_name,lv_name,tags | grep volume-uuid
> 
> 5. Activate the lv
> 
> lvchange -ay vg_name/lv_name
> 
> 6. Share the output of
> 
> qemu-img info /dev/vg_name/lv_name
> qemu-img check /dev/vg_name/lv_name
> 
> 7. Deactivate the lv
> 
> lvchange -an vg_name/lv_name
> 
> 8. Find the lv metadata
> 
> The metadata is stored in /dev/vg_name/metadata. To find the correct
> block,
> find the tag named MD_N in the lv tags you found in step 4
> 
> The block we need is located at offset N from start of volume.
> 
> 9. Share the output of:
> 
> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
> 
> The output of this command should show the image-uuid.
> 
> Nir
> 
> >
> > - MeLLy
> >
> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
> >> Nir,
> >>
> >> That's exactly how I did it Nir.
> >> I will test tomorrow with a new Windows VM and report back.
> >>
> >> Regards,
> >>
> >> --
> >> Fernando Fuentes
> >> ffuen...@txweather.org
> >> http://www.txweather.org
> >>
> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani <from...@redhat.com>
> >> > wrote:
> >> > > - Original Message -
> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 
> >> > >> <ffuen...@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]
> >> > >
> >> > >
> >> > >>   oVirt
> >> > >>   oVirt Node
> >> > >>   6-5.el6.centos.11.2
> >> > >

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Nir,

I am on it and will reply with the requested info asap.

Regards,

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler <meli...@justmelly.com>
> wrote:
> > All, I did a test for Fernando in our ovirt environment. I created a vm
> > called win7melly in the nfs domain. I then migrated it to the iscsi
> > domain. It booted without any issue. So it has to be something with the
> > templates. I have attached the vdsm log for the host the vm resides on.
> 
> The log show a working vm, so it does not help much.
> 
> I think that the template you copied from the nfs domain to the block
> domain is
> corrupted, or the volume metadata are incorrect.
> 
> If I understand this correctly, this started when Fernando could not copy
> the vm
> disk to the block storage, and I guess the issue was that the template
> was missing
> on that storage domain. I assume that he copied the template to the
> block storage
> domain by opening the templates tab, selecting the template, and choosing
> copy
> from the menu.
> 
> Lets compare the template on both nfs and block storage domain.
> 
> 1. Find the template on the nfs storage domain, using the image uuid in
> engine.
> 
> It should be at
> 
> 
> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
> 
> 2. Please share the output of:
> 
> cat /path/to/volume.meta
> qemu-img info /path/to/volume
> qemu-img check /path/to/volume
> 
> 4. Find the template on the block storage domain
> 
> You should have an lv using the same volume uuid and the image-uuid
> should be in the lv tag.
> 
> Find it using:
> 
> lvs -o vg_name,lv_name,tags | grep volume-uuid
> 
> 5. Activate the lv
> 
> lvchange -ay vg_name/lv_name
> 
> 6. Share the output of
> 
> qemu-img info /dev/vg_name/lv_name
> qemu-img check /dev/vg_name/lv_name
> 
> 7. Deactivate the lv
> 
> lvchange -an vg_name/lv_name
> 
> 8. Find the lv metadata
> 
> The metadata is stored in /dev/vg_name/metadata. To find the correct
> block,
> find the tag named MD_N in the lv tags you found in step 4
> 
> The block we need is located at offset N from start of volume.
> 
> 9. Share the output of:
> 
> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
> 
> The output of this command should show the image-uuid.
> 
> Nir
> 
> >
> > - MeLLy
> >
> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
> >> Nir,
> >>
> >> That's exactly how I did it Nir.
> >> I will test tomorrow with a new Windows VM and report back.
> >>
> >> Regards,
> >>
> >> --
> >> Fernando Fuentes
> >> ffuen...@txweather.org
> >> http://www.txweather.org
> >>
> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani <from...@redhat.com>
> >> > wrote:
> >> > > - Original Message -
> >> > >> From: "Nir Soffer" <nsof...@redhat.com>
> >> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> >> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 
> >> > >> <ffuen...@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]
> >> > >
> >> > >
> >> > >>   oVirt
> >> > >>   oVirt Node
> >> > >>   6-5.el6.centos.11.2
> >> > >> - C938F077-55E

Re: [ovirt-users] disk not bootable

[Nir Soffer]

On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler <meli...@justmelly.com> wrote:
> All, I did a test for Fernando in our ovirt environment. I created a vm
> called win7melly in the nfs domain. I then migrated it to the iscsi
> domain. It booted without any issue. So it has to be something with the
> templates. I have attached the vdsm log for the host the vm resides on.

The log show a working vm, so it does not help much.

I think that the template you copied from the nfs domain to the block domain is
corrupted, or the volume metadata are incorrect.

If I understand this correctly, this started when Fernando could not copy the vm
disk to the block storage, and I guess the issue was that the template
was missing
on that storage domain. I assume that he copied the template to the
block storage
domain by opening the templates tab, selecting the template, and choosing copy
from the menu.

Lets compare the template on both nfs and block storage domain.

1. Find the template on the nfs storage domain, using the image uuid in engine.

It should be at

/rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid

2. Please share the output of:

cat /path/to/volume.meta
qemu-img info /path/to/volume
qemu-img check /path/to/volume

4. Find the template on the block storage domain

You should have an lv using the same volume uuid and the image-uuid
should be in the lv tag.

Find it using:

lvs -o vg_name,lv_name,tags | grep volume-uuid

5. Activate the lv

lvchange -ay vg_name/lv_name

6. Share the output of

qemu-img info /dev/vg_name/lv_name
qemu-img check /dev/vg_name/lv_name

7. Deactivate the lv

lvchange -an vg_name/lv_name

8. Find the lv metadata

The metadata is stored in /dev/vg_name/metadata. To find the correct block,
find the tag named MD_N in the lv tags you found in step 4

The block we need is located at offset N from start of volume.

9. Share the output of:

dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct

The output of this command should show the image-uuid.

Nir

>
> - MeLLy
>
> On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
>> Nir,
>>
>> That's exactly how I did it Nir.
>> I will test tomorrow with a new Windows VM and report back.
>>
>> Regards,
>>
>> --
>> Fernando Fuentes
>> ffuen...@txweather.org
>> http://www.txweather.org
>>
>> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
>> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani <from...@redhat.com>
>> > wrote:
>> > > - Original Message -
>> > >> From: "Nir Soffer" <nsof...@redhat.com>
>> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
>> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]
>> > >
>> > >
>> > >>   oVirt
>> > >>   oVirt Node
>> > >>   6-5.el6.centos.11.2
>> > >> - C938F077-55E2-3E50-A694-9FCB7661FD89
>> > >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
>> > >>
>> > >> 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.
>> >
>> > Fernando, can you describe exactly how you moved the disk?
>> >
>> > I assume that you selected the vm in the virtual machines ta

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Team,

Any more ideas? :(

-- 
Fernando Fuentes
ffuen...@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 <from...@redhat.com> wrote:
> > > 
> > > - Original Message -
> > >> From: "Nir Soffer" <nsof...@redhat.com>
> > >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> > >> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]
> > > 
> > > 
> > >>  oVirt
> > >>  oVirt Node
> > >>  6-5.el6.centos.11.2
> > >> - C938F077-55E2-3E50-A694-9FCB7661FD89
> > >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> > >> 
> > >> 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@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > 
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Melissa Mesler]

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 <from...@redhat.com> wrote:
> > 
> > - Original Message -
> >> From: "Nir Soffer" <nsof...@redhat.com>
> >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> >> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]
> > 
> > 
> >>  oVirt
> >>  oVirt Node
> >>  6-5.el6.centos.11.2
> >> - C938F077-55E2-3E50-A694-9FCB7661FD89
> >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> >> 
> >> 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@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Michal Skrivanek]

> On 04 Jul 2016, at 17:43, Francesco Romani <from...@redhat.com> wrote:
> 
> - Original Message -
>> From: "Nir Soffer" <nsof...@redhat.com>
>> To: "Fernando Fuentes" <ffuen...@darktcp.net>
>> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]
> 
> 
>>  oVirt
>>  oVirt Node
>>  6-5.el6.centos.11.2
>> - C938F077-55E2-3E50-A694-9FCB7661FD89
>> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
>> 
>> 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@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Nir,

That's exactly how I did it Nir.
I will test tomorrow with a new Windows VM and report back.

Regards,

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani <from...@redhat.com>
> wrote:
> > - Original Message -
> >> From: "Nir Soffer" <nsof...@redhat.com>
> >> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> >> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]
> >
> >
> >>   oVirt
> >>   oVirt Node
> >>   6-5.el6.centos.11.2
> >> - C938F077-55E2-3E50-A694-9FCB7661FD89
> >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> >>
> >> 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.
> 
> Fernando, can you describe exactly how you moved the disk?
> 
> I assume that you selected the vm in the virtual machines tab, then
> selected
> disks from the sub tab, then selected move, and selected the target
> storage domain.
> 
> Also, can you reproduce this with a new vm? (create vm with disk nfs,
> stop vm,
> move disk to iscsi, start vm).
> 
> > 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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Nir Soffer]

On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani <from...@redhat.com> wrote:
> - Original Message -
>> From: "Nir Soffer" <nsof...@redhat.com>
>> To: "Fernando Fuentes" <ffuen...@darktcp.net>
>> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]
>
>
>>   oVirt
>>   oVirt Node
>>   6-5.el6.centos.11.2
>> - C938F077-55E2-3E50-A694-9FCB7661FD89
>> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
>>
>> 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.

Fernando, can you describe exactly how you moved the disk?

I assume that you selected the vm in the virtual machines tab, then selected
disks from the sub tab, then selected move, and selected the target
storage domain.

Also, can you reproduce this with a new vm? (create vm with disk nfs, stop vm,
move disk to iscsi, start vm).

> 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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Francesco Romani]

- Original Message -
> From: "Nir Soffer" <nsof...@redhat.com>
> To: "Fernando Fuentes" <ffuen...@darktcp.net>
> Cc: "Francesco Romani" <from...@redhat.com>, "users" <users@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 <ffuen...@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]


>   oVirt
>   oVirt Node
>   6-5.el6.centos.11.2
> - C938F077-55E2-3E50-A694-9FCB7661FD89
> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> 
> 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Nir, 

I will try and get you a working xml. 

Any updates on your question from the team? 
TIA! 
-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Sat, Jul 2, 2016, at 04:18 AM, Nir Soffer wrote:
> On Sat, Jul 2, 2016 at 1:33 AM, Fernando Fuentes 
> 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.
> 
> >
> > Now here is an example of one that I migrated from the NFS domain to the
> > iscsi domain and stop working:
> > VM: Win7-QA5
> > Host: Alpha
> > Info as requested:  http://pastebin.com/BXqLFqZt
> >
> > The same VM I moved it back to the NFS domain and boot it just fine:
> > VM: Win7-QA5
> > Host: Zeta
> > Info as requested:  http://pastebin.com/7BA97CsC
> 
> Diffing both xmls show:
> 
> $ diff -u win-qa5-iscsi.txt win-qa5-nfs.txt
> --- win-qa5-iscsi.txt 2016-07-02 12:10:17.094202558 +0300
> +++ win-qa5-nfs.txt 2016-07-02 12:11:06.729375231 +0300
> @@ -60,13 +60,13 @@
>   
>   
>   
> - 
> + 
> 
> Expected, one vm is using block based disk and the other file based disk
> 
>  type="pci"/>
> -  dev="/rhev/data-center/mnt/blockSD/4861322b-352f-41c6-890a-5cbf1c2c1f01/images/25ebd3ac-fe5a-4cbb-9f71-c6b4325231d8/763a9a47-6b29-420a-83c9-c8a887bd15df"/>
> +  file="/rhev/data-center/mnt/172.30.10.5:_opt_libvirtd_images/ecfaf7ac-5459-4c83-bd97-2bb448e38526/images/25ebd3ac-fe5a-4cbb-9f71-c6b4325231d8/763a9a47-6b29-420a-83c9-c8a887bd15df"/>
> 
> Expected, file and block disks are mounted on different paths
> 
>   
>   25ebd3ac-fe5a-4cbb-9f71-c6b4325231d8
>   
> -  type="qcow2"/>
> +  type="qcow2"/>
> 
> Expected, we use different io for file and block
> 
>   
>   
>   
> @@ -78,7 +78,7 @@
>   oVirt
>   oVirt Node
>   6-5.el6.centos.11.2
> - C938F077-55E2-3E50-A694-9FCB7661FD89
> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> 
> Not expected - maybe this is confusing windows?
> 
> Francesco, why vm serial has changed after moving disks from one storage
> domain
> to another?
> 
>   46e6d52c-2567-4f23-9a07-66f64990663a
>   
>   
> 
> 
> >
> > --
> > Fernando Fuentes
> > ffuen...@txweather.org
> > http://www.txweather.org
> >
> > On Fri, Jul 1, 2016, at 03:22 PM, Nir Soffer wrote:
> >> Fernando,
> >>
> >> These logs do not contain the libvirt xml.
> >>
> >> I want to see the part that start like this:
> >>
> >> Thread-17656::INFO::2016-07-01 23:17:33,845::vm::2032::virt.vm::(_run)
> >> vmId=`f66da2b0-0f71-490b-a57e-eceb9be9cade`:: >> encoding="utf-8"?>
> >> http://ovirt.org/vm/tune/1.0;>
> >> test-iscsi
> >> f66da2b0-0f71-490b-a57e-eceb9be9cade
> >> ...
> >>
> >> The most important part is the devices sections showing the disks:
> >>
> >> 
> >>  >> type="drive" unit="0"/>
> >>  >> dev="/rhev/data-center/f9374c0e-ae24-4bc1-a596-f61d5f05bc5f/5f35b5c0-17d7-4475-9125-e97f1cdb06f9/images/8f61b697-b3e4-4f63-8951-bdf9b6b39192/f409cc48-8248-4239-a4ea-66b0b1084416"/>
> >> 
> >> 
> >> 8f61b697-b3e4-4f63-8951-bdf9b6b39192
> >> 
> >>  >> io="native" name="qemu" type="qcow2"/>
> >> 
> >>
> >> Please try to find the logs (probably already rotated to vdsm.log.N.xz)
> >> containing the xml for this vm when running on nfs and iscsi.
> >>
> >> Nir
> >>
> >> On Fri, Jul 1, 2016 at 10:31 PM, Fernando Fuentes 
> >> wrote:
> >> > Nir.
> >> >
> >> > Thank you for your reply.
> >> >
> >> > Attached is the vdsm log of the hosts that power on the vm in this
> >> > example.
> >> >
> >> > VM name is Win7-QA5
> >> > vdsm_alpha.log was the host that started the VM when it got transfer to
> >> > the iscsi domain.
> >> > vdsm_zeta.log was the host that started the VM when it got transfer back
> >> > to the nfs domain.
> >> >
> >> > I included everything for trouble shooting purposes.
> >> >
> >> > Also here is the engine log that talks about it as well:
> >> > http://pastebin.com/3cHBNMcg
> >> >
> >> > Hope this helps.
> >> >
> >> > Regards,
> >> > --
> >> > Fernando Fuentes
> >> > ffuen...@txweather.org
> >> > http://www.txweather.org
> >> >
> >> > On Fri, Jul 1, 2016, at 01:58 PM, Nir Soffer wrote:
> >> >> On Fri, Jul 1, 2016 at 7:58 PM, Fernando Fuentes 
> >> >> wrote:
> >> >> > Pavel,
> >> >> >
> >> >> > Thanks for your reply, But thats not the problem
> >> >> > The disk is active and is set with to bootable. The problem presents 
> >> >> > it
> >> >> > self only if I move Windows VM DIsks.
> >> >> > All my Linux VM Disk's move across storage domains just fine.
> >> >> >
> >> >> > As a matter of fact I moved the disk back to the original nfs domain 
> >> >> > and
> >> >> > it started 

Re: [ovirt-users] disk not bootable

[Nir Soffer]

On Sat, Jul 2, 2016 at 1:33 AM, Fernando Fuentes  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.

>
> Now here is an example of one that I migrated from the NFS domain to the
> iscsi domain and stop working:
> VM: Win7-QA5
> Host: Alpha
> Info as requested:  http://pastebin.com/BXqLFqZt
>
> The same VM I moved it back to the NFS domain and boot it just fine:
> VM: Win7-QA5
> Host: Zeta
> Info as requested:  http://pastebin.com/7BA97CsC

Diffing both xmls show:

$ diff -u win-qa5-iscsi.txt win-qa5-nfs.txt
--- win-qa5-iscsi.txt 2016-07-02 12:10:17.094202558 +0300
+++ win-qa5-nfs.txt 2016-07-02 12:11:06.729375231 +0300
@@ -60,13 +60,13 @@
  
  
  
- 
+ 

Expected, one vm is using block based disk and the other file based disk

  
- 
+ 

Expected, file and block disks are mounted on different paths

  
  25ebd3ac-fe5a-4cbb-9f71-c6b4325231d8
  
- 
+ 

Expected, we use different io for file and block

  
  
  
@@ -78,7 +78,7 @@
  oVirt
  oVirt Node
  6-5.el6.centos.11.2
- C938F077-55E2-3E50-A694-9FCB7661FD89
+ 735C7A01-1F16-3CF0-AF8C-A99823E95AC0

Not expected - maybe this is confusing windows?

Francesco, why vm serial has changed after moving disks from one storage domain
to another?

  46e6d52c-2567-4f23-9a07-66f64990663a
  
  


>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
> On Fri, Jul 1, 2016, at 03:22 PM, Nir Soffer wrote:
>> Fernando,
>>
>> These logs do not contain the libvirt xml.
>>
>> I want to see the part that start like this:
>>
>> Thread-17656::INFO::2016-07-01 23:17:33,845::vm::2032::virt.vm::(_run)
>> vmId=`f66da2b0-0f71-490b-a57e-eceb9be9cade`::> encoding="utf-8"?>
>> http://ovirt.org/vm/tune/1.0;>
>> test-iscsi
>> f66da2b0-0f71-490b-a57e-eceb9be9cade
>> ...
>>
>> The most important part is the devices sections showing the disks:
>>
>> 
>> > type="drive" unit="0"/>
>> > dev="/rhev/data-center/f9374c0e-ae24-4bc1-a596-f61d5f05bc5f/5f35b5c0-17d7-4475-9125-e97f1cdb06f9/images/8f61b697-b3e4-4f63-8951-bdf9b6b39192/f409cc48-8248-4239-a4ea-66b0b1084416"/>
>> 
>> 8f61b697-b3e4-4f63-8951-bdf9b6b39192
>> 
>> > io="native" name="qemu" type="qcow2"/>
>> 
>>
>> Please try to find the logs (probably already rotated to vdsm.log.N.xz)
>> containing the xml for this vm when running on nfs and iscsi.
>>
>> Nir
>>
>> On Fri, Jul 1, 2016 at 10:31 PM, Fernando Fuentes 
>> wrote:
>> > Nir.
>> >
>> > Thank you for your reply.
>> >
>> > Attached is the vdsm log of the hosts that power on the vm in this
>> > example.
>> >
>> > VM name is Win7-QA5
>> > vdsm_alpha.log was the host that started the VM when it got transfer to
>> > the iscsi domain.
>> > vdsm_zeta.log was the host that started the VM when it got transfer back
>> > to the nfs domain.
>> >
>> > I included everything for trouble shooting purposes.
>> >
>> > Also here is the engine log that talks about it as well:
>> > http://pastebin.com/3cHBNMcg
>> >
>> > Hope this helps.
>> >
>> > Regards,
>> > --
>> > Fernando Fuentes
>> > ffuen...@txweather.org
>> > http://www.txweather.org
>> >
>> > On Fri, Jul 1, 2016, at 01:58 PM, Nir Soffer wrote:
>> >> On Fri, Jul 1, 2016 at 7:58 PM, Fernando Fuentes 
>> >> wrote:
>> >> > Pavel,
>> >> >
>> >> > Thanks for your reply, But thats not the problem
>> >> > The disk is active and is set with to bootable. The problem presents it
>> >> > self only if I move Windows VM DIsks.
>> >> > All my Linux VM Disk's move across storage domains just fine.
>> >> >
>> >> > As a matter of fact I moved the disk back to the original nfs domain and
>> >> > it started working.
>> >> > Could this be a bug?
>> >>
>> >> Can you share the vdsm log showing startup of the vm when the disk is on
>> >> on nfs storage domain (vm starts) and iscsi storage domain (vm fail)?
>> >>
>> >> The most interesting part in the logs is the libvirt xml describing the
>> >> vm.
>> >>
>> >> Nir
>> >>
>> >> > Regards,
>> >> >
>> >> > --
>> >> > Fernando Fuentes
>> >> > ffuen...@txweather.org
>> >> > http://www.txweather.org
>> >> >
>> >> > On Fri, Jul 1, 2016, at 11:33 AM, Pavel Gashev wrote:
>> >> >> Fernando,
>> >> >>
>> >> >> One from VM disks have to have bootable flag.
>> >> >> See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862
>> >> >>
>> >> >>
>> >> >> On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando
>> >> >> Fuentes" 
>> >> >> wrote:
>> >> >>
>> >> >> Team,
>> >> >>
>> >> >> After I successfully copy my template 

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

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

Now here is an example of one that I migrated from the NFS domain to the
iscsi domain and stop working:
VM: Win7-QA5
Host: Alpha
Info as requested:  http://pastebin.com/BXqLFqZt

The same VM I moved it back to the NFS domain and boot it just fine:
VM: Win7-QA5
Host: Zeta
Info as requested:  http://pastebin.com/7BA97CsC

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Fri, Jul 1, 2016, at 03:22 PM, Nir Soffer wrote:
> Fernando,
> 
> These logs do not contain the libvirt xml.
> 
> I want to see the part that start like this:
> 
> Thread-17656::INFO::2016-07-01 23:17:33,845::vm::2032::virt.vm::(_run)
> vmId=`f66da2b0-0f71-490b-a57e-eceb9be9cade`:: encoding="utf-8"?>
> http://ovirt.org/vm/tune/1.0;>
> test-iscsi
> f66da2b0-0f71-490b-a57e-eceb9be9cade
> ...
> 
> The most important part is the devices sections showing the disks:
> 
> 
>  type="drive" unit="0"/>
>  dev="/rhev/data-center/f9374c0e-ae24-4bc1-a596-f61d5f05bc5f/5f35b5c0-17d7-4475-9125-e97f1cdb06f9/images/8f61b697-b3e4-4f63-8951-bdf9b6b39192/f409cc48-8248-4239-a4ea-66b0b1084416"/>
> 
> 8f61b697-b3e4-4f63-8951-bdf9b6b39192
> 
>  io="native" name="qemu" type="qcow2"/>
> 
> 
> Please try to find the logs (probably already rotated to vdsm.log.N.xz)
> containing the xml for this vm when running on nfs and iscsi.
> 
> Nir
> 
> On Fri, Jul 1, 2016 at 10:31 PM, Fernando Fuentes 
> wrote:
> > Nir.
> >
> > Thank you for your reply.
> >
> > Attached is the vdsm log of the hosts that power on the vm in this
> > example.
> >
> > VM name is Win7-QA5
> > vdsm_alpha.log was the host that started the VM when it got transfer to
> > the iscsi domain.
> > vdsm_zeta.log was the host that started the VM when it got transfer back
> > to the nfs domain.
> >
> > I included everything for trouble shooting purposes.
> >
> > Also here is the engine log that talks about it as well:
> > http://pastebin.com/3cHBNMcg
> >
> > Hope this helps.
> >
> > Regards,
> > --
> > Fernando Fuentes
> > ffuen...@txweather.org
> > http://www.txweather.org
> >
> > On Fri, Jul 1, 2016, at 01:58 PM, Nir Soffer wrote:
> >> On Fri, Jul 1, 2016 at 7:58 PM, Fernando Fuentes 
> >> wrote:
> >> > Pavel,
> >> >
> >> > Thanks for your reply, But thats not the problem
> >> > The disk is active and is set with to bootable. The problem presents it
> >> > self only if I move Windows VM DIsks.
> >> > All my Linux VM Disk's move across storage domains just fine.
> >> >
> >> > As a matter of fact I moved the disk back to the original nfs domain and
> >> > it started working.
> >> > Could this be a bug?
> >>
> >> Can you share the vdsm log showing startup of the vm when the disk is on
> >> on nfs storage domain (vm starts) and iscsi storage domain (vm fail)?
> >>
> >> The most interesting part in the logs is the libvirt xml describing the
> >> vm.
> >>
> >> Nir
> >>
> >> > Regards,
> >> >
> >> > --
> >> > Fernando Fuentes
> >> > ffuen...@txweather.org
> >> > http://www.txweather.org
> >> >
> >> > On Fri, Jul 1, 2016, at 11:33 AM, Pavel Gashev wrote:
> >> >> Fernando,
> >> >>
> >> >> One from VM disks have to have bootable flag.
> >> >> See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862
> >> >>
> >> >>
> >> >> On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando
> >> >> Fuentes" 
> >> >> wrote:
> >> >>
> >> >> Team,
> >> >>
> >> >> After I successfully copy my template from one storage to another I was
> >> >> able to move my VM disks from my nfs domain to my iscsi domain.
> >> >> My linux vms which are basic template (No template) moved just fine and
> >> >> boot just fine.
> >> >> On the other hand my windows vms (Template) once moved they cant boot.
> >> >> Complaining that there is no bootable disk available.
> >> >> What is going on?
> >> >>
> >> >> oVirt 3.6.6
> >> >> Hosts Centos 6.6  x86_64
> >> >> iSCSI Domain on TrueNAS Attached via ovirt.
> >> >>
> >> >>
> >> >> --
> >> >> Fernando Fuentes
> >> >> ffuen...@txweather.org
> >> >> http://www.txweather.org
> >> >> ___
> >> >> Users mailing list
> >> >> Users@ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> >>
> >> >>
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Nir, 

I apologize I'll look for it ASAP. 

Regards, 

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Fri, Jul 1, 2016, at 03:22 PM, Nir Soffer wrote:
> Fernando,
> 
> These logs do not contain the libvirt xml.
> 
> I want to see the part that start like this:
> 
> Thread-17656::INFO::2016-07-01 23:17:33,845::vm::2032::virt.vm::(_run)
> vmId=`f66da2b0-0f71-490b-a57e-eceb9be9cade`:: encoding="utf-8"?>
> http://ovirt.org/vm/tune/1.0;>
> test-iscsi
> f66da2b0-0f71-490b-a57e-eceb9be9cade
> ...
> 
> The most important part is the devices sections showing the disks:
> 
> 
>  type="drive" unit="0"/>
>  dev="/rhev/data-center/f9374c0e-ae24-4bc1-a596-f61d5f05bc5f/5f35b5c0-17d7-4475-9125-e97f1cdb06f9/images/8f61b697-b3e4-4f63-8951-bdf9b6b39192/f409cc48-8248-4239-a4ea-66b0b1084416"/>
> 
> 8f61b697-b3e4-4f63-8951-bdf9b6b39192
> 
>  io="native" name="qemu" type="qcow2"/>
> 
> 
> Please try to find the logs (probably already rotated to vdsm.log.N.xz)
> containing the xml for this vm when running on nfs and iscsi.
> 
> Nir
> 
> On Fri, Jul 1, 2016 at 10:31 PM, Fernando Fuentes 
> wrote:
> > Nir.
> >
> > Thank you for your reply.
> >
> > Attached is the vdsm log of the hosts that power on the vm in this
> > example.
> >
> > VM name is Win7-QA5
> > vdsm_alpha.log was the host that started the VM when it got transfer to
> > the iscsi domain.
> > vdsm_zeta.log was the host that started the VM when it got transfer back
> > to the nfs domain.
> >
> > I included everything for trouble shooting purposes.
> >
> > Also here is the engine log that talks about it as well:
> > http://pastebin.com/3cHBNMcg
> >
> > Hope this helps.
> >
> > Regards,
> > --
> > Fernando Fuentes
> > ffuen...@txweather.org
> > http://www.txweather.org
> >
> > On Fri, Jul 1, 2016, at 01:58 PM, Nir Soffer wrote:
> >> On Fri, Jul 1, 2016 at 7:58 PM, Fernando Fuentes 
> >> wrote:
> >> > Pavel,
> >> >
> >> > Thanks for your reply, But thats not the problem
> >> > The disk is active and is set with to bootable. The problem presents it
> >> > self only if I move Windows VM DIsks.
> >> > All my Linux VM Disk's move across storage domains just fine.
> >> >
> >> > As a matter of fact I moved the disk back to the original nfs domain and
> >> > it started working.
> >> > Could this be a bug?
> >>
> >> Can you share the vdsm log showing startup of the vm when the disk is on
> >> on nfs storage domain (vm starts) and iscsi storage domain (vm fail)?
> >>
> >> The most interesting part in the logs is the libvirt xml describing the
> >> vm.
> >>
> >> Nir
> >>
> >> > Regards,
> >> >
> >> > --
> >> > Fernando Fuentes
> >> > ffuen...@txweather.org
> >> > http://www.txweather.org
> >> >
> >> > On Fri, Jul 1, 2016, at 11:33 AM, Pavel Gashev wrote:
> >> >> Fernando,
> >> >>
> >> >> One from VM disks have to have bootable flag.
> >> >> See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862
> >> >>
> >> >>
> >> >> On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando
> >> >> Fuentes" 
> >> >> wrote:
> >> >>
> >> >> Team,
> >> >>
> >> >> After I successfully copy my template from one storage to another I was
> >> >> able to move my VM disks from my nfs domain to my iscsi domain.
> >> >> My linux vms which are basic template (No template) moved just fine and
> >> >> boot just fine.
> >> >> On the other hand my windows vms (Template) once moved they cant boot.
> >> >> Complaining that there is no bootable disk available.
> >> >> What is going on?
> >> >>
> >> >> oVirt 3.6.6
> >> >> Hosts Centos 6.6  x86_64
> >> >> iSCSI Domain on TrueNAS Attached via ovirt.
> >> >>
> >> >>
> >> >> --
> >> >> Fernando Fuentes
> >> >> ffuen...@txweather.org
> >> >> http://www.txweather.org
> >> >> ___
> >> >> Users mailing list
> >> >> Users@ovirt.org
> >> >> http://lists.ovirt.org/mailman/listinfo/users
> >> >>
> >> >>
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Nir Soffer]

Fernando,

These logs do not contain the libvirt xml.

I want to see the part that start like this:

Thread-17656::INFO::2016-07-01 23:17:33,845::vm::2032::virt.vm::(_run)
vmId=`f66da2b0-0f71-490b-a57e-eceb9be9cade`::
http://ovirt.org/vm/tune/1.0;>
test-iscsi
f66da2b0-0f71-490b-a57e-eceb9be9cade
...

The most important part is the devices sections showing the disks:





8f61b697-b3e4-4f63-8951-bdf9b6b39192




Please try to find the logs (probably already rotated to vdsm.log.N.xz)
containing the xml for this vm when running on nfs and iscsi.

Nir

On Fri, Jul 1, 2016 at 10:31 PM, Fernando Fuentes  wrote:
> Nir.
>
> Thank you for your reply.
>
> Attached is the vdsm log of the hosts that power on the vm in this
> example.
>
> VM name is Win7-QA5
> vdsm_alpha.log was the host that started the VM when it got transfer to
> the iscsi domain.
> vdsm_zeta.log was the host that started the VM when it got transfer back
> to the nfs domain.
>
> I included everything for trouble shooting purposes.
>
> Also here is the engine log that talks about it as well:
> http://pastebin.com/3cHBNMcg
>
> Hope this helps.
>
> Regards,
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
> On Fri, Jul 1, 2016, at 01:58 PM, Nir Soffer wrote:
>> On Fri, Jul 1, 2016 at 7:58 PM, Fernando Fuentes 
>> wrote:
>> > Pavel,
>> >
>> > Thanks for your reply, But thats not the problem
>> > The disk is active and is set with to bootable. The problem presents it
>> > self only if I move Windows VM DIsks.
>> > All my Linux VM Disk's move across storage domains just fine.
>> >
>> > As a matter of fact I moved the disk back to the original nfs domain and
>> > it started working.
>> > Could this be a bug?
>>
>> Can you share the vdsm log showing startup of the vm when the disk is on
>> on nfs storage domain (vm starts) and iscsi storage domain (vm fail)?
>>
>> The most interesting part in the logs is the libvirt xml describing the
>> vm.
>>
>> Nir
>>
>> > Regards,
>> >
>> > --
>> > Fernando Fuentes
>> > ffuen...@txweather.org
>> > http://www.txweather.org
>> >
>> > On Fri, Jul 1, 2016, at 11:33 AM, Pavel Gashev wrote:
>> >> Fernando,
>> >>
>> >> One from VM disks have to have bootable flag.
>> >> See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862
>> >>
>> >>
>> >> On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando
>> >> Fuentes" 
>> >> wrote:
>> >>
>> >> Team,
>> >>
>> >> After I successfully copy my template from one storage to another I was
>> >> able to move my VM disks from my nfs domain to my iscsi domain.
>> >> My linux vms which are basic template (No template) moved just fine and
>> >> boot just fine.
>> >> On the other hand my windows vms (Template) once moved they cant boot.
>> >> Complaining that there is no bootable disk available.
>> >> What is going on?
>> >>
>> >> oVirt 3.6.6
>> >> Hosts Centos 6.6  x86_64
>> >> iSCSI Domain on TrueNAS Attached via ovirt.
>> >>
>> >>
>> >> --
>> >> Fernando Fuentes
>> >> ffuen...@txweather.org
>> >> http://www.txweather.org
>> >> ___
>> >> Users mailing list
>> >> Users@ovirt.org
>> >> http://lists.ovirt.org/mailman/listinfo/users
>> >>
>> >>
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Nir Soffer]

On Fri, Jul 1, 2016 at 7:58 PM, Fernando Fuentes  wrote:
> Pavel,
>
> Thanks for your reply, But thats not the problem
> The disk is active and is set with to bootable. The problem presents it
> self only if I move Windows VM DIsks.
> All my Linux VM Disk's move across storage domains just fine.
>
> As a matter of fact I moved the disk back to the original nfs domain and
> it started working.
> Could this be a bug?

Can you share the vdsm log showing startup of the vm when the disk is on
on nfs storage domain (vm starts) and iscsi storage domain (vm fail)?

The most interesting part in the logs is the libvirt xml describing the vm.

Nir

> Regards,
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
> On Fri, Jul 1, 2016, at 11:33 AM, Pavel Gashev wrote:
>> Fernando,
>>
>> One from VM disks have to have bootable flag.
>> See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862
>>
>>
>> On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando
>> Fuentes" 
>> wrote:
>>
>> Team,
>>
>> After I successfully copy my template from one storage to another I was
>> able to move my VM disks from my nfs domain to my iscsi domain.
>> My linux vms which are basic template (No template) moved just fine and
>> boot just fine.
>> On the other hand my windows vms (Template) once moved they cant boot.
>> Complaining that there is no bootable disk available.
>> What is going on?
>>
>> oVirt 3.6.6
>> Hosts Centos 6.6  x86_64
>> iSCSI Domain on TrueNAS Attached via ovirt.
>>
>>
>> --
>> Fernando Fuentes
>> ffuen...@txweather.org
>> http://www.txweather.org
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Fernando Fuentes]

Pavel,

Thanks for your reply, But thats not the problem
The disk is active and is set with to bootable. The problem presents it
self only if I move Windows VM DIsks.
All my Linux VM Disk's move across storage domains just fine.

As a matter of fact I moved the disk back to the original nfs domain and
it started working.
Could this be a bug?

Regards,

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Fri, Jul 1, 2016, at 11:33 AM, Pavel Gashev wrote:
> Fernando,
> 
> One from VM disks have to have bootable flag.
> See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862
> 
> 
> On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando
> Fuentes" 
> wrote:
> 
> Team,
> 
> After I successfully copy my template from one storage to another I was
> able to move my VM disks from my nfs domain to my iscsi domain.
> My linux vms which are basic template (No template) moved just fine and
> boot just fine.
> On the other hand my windows vms (Template) once moved they cant boot.
> Complaining that there is no bootable disk available.
> What is going on?
> 
> oVirt 3.6.6
> Hosts Centos 6.6  x86_64
> iSCSI Domain on TrueNAS Attached via ovirt.
> 
> 
> -- 
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] disk not bootable

[Pavel Gashev]

Fernando,

One from VM disks have to have bootable flag.
See http://www.ovirt.org/images/wiki/Add_Virtual_Disk.png?1454370862


On 01/07/16 19:09, "users-boun...@ovirt.org on behalf of Fernando Fuentes" 
 wrote:

Team,

After I successfully copy my template from one storage to another I was
able to move my VM disks from my nfs domain to my iscsi domain.
My linux vms which are basic template (No template) moved just fine and
boot just fine.
On the other hand my windows vms (Template) once moved they cant boot.
Complaining that there is no bootable disk available.
What is going on?

oVirt 3.6.6
Hosts Centos 6.6  x86_64
iSCSI Domain on TrueNAS Attached via ovirt.


-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users