-
Notifications
You must be signed in to change notification settings - Fork 136
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
mfsbsd img file not working in UEFI mode #110
Comments
This is probably not the correct way to boot mfsBSD via iPXE. You should run because the Anyway, loader.efi is not a kernel. If you want to use it, you probably should run and then loader.efi would fetch and load the kernel and mfsroot. But only with NFS. |
@victor-sudakov Thanks for correcting me. |
@Gitrrrr look The way it should work (though it does not):
loader.efi will be fetched to the host by the PXE boot, and should do the rest of the job. However in my case, it loads the kernel, tries to load mfsroot and then freezes, and then reboots in a minute or so. Or maybe it's not loader.efi that freezes, but "/mfsroot" and several seconds of rotating "/" is the last thing I can see. |
Can you please tell me how to enable some debug output to see what's happening after the "/mfsroot" message? |
I know it is old issue, but if someone find it useful, I have successfully booted |
@tuxjz could you be able to share the working config? |
Can you please elaborate on what part of config you are interested in? |
Thanks @tuxjz . Finally, I managed to get it to work. I am not using ipxe. I was totally stuck on it. My PXE server is based on debian. I was using dnsmasq for DHCP and TFTP. My issue was I couldn't find a way to pass the dhcp-option |
mfsbsd boot is not working in UEFI mode. it is working fine for me in legacy mode using memdisk.
ipxe file
kernel http://$server/cobbler/ks_mirror/$distro/boot/loader.efi
initrd http://$server/cobbler/ks_mirror/$distro/boot/mfsbsd-amd64.img
boot
Note i tried this (#100) but not worked for me.
The text was updated successfully, but these errors were encountered: