Re: Centos7 uefi boot problem with bhyve after update

2018-05-04 Thread Michael Reifenberger 


Zitat von "Patrick M. Hausen" :


Hi all,


Am 04.05.2018 um 15:41 schrieb Peter Grehan :

Hi Mike,


the fault here could be that of bootrom not reading the files it should


That is exactly the issue. The current UEFI code does not save  
non-volatile variables to persistent storage. Guest o/s's are  
increasingly writing their efi loaders to non-standard locations  
and using nv vars to direct UEFI to boot from these locations.


I recommend installing rEFInd to the default location /EFI/BOOT/bootx64.efi.
It will call the Centos boot loader automatically if this is the  
only other one installed.


http://www.rodsbooks.com/refind/



Thanks for the hint!
I installed rEFInd into /boot/efi/EFI/BOOT
This workaround works.

greetings
---
Mike

Gruß
---
Michael Reifenberger

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Centos7 uefi boot problem with bhyve after update

2018-05-04 Thread Patrick M. Hausen 
Hi all,

> Am 04.05.2018 um 15:41 schrieb Peter Grehan :
> 
> Hi Mike,
> 
>> the fault here could be that of bootrom not reading the files it should
> 
> That is exactly the issue. The current UEFI code does not save non-volatile 
> variables to persistent storage. Guest o/s's are increasingly writing their 
> efi loaders to non-standard locations and using nv vars to direct UEFI to 
> boot from these locations.

I recommend installing rEFInd to the default location /EFI/BOOT/bootx64.efi.
It will call the Centos boot loader automatically if this is the only other one 
installed.

http://www.rodsbooks.com/refind/

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

[Bug 227956] [bhyve] [feature request] add an init script in base

2018-05-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227956

Rodney W. Grimes  changed:

   What|Removed |Added

Version|11.1-STABLE |CURRENT

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

[Bug 227956] [bhyve] [feature request] add an init script in base

2018-05-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227956

Rodney W. Grimes  changed:

   What|Removed |Added

 CC||rgri...@freebsd.org

--- Comment #1 from Rodney W. Grimes  ---
There are several ports to manage bhyve vm's with, such as vm-bhyve, bhyve-rc,
and other third party software I can not seem to locate right now, chyves?

At this time it would not be advantages to add this type of functionality to
base.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Centos7 uefi boot problem with bhyve after update

2018-05-04 Thread Peter Grehan 

Hi Mike,


the fault here could be that of bootrom not reading the files it should


 That is exactly the issue. The current UEFI code does not save 
non-volatile variables to persistent storage. Guest o/s's are 
increasingly writing their efi loaders to non-standard locations and 
using nv vars to direct UEFI to boot from these locations.


 I'm (very slowly) merging a fix from Leon for this in both UEFI and 
bhyve which directs nv var writes to a file on the host, providing a 
persistent store.


later,

Peter.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

[Bug 227956] [bhyve] [feature request] add an init script in base

2018-05-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227956

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|virtualizat...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Centos7 uefi boot problem with bhyve after update

2018-05-04 Thread Mike Gerdts 
On Fri, May 4, 2018 at 7:26 AM, Michael Reifenberger 
wrote:

> The kernel version shouldn't matter that much because the error occures
> before the kernel gets loaded.
> It's after /EFI/BOOT/BOOTX64.EFI got loaded and before
> /EFI/centos/grubx64.efi gets loaded
> because of not beeing found...
>

On SmartOS I've found that fresh installations of CentOS 7 put all of the
required files to actually boot the OS in the /EFI/centos directory leaving
the /EFI/BOOT directory mostly empty.  The image at https://ibb.co/jFwDES
matches this symptom.  This can be fixed (hacked around) via the EFI shell.

The following is pieced together from scrollback (that was kinda wonky due
to size issues) from a serial console.

Shell> FS0:
FS0:\> cd efi
FS0:\efi\> cd BOOT
FS0:\efi\BOOT\> dir
Directory of: FS0:\efi\BOOT\
05/03/2018  19:29  4,096  .
05/03/2018  19:29  4,096  ..
08/31/2017  21:30   1,296,176  BOOTX64.EFI
08/31/2017  21:30  79,048  fbx64.efi
  2 File(s)   1,375,224 bytes
  2 Dir(s)
FS0:\efi\BOOT\> cd ..\centos
FS0:\efi\centos\> dir
Directory of: FS0:\efi\centos\
05/03/2018  19:27  4,096  .
05/03/2018  19:27  4,096  ..
05/03/2018  19:29  4,096  fonts
08/31/2017  21:30   1,297,120  shimx64-centos.efi
08/17/2017  18:00   1,052,032  grubx64.efi
08/31/2017  21:30 134  BOOT.CSV
08/31/2017  21:30 134  BOOTX64.CSV
08/31/2017  21:30   1,262,816  mmx64.efi
08/31/2017  21:30   1,296,176  shim.efi
05/03/2018  19:33   1,024  grubenv
08/31/2017  21:30   1,296,176  shimx64.efi
05/03/2018  19:33   4,231  grub.cfg
  9 File(s)   6,209,843 bytes
  3 Dir(s)
FS0:\efi\centos\> cp -r * ..\boot
Copying FS0:\EFI\centos\fonts -> FS0:\EFI\BOOT\fonts
...
Copying FS0:\EFI\centos\grub.cfg -> FS0:\EFI\BOOT\grub.cfg
- [ok]
FS0:\efi\centos\> reset


I've not curled up with the EFI spec for a while and forget how it is
supposed to choose which directory to read the various files from.  That
is, the fault here could be that of bootrom not reading the files it should
or the guest OS not putting the right thing in \EFI\BOOT to get it to look
in \EFI\centos.

Mike
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Centos7 uefi boot problem with bhyve after update

2018-05-04 Thread Michael Reifenberger 


Zitat von Jason Tubnor :


On 2 May 2018 at 19:58, Michael Reifenberger  wrote:



Hi,
Im running a Centos7 bhyve VM under FreeBSD-11 (latest stable).
The VM boots using UEFI: uefi-edk2-bhyve-0.1
Centos was installed and ist booting fine: CentOS Linux release 7.3.1611
(Core)



What Kernel version are you running here?  Have you tried
uefi-edk2-bhyve-20180318 ?


Centos (the older working one):
Linux nw3 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC  
2017 x86_64 x86_64 x86_64 GNU/Linux

It was installed Sep.2016 using CentOS-7-x86_64-LiveKDE.iso

The newer one (the non working), I dont know currently, but should be  
a 3.10.* kernel as well.


uefi-edk2-bhyve-20180318 ist the latest one?
Yes. I used this version to get the Screenshot.





BTW:
A new installation of a recent Centos fails after the installation/reboot
with the same error.
Other Linux distros (Ubuntu) seem to be affectet too...



Can you define the version of Ubuntu that you are testing with and the
kernel that it is running?  Ubuntu 17.10 Server stock works fine with the
currently supplied UEFI shims, but there are known issues with 18.04 with
fixes in the pipeline.

Cheers,

Jason.


I used:
ubuntu-16.04.3-desktop-amd64.iso
ubuntu-16.04.3-server-amd64.iso
and, I think,
manjaro-xfce-17.1.1-stable-x86_64.iso

Kernelversion I don't know.

The kernel version shouldn't matter that much because the error  
occures before the kernel gets loaded.
It's after /EFI/BOOT/BOOTX64.EFI got loaded and before  
/EFI/centos/grubx64.efi gets loaded

because of not beeing found...

greetings
---
Mike


Gruß
---
Michael Reifenberger

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"