-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
main/xen: build EFI binaries #1513
Conversation
@kaniini Here's the second one. It seems like it makes most sense to place them in /boot and thus in the xen-hypervisor package, this is like Debian I think. But if you believe that is a more intruding change before the release, maybe I can redo with a xen-efi package instead, and perhaps in the original /usr/lib64/efi location? |
I'm not sure it is appropriate to install them to /boot, shouldn't it be installed to a standard EFI location? |
Yes, you are right. Correct me if I'm wrong, but I don't think we have anything like that in Alpine yet? Packages with EFI binaries that I've looked at now seem to store them in /usr somewhere, like:
Do you think it would be viable to keep them in /usr/lib64/efi for now, but perhaps in the xen-hypervisor package? It would be nice to get the binaries in place for 3.6, and then maybe pursue a general "EFI boot support" feature? |
Btw, looks like Travis terminates the job due to exceeding the log limit of 4MB... |
@radhus yes that is fine. i am still working out the details on formal EFI support in alpine as it's kind of complicated. so lets use /usr/lib/efi for now. |
@kaniini Ok, cool, I'll try to push that asap. If you want help with the EFI support, I can help out with testing and development, just let me know if there's something I can work on. I will be running at least some boxes now with Xen that I will boot from EFI. |
Alright, finally, now it's in /usr/lib64/efi If this is accepted, is there any chance this might get backported to 3.6 stable? :) |
That’s wrong, we don’t use |
Ah yes, sorry. And I seem to have missed committing the CARCH check for x86_64, sorry. Wait just a minute :) |
New binutils 2.28-r2 provides the x86_64-pep target which makes Xen build its EFI bootloader. The EFI binaries are placed in the xen-hypervisor package, which stores them under /usr/lib/efi. To use and configure, see https://wiki.xenproject.org/wiki/Xen_EFI
@jirutka fixed now :) |
Let me know if you want to do it any other way, I'm running one physical box with this now and have it verified working with Virtualbox UEFI VM's (although in both cases, you need to configure bootloader (like gummiboot) yourself of course). |
Btw, looks like /usr/lib64/efi/xen-4.8.1.efi is created in the xen packages now, both in 4.8.x and 4.9. Not really what we want I guess. @jirutka do you have any pointers on how to proceed with this? I can of course rebase it if it's fine as it is. |
New binutils 2.28-r2 provides the x86_64-pep target which makes Xen
build its EFI bootloader.
The EFI binaries are placed in /boot and provided by xen-hypervisor:
/boot/xen-4.8.1.efi
/boot/xen-4.8.efi
/boot/xen-4.efi
/boot/xen.efi