Hello, Sorry, I should’ve been more specific! That is what I am doing. Would it be more help if I gave you the script I am running and my grub.cfg...When I reboot my system and pick that partition in BIOS, then it kernel panics.
I’ve been trying to get it to work for some time now but I am stumped. Thanks for your help! > On Dec 3, 2019, at 7:37 AM, Geraldo Netto <[email protected]> wrote: > > > Hello! > > > I might be saying some non sense > But maybe we don't have all the bare minimum drivers to boot it up from bare > metal > Maybe one strategy would be to DD the image to a disk and try to boot from it > before trying grub configuration? > > > Keep Rocking, > Geraldo Netto > > Em ter, 3 de dez de 2019 13:25, Matthew Weekley <[email protected]> > escreveu: >> After further experimentation I still haven’t had any luck. When trying to >> boot it via USB, it appears I’m going into a kernel panic... >> >> I can not tell if I am missing parameters in my grub.cfg or not... Does >> anyone have any thoughts about what could be causing that? >> >> What I am doing is making the iso, putting it on the usb (kind of cheating >> as I just say the usb is another partition, sdb) and then boot that >> partition from grub menu. >> >> Any help is much appreciated! >> >>>> On Nov 26, 2019, at 1:56 PM, Matthew Weekley <[email protected]> wrote: >>>> >>> >>> My current grub.cfg: >>> >>> menuentry “OSv”{ >>> linux /boot/service/release.x64/vmlinuz.bin >>> boot >>> } >>> >>> When I go to boot from within grub, I get a critical error :( >>> >>> Any thoughts why?? >>> >>>>> On Nov 26, 2019, at 10:06 AM, Matthew Weekley <[email protected]> >>>>> wrote: >>>>> >>>> >>>> Corrected that but that lead to a critical error when trying to boot it. >>>> >>>> Do I need to specify any further files below the vmlinuz file? >>>> >>>>>> On Nov 26, 2019, at 9:56 AM, Pekka Enberg <[email protected]> wrote: >>>>>> >>>>> >>>>>> On Tue, Nov 26, 2019 at 4:50 PM Matthew Weekley <[email protected]> >>>>>> wrote: >>>>> >>>>>> My current grub is >>>>>> >>>>>> menuentry “OSv” { >>>>>> multiboot /boots/service/release.x64/vmlinuz.bin >>>>> >>>>> ^^^ this needs to "linux", instead of "multiboot". >>>>> >>>>>> boot >>>>>> } >>>>>> >>>>>> This returns “no multiboot header found. You need to load the kernel >>>>>> first” >>>>> >>>>> Yes, because there's no Multiboot support in OSv anymore. The "vmlinuz" >>>>> file follows the Linux boot protocol described here: >>>>> >>>>> https://www.kernel.org/doc/Documentation/x86/boot.txt >>>>> >>>>> - Pekka >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "OSv Development" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/osv-dev/jEMfRZ0GtSc/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/osv-dev/209F20AC-D16A-4BC3-9960-7BE14BA0CB03%40comcast.net. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OSv Development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/osv-dev/88E15BA6-68EB-4108-9BFD-18262350E918%40comcast.net. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/F099FF30-DB87-4360-AA79-E68DA3C107BB%40comcast.net.
