unikraft VS QEMU

You should also probably check out Unikraft (https://unikraft.org) , supports many languages/apps, x86/ARM64 and QEMU/Firecracker. Is also able to run an ELF built under Linux as a unikernel (see https://unikraft.org/guides/bincompat). Discord is at https://unikraft.org/discord .

>"For performance-oriented UDP-based apps, much of the OS networking stack is useless:

the app could simply use the driver API, much like DPDK-style applications already do.

There is currently no way to easily remove just the network stack but not the entire network sub-system from standard OSes."

This page is a great read for any current or future OS developer...

Related:

"Unikraft is a fast, secure and open-source Unikernel Development Kit":

https://unikraft.org/

"Unikraft is an automated system for building specialized OSes known as unikernels."

https://github.com/unikraft/unikraft

unikernel is not the same microkernel.

I've found these after some quick googling:

https://unikraft.org/

Check out https://github.com/unikraft/unikraft

Wow, just now seeing this topic. I work for a cloud company hosted in AWS. We started out, Netflix/Spotify style microservices. We were all on ec2 images generate by packer (and later with AWS Image Factory). When Docker hit, we kicked the tires but never did anything with it beyond using it for running unit tests, and later, infrastructure tests. 5 years ago, during a hackathon, our little group began experimenting with Unikernels, or library operating systems. Interestingly enough, these Unikernels were all stripped down BSD kernels. OSv is FreeBSD based, and Rumprun is NetBSD based. Services running in EC2 on Unikernels would spin up and start sending and receiving traffic before the AWS EC2 healthchecks completed. They are blazing fast! Only problem in 2017, was the tooling. It would have taken too much effort to use Unikernals with our infrastructure. As soon as they start making Unikernels that can run Java bytecode like native code, the fate of containerization will be sealed, IMO. We could get basic JVM webservers running on OSv, but not Cassandra, not Kafka, not yet. OSv now runs on Firecracker, but I have not tried it out, yet. Some links if you are interested: OSv: https://osv.io Rumprun: https://github.com/rumpkernel/rumprun We used this tooling during the Hackathon, but doesn't look like it has been touched in 3 years: https://github.com/solo-io/unik Unikraft Unikernel Dev kit: https://unikraft.org/ And don't forget Firecracker running in Kubernetes https://www.weave.works/oss/firekube/ And of course, being a FreeBSD subreddit, let's not forget FreeBSD on Firecracker https://www.daemonology.net/blog/2022-10-18-FreeBSD-Firecracker.html

and Unikraft

My most-wanted QEMU feature: https://github.com/qemu/qemu/commit/a2260983c6553

Using `gic-version=3` on macOS you can now use more than 8 cores on ARM chips.

A better solution is just to write a plain ass shell script that tests if various C snippets compile.

https://github.com/oilshell/oil/blob/master/configure

https://github.com/oilshell/oil/blob/master/build/detect-pwe...

Not an unholy mix of m4, shell, and C, all in the same file.

---

These are the same style as a the configure scripts that Fabrice Bellard wrote for tcc and QEMU.

They are plain ass shell scripts, because he actually understands the code he writes.

https://github.com/qemu/qemu/blob/master/configure

https://github.com/TinyCC/tinycc/blob/mob/configure

OCaml’s configure script is also “normal”.

You don’t have to copy and paste thousands of lines of GNU stuff that you don’t understand.

(copy of lobste.rs comment)

Related:

A fast Pascal (Delphi) WebAssembly interpreter:

https://github.com/marat1961/wasm

WASM-4:

https://github.com/aduros/wasm4

Curated list of awesome things regarding WebAssembly (wasm) ecosystem:

https://github.com/mbasso/awesome-wasm

Also, it would be nice if there was a WASM (soft) CPU for QEMU, which (if it existed!) would go here:

https://github.com/qemu/qemu/tree/master/target

> architectural registers are always updated

In tiny code, the guest registers (global TCG variables) are stored in the host's registers until you either call an helper which can access the CPU state or you return (`git grep la_global_sync`). This is the reason why QEMU is not so terribly slow.

But after a check, this also happens when you access the guest memory address space! https://github.com/qemu/qemu/blob/master/include/tcg/tcg-opc... (TCG_OPF_SIDE_EFFECTS is what matters)

But still, in the end, it's the same problem. What QEMU does, can be done in LLVM too. You could probably be more efficient in LLVM by using the exception handling mechanism (invoke and friends) to only serialize back to memory when there's an actual exception, at the cost of higher register pressure. More or less what we do here: https://rev.ng/downloads/bar-2019-paper.pdf

Um, in case you don't know, UTM (based on QEMU) is out for quite a while.

Some of these tools include Oracle VM VirtualBox (that I've used since before the acquisition of Sun Microsystems by Oracle), VMWare Workstation Player, and QEMU, but last year, I found out about Multipass.

For C/C++ projects that use meson as the build system, there is an excellent way to manage dependencies:

https://mesonbuild.com/Wrapdb-projects.html

https://mesonbuild.com/Wrap-dependency-system-manual.html

meson will download and build the libraries automatically and give you a variable which you pass as a regular dependency into the built target:

https://github.com/qemu/qemu/tree/005ad32358f12fe9313a4a0191...

https://github.com/harfbuzz/harfbuzz/tree/main/subprojects

https://github.com/harfbuzz/harfbuzz/blob/37457412b3212463c5...

Or, if you're using proper operating systems, they're managed by the usual package manager, just like everything else.

For all the users of the Linux platform, QEMU is the VM that you should go for. This software comes without any price tag and works as an emulator of various machines with utmost ease and completion; the software uses dynamic translations to emulate hardware peripherals and enhances its overall performance. If you are using QEMU as a virtualizer, then it will function exactly like the host system (provided you have the right set of hardware).

In this tutorial, we set up macOS and Windows virtual machines on UTM, a macOS application that provides a GUI wrapper for QEMU, a powerful open-source emulator and virtualizer. UTM allows you to easily manage and run virtual machines without memorizing complex commands. It also has special handling for macOS, making it simpler to install compared to other virtual machine software.