MirageOS 4.0 – Self-managed internet infrastructure with unikernels
1–10 of 38 posts
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#2I am fascinated by Unikernels. But how do they deal with things that need to fork or run multiple processes? Aren't they restricted to single processes?
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#3This project mentions it’s based on the Xen hypervisor and uses EC2 as an example for running it, but haven’t AWS now moved to their own KVM based hypervisor? Would this still work?
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#4I am fascinated by Unikernels. But how do they deal with things that need to fork or run multiple processes? Aren't they restricted to single processes?
Yes they are, but you don't need to fork for a lot of workloads.
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#5This project mentions it’s based on the Xen hypervisor and uses EC2 as an example for running it, but haven’t AWS now moved to their own KVM based hypervisor? Would this still work?
You can still choose Xen-based instances in EC2.
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#6This project mentions it’s based on the Xen hypervisor and uses EC2 as an example for running it, but haven’t AWS now moved to their own KVM based hypervisor? Would this still work?
You can still choose Xen-based instances in EC2.
Ahh ok. I imagine you would lose all the nice Nitro stuff though like enhanced networking etc which is a bummer.
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#7This name is associated with a lot of nostalgia for me, as it is the same name as the shell launcher for Texas Instruments' TI-83/84 graphing calculators.
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#8I am fascinated by Unikernels. But how do they deal with things that need to fork or run multiple processes? Aren't they restricted to single processes?
The new version of OCaml got multiprocessor support recently.
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#9This name is associated with a lot of nostalgia for me, as it is the same name as the shell launcher for Texas Instruments' TI-83/84 graphing calculators.
I was wondering why the name sounded familiar. For a second I thought this was referring to ReactOS, which is something else completely different.
Re: MirageOS 4.0 – Self-managed internet infrastructure with unikernels
#10Earlier quoted context omitted.
You can still choose Xen-based instances in EC2.
Ahh ok. I imagine you would lose all the nice Nitro stuff though like enhanced networking etc which is a bummer.
There is Xen-on-Nitro, which AWS developed to continue to support customers using Xen to run on EC2 instances featuring Nitro: https://perspectives.mvdirona.com/2021/11/xen-on-nitro-aws-n...