Re: [ovirt-users] Failed to open grubx64.efi

2017-12-12 Thread Yuval Turgeman
Glad to hear, thanks for the update ! :) On Tue, Dec 12, 2017 at 1:20 PM, Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com> wrote: > On Thu, Nov 23, 2017 at 10:41 AM, Luca 'remix_tj' Lorenzetto > wrote: > > > > On Wed, Nov 22, 2017 at 11:05 AM, Yuval Turgeman

Re: [ovirt-users] Failed to open grubx64.efi

2017-12-12 Thread Luca 'remix_tj' Lorenzetto
On Thu, Nov 23, 2017 at 10:41 AM, Luca 'remix_tj' Lorenzetto wrote: > > On Wed, Nov 22, 2017 at 11:05 AM, Yuval Turgeman wrote: > [cut] > > You can access boot_params under /sys/kernel/boot_params/data, so if you > > want > > to understand what's

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-23 Thread Luca 'remix_tj' Lorenzetto
On Wed, Nov 22, 2017 at 11:05 AM, Yuval Turgeman wrote: [cut] > You can access boot_params under /sys/kernel/boot_params/data, so if you > want > to understand what's going on with your machine, you can try to use strings > to > see if it's enabled while running anaconda - on

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-22 Thread Yuval Turgeman
Hi, I checked a little more, anaconda uses blivet to detect if the machine is EFI for its boot partition requirements, and blivet checks if /sys/firmware/efi exists [1]. The kernel registers /sys/firmware/efi only if EFI_BOOT is enabled [2], and this is set in on setup, when the kernel searches

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-21 Thread Yuval Turgeman
Boot partition reqs should be handled the same on both ovirt node and centos (or rhel) and you having to add this manually on rhel can give us a hint that this is a bug in anaconda (doesnt detect efi?). In other words, if you need to add this to rhel you'd need to add it to ovirt node and

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-21 Thread Luca 'remix_tj' Lorenzetto
On Tue, Nov 21, 2017 at 4:54 PM, Yuval Turgeman wrote: > Hi, > > I tried to recreate this without success, i'll try with different hw > tomorrow. > The thing is, autopart with thinp doesn't mean that everything is lvm-thin - > /boot should be a regular (primary) partition (for

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-21 Thread Yuval Turgeman
Hi, I tried to recreate this without success, i'll try with different hw tomorrow. The thing is, autopart with thinp doesn't mean that everything is lvm-thin - /boot should be a regular (primary) partition (for details you can check anaconda's ovirt install class) This could be a bug in anaconda

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-19 Thread Julio Cesar Bustamante
Hi Luca. But do you have installed Ovirt without UEFI in production environments?. UEFI , is it necessary in production environments?. 2017-11-16 14:02 GMT-05:00 Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com>: > Hello Julio, > > On Thu, Nov 16, 2017 at 6:41 PM, Julio Cesar Bustamante

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-19 Thread Julio Cesar Bustamante
Hi Luca and Magnus, I downloaded and installed ovirt-node-ng-installer-ovirt-4.1-2017110820, in blade HS 22, without set legacy mode and this installation was successed. Thanks a lot for you help 2017-11-17 8:48 GMT-05:00 Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com>: > On Fri, Nov

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-19 Thread Julio Cesar Bustamante
Hi Luca, I tried to install Ovirt node with legacy mode but It didn't work. I dont know where I'm mistaking. 2017-11-16 17:12 GMT-05:00 Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com>: > > > Il 16 nov 2017 9:36 PM, "Julio Cesar Bustamante" < > julio.cesar.bustama...@gmail.com> ha

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-17 Thread Luca 'remix_tj' Lorenzetto
On Fri, Nov 17, 2017 at 2:31 PM, Julio Cesar Bustamante wrote: > Hi Luca > > I didn't find in my blade hs22 IBM that option boot. > > Looking around i've seen that there is an Alt+B sequence for booting in legacy mode. Maybe in the system setup there is an

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-17 Thread Luca 'remix_tj' Lorenzetto
On Fri, Nov 17, 2017 at 3:24 AM, Julio Cesar Bustamante wrote: > Hi Luca, > > I tried to install Ovirt node with legacy mode but It didn't work. I dont > know where I'm mistaking. Are you also booting in legacy mode? I don't use UEFI at all. Luca -- "E'

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-16 Thread Magnus Isaksson
Hello I got the same thing. Tho, this post at comment 6 worked perfekt. https://bugzilla.redhat.com/show_bug.cgi?id=1496762 //Magnus On 16 November 2017 23:12:26 CET, Luca 'remix_tj' Lorenzetto wrote: >Il 16 nov 2017 9:36 PM, "Julio Cesar Bustamante" <

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-16 Thread Luca 'remix_tj' Lorenzetto
Il 16 nov 2017 9:36 PM, "Julio Cesar Bustamante" < julio.cesar.bustama...@gmail.com> ha scritto: Hi Luca. But do you have installed Ovirt without UEFI in production environments?. UEFI , is it necessary in production environments?. Hi Julio, No, at all. We have a setup of 7 nodes hp bl460

Re: [ovirt-users] Failed to open grubx64.efi

2017-11-16 Thread Luca 'remix_tj' Lorenzetto
Hello Julio, On Thu, Nov 16, 2017 at 6:41 PM, Julio Cesar Bustamante wrote: > Hi there, > > I have installed Ovirt Host in a HS22 Blade Ibm, but I have this bug. > > Failed to open \efi\centos\grubx64.efi not found > Falied to load image \EFI\centos\grubx64.efi