_ananos_

6 ms·

31.
by _ananos_ 6y ago
yeap, the initial idea was to cover VMs (and one of the use cases is indeed Serverless, for instance AWS Firecracker), but as it turns out, there are users that might benefit from this simplified abstraction in general.
32.
by _ananos_ 6y ago
thanks for your feedback! we will try to clarify things on our next posts! in short vAccel is a framework that translates function calls from users (upper side of this diagram) to the relevant functions of the respective acceleration framew
33.
Enabling Hardware Acceleration on AWS Firecracker(blog.cloudkernels.net)
4 points by _ananos_ 6y ago|0 comments
34.
by _ananos_ 6y ago
More info on how we use it on AWS Firecracker is available on our blog post: https://blog.cloudkernels.net/posts/vaccel_v2/ and our github pages: https://github.com/cloudkernels/vaccelRT , ht
35.
VAccel: Hardware Acceleration for Lightweight Hypervisors(vaccel.org)
48 points by _ananos_ 6y ago|10 comments
36.
Firecracker on the RPi4, code now upstream(github.com)
4 points by _ananos_ 7y ago|0 comments
37.
Build a single-app rootfs for Firecracker MicroVMs(blog.cloudkernels.net)
6 points by _ananos_ 7y ago|0 comments
38.
Porting Firecracker to a Raspberry Pi 4(blog.cloudkernels.net)
6 points by _ananos_ 7y ago|0 comments
39.
Build a 64bit bootable image for a Raspberry Pi 4(blog.cloudkernels.net)
6 points by _ananos_ 7y ago|0 comments
40.
by _ananos_ 7y ago
built a stock ubuntu (cloud-init ready) image: https://cloudkernels.net/ubuntu-18.04.2-preinstalled-server-... sha1sum: 0b1d8b72ea5410fb7928925fd76dd0218b4f7a94 The behaviour should be identical to installing on a RPi3 (us
41.
by _ananos_ 7y ago
there is a number of factors to consider when comparing this kind of technologies. Linux containers provide native performance for almost all applications, true; but there are tons of implications when it comes to multi-tenancy (security, Q
42.
by _ananos_ 7y ago
agree, I'm just talking about the flexibility to build & deploy a workload in any device (cloud / edge). Think of it like "building your own buildroot image" vs. "docker build" based on busybox or alpine. I
43.
by _ananos_ 7y ago
will do -- that was only a high-level run to make sure there's enough compatibility with our framework & tools to move forward. stay tuned ;)
44.
by _ananos_ 7y ago
there you go: https://cloudkernels.net/rpi4-64-bit-kvm-docker.img.xz sha1sum: 1b96a6be5256182eaceb5894fb993c8ffce8c2a2 it's quite beefy, 2.5GB -- apologies for that. We should be able to craft a much smaller image base
45.
by _ananos_ 7y ago
definitely! that's our initial goal. Quantify the penalty and examine the trade-offs. Clearly, virtualizing workloads on such devices with standard VMMs/hypervisors isn't ideal. And we're working towards this direction;
46.
by _ananos_ 7y ago
sure! bare-metal would be awesome. But isn't it a shame not to take advantage of all the virtualization/containerization goodies out there? After all, the virtualization overhead nowadays is only referring to I/O (network &am
47.
by _ananos_ 7y ago
baking one right now -- it is based on http://cdimage.ubuntu.com/ubuntu/releases/18.04.2/release/ub... but slightly modified (no root password, KVM setup, docker installed etc.) will provide a link once
48.
by _ananos_ 7y ago
the issue about the available RAM is this: https://github.com/raspberrypi/linux/commit/cdb78ce891f6c636... probably some kind of address mapping, but I'm no expert on this stuff ;-)
49.
by _ananos_ 7y ago
actually, the host OS for this post is a ubuntu 18.04.2 server image. root@pi:~# cat /etc/issue.net Ubuntu 18.04.2 LTS root@pi:~# uname -a Linux pi 4.19.57-v8+ #2 SMP PREEMPT Tue Jul 9 20:31:37 UTC 2019 aarch64 aarch64 aarch64 GNU
50.
by _ananos_ 7y ago
yeap, that's the case with the older models too. A53 has also virtualisation extensions. The main difference about the Pi4 is the GIC which removes the need for emulating interrupt handling. Other than that, the A72 handles VMEnters&#x
51.
by _ananos_ 7y ago
More RAM could help us with a scale test, or maybe with a storage-related benchmark. Regarding the GIC, first I think we should spend some time examining the benefits from the A72 upgrade. Then, breaking down the time spent on each step of
52.
Playing with a Raspberry Pi 4 64-bit(blog.cloudkernels.net)
116 points by _ananos_ 7y ago|67 comments
53.
by _ananos_ 8y ago
seems a bit overpriced. Other than that, it's a decent workstation.
54.
Bake and run a Python snippet on a rumprun/solo5 unikernel and nabla-containers(blog.cloudkernels.net)
5 points by _ananos_ 8y ago|0 comments
55.
by _ananos_ 8y ago
Well, I thought it was funny. A bit of (self-)sarcasm is not bad from time to time.
56.
by _ananos_ 8y ago
http://research.cs.wisc.edu/multifacet/papers/micro15_border... I think this paper presents an interesting overview of how to mitigate a subset of hw-related attack vectors. Seems really relevant.
57.
Build the nabla containers toolchain on ARMv8(blog.cloudkernels.net)
7 points by _ananos_ 8y ago|0 comments