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 wrote:
>
>
> Corrected that but that lead to a critical error when
I built OSv on Fedora 31, worked just fine I had to do this tiny thing:
dorlaor@dorpc osv]$ git diff
diff --git a/scripts/setup.py b/scripts/setup.py
index ce02b5d8..7412bb51 100755
--- a/scripts/setup.py
+++ b/scripts/setup.py
@@ -99,7 +99,15 @@ class Fedora(object):
ec2_post_install =
For example, there’re lots of program that uses subprocess in python or
exec.cmd in golang. Those programs have to be ported to rewrite with the
api bindings.
On Tue, Nov 26, 2019 at 9:06 AM Nadav Har'El wrote:
>
> On Tue, Nov 26, 2019 at 12:44 AM Waldek Kozaczuk
> wrote:
>
>> Sometimes it
On Tue, Nov 26, 2019 at 12:44 AM Waldek Kozaczuk
wrote:
> Sometimes it might be more useful to think of unikernels as highly
> isolated processes instead of microVMs with a specialised guest OS. See
> Nabla processes -
> https://acmsocc.github.io/2018/slides/socc18-slides-williams.pdf.
>
> So
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 wrote:
>
>
>> On Tue, Nov 26, 2019 at 4:50 PM Matthew Weekley
>> wrote:
>
>> My current grub is
>>
>>
Imagine the potential for serverless given OSv supports runscript boot option.
If we can replace the runscript file for every reboot, OSv can execute
different app with different parameters. Even better reboot and wait until the
runscript file changes or some other touch mechanism. But for that
On Tue, Nov 26, 2019 at 4:50 PM Matthew Weekley
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
My current grub is
menuentry “OSv” {
multiboot /boots/service/release.x64/vmlinuz.bin
boot
}
This returns “no multiboot header found. You need to load the kernel first”
Also, I don’t need any networking capabilities. Just trying to run a simple
program and show it can boot bare metal :)
On Tue, Nov 26, 2019 at 3:35 PM Waldek Kozaczuk
wrote:
> The review and discussion around proper poweroff/reboot sequence on
> microvm/firecracker with Nadav (see other email) inspired me to check
> another thing - remove '-no-reboot` from QEMU parameter list. This should
> then trigger reboot
On Tue, Nov 26, 2019 at 2:51 AM Matthew Weekley
wrote:
> I am looking to boot the kernel I generated from the build script.
>
> How would one recommend doing so using grub? I have noticed that OSv
> doesn't support multiboot, or so it seems to me. I am not a grub expert by
> any means so that's
On Tue, Nov 26, 2019 at 4:14 PM wrote:
> I've never used vmlinuz to boot, but I see files that pertain to vmlinuz.
> Any suggestions for how to boot bare metal using vmlinuz? Currently looking
> for solutions now. Thanks!
>
Use GRUB, for example. See the previous links to "grub-mkrescue" how to
I’ve never used vmlinuz to boot. Any suggestions?? Currently looking but maybe
you can provide a faster solution than I’ll be able to research. Thanks!
> On Nov 26, 2019, at 8:51 AM, Waldek Kozaczuk wrote:
>
> Pekka,
>
> Thanks for finding this. From what I remember I found multiboot not
I've never used vmlinuz to boot, but I see files that pertain to vmlinuz.
Any suggestions for how to boot bare metal using vmlinuz? Currently looking
for solutions now. Thanks!
On Tuesday, November 26, 2019 at 8:50:59 AM UTC-5, Waldek Kozaczuk wrote:
>
> Pekka,
>
> Thanks for finding this. From
It seems fine on Fedora 30 (I seem to remember there were some specific
modules that had problems because of the Boost mess, but not the tests). I
didn't move to Fedora 31 yet. (I should).
On Tue, Nov 26, 2019 at 3:39 PM Waldek Kozaczuk
wrote:
> Has anybody tried to build and run OSv on any of
Pekka,
Thanks for finding this. From what I remember I found multiboot not that widely
supported comparing to vmlinuz.
Please note that OSv vmlinuz is not compressed so we simply wrap loader.elf
I really need to revise the boot wikis
Sent from my iPhone
> On Nov 26, 2019, at 08:46, Pekka
On Tue, Nov 26, 2019 at 3:30 PM wrote:
> I just looked and I do not have any of those files anywhere on my system
> (did the find command).
>
Aah, my tree was not up-to-date. Looks like Waldek removed Multiboot
support:
commit 2a34f9f2acb582b8351c3ca7cac0ac2ad18dfe2a
Author: Waldemar Kozaczuk
Has anybody tried to build and run OSv on any of those distributions? I
think per #1040 the code should build and all unit tests should pass on
Fedora 30 (I tested it on my other old laptop with that system).
Regards,
Waldek
--
You received this message because you are subscribed to the
The review and discussion around proper poweroff/reboot sequence on
microvm/firecracker with Nadav (see other email) inspired me to check
another thing - remove '-no-reboot` from QEMU parameter list. This should
then trigger reboot rather than poweroff, right? And then constantly
re-execute
I just looked and I do not have any of those files anywhere on my system
(did the find command).
On Tuesday, November 26, 2019 at 1:30:26 AM UTC-5, Pekka Enberg wrote:
>
> Hi Matthew,
>
> On Tue, Nov 26, 2019 at 2:51 AM Matthew Weekley > wrote:
>
>> How would one recommend doing so using grub?
Hi Waldek,
On Tue, Nov 26, 2019 at 12:44 AM Waldek Kozaczuk
wrote:
> Sometimes it might be more useful to think of unikernels as highly
> isolated processes instead of microVMs with a specialised guest OS. See
> Nabla processes -
>
Hi,
On Mon, Nov 25, 2019 at 6:59 PM Waldek Kozaczuk
wrote:
> I am not golang expert either. Maybe others, original authors of capstan
> on the list can chime in. I will look into myself. If there is a lot of
> work we might just explicitly stick with v1. Either way, it would be good
> to
21 matches
Mail list logo
