Systems Programming | 294 Members | |
| Kernel, stdenv, low-level hacking, patchelf, … | 74 Servers |
| Sender | Message | Time |
|---|---|---|
| 13 Jan 2022 | ||
| Actually, this has to be the coolest thing I've seen this week. With all those crazy tracing features, I assume you've been using this in place of QEMU for kernel development? | 07:35:13 | |
| (actually it attaches to VMs - pretty cool) | 07:38:56 | |
| Mic92: I already saw your nixos-shell, you have a lot of different VM stuff, Maybe I should add some links to the wiki or something. | 08:00:30 | |
In reply to @zhaofeng:zhaofeng.liThis project side-loads a process into kvm-based guests and mounts a block device based on a file you give to vmsh. I really need to update the README, since my paper is now on a good way to get published. | 08:04:52 | |
| This is the abstract of my paper: Lightweight virtual machines (VMs) are prominently adopted for improved performance and dependability in cloud envi- ronments. To reduce boot up times and resource utilisation, they are usually “pre-baked" with only the minimal kernel and userland strictly required to run an application. This in- troduces a fundamental trade-off between the advantages of lightweight VMs and available services within a VM, usually leaning towards the former. We propose Loki, a hypervisor-agnostic abstraction that enables on-demand attachment of services to a running VM— allowing developers to provide minimal, lightweight images without compromising their functionality. The additional applications are made available to the guest via a file system image. To ensure that the newly added services do not affect the original applications in the VM, Loki uses lightweight isolation mechanisms based on containers. We evaluate Loki on multiple KVM-based hypervisors and Linux LTS kernels and show that: (i) Loki adds no overhead for the applications running in the VM, (ii) de-bloating im- ages from the Docker registry can save up to 60% of their size on average, and (iii) Loki enables cloud providers to offer services to customers, such as recovery shells, without interfering with their VM’s execution. | 08:05:44 | |
| In a nutshell, it finds the guest kernel in memory and loads some code into it. | 08:07:18 | |
In reply to @mic92:nixos.devYeah, I see the injection part - Pretty cool I must say. At the beginning I thought you were building your own VMM with all the rust-vmm crates. | 08:08:08 | |
In reply to @zhaofeng:zhaofeng.linah, there are already too many hypervisor out there :) | 08:09:01 | |
| I was considering taking the vm builder and having it not build the total vm and just spit out an init I could pass to qemu and boot that over 9p | 08:08:58 | |
| arg did github just ship an update that crashes firefox? | 08:15:34 | |
| Sounds like Mozilla did | 08:16:46 | |
| I didn't update anything in like a week, but now github has a loading bar like Youtube, and it's spininng on two cores doing nothing. | 08:17:23 | |
| My friends are reporting the same as well. This doesn't seem to be an isolated issue. https://old.reddit.com/r/firefox/comments/s2u7eg/is_firefox_down/ | 08:17:37 | |
| Oops copied the entire message | 08:17:46 | |
| Zhaofeng Li was the one who found it | 08:17:57 | |
| Yup, see offtopic. I'm typing from my phone atm. Absolutely mindblowing | 08:18:17 | |
| Oh right...wtf is firefox phoning home wut. | 08:18:27 | |
| Firefox is definitely phoning home, yes | 08:18:43 | |
| Mostly for things like staged feature rollout | 08:19:09 | |
| I guess this is getting offtopic I just wanted to load that link. | 08:23:35 | |
| phoning home is not unusual, but if it breaks something, somethign did a booboo | 08:23:45 | |
| I moved to FF to try and get away from Google and shit like this. | 08:25:46 | |
| http3 bug? | 08:33:01 | |
| Mic92: how do I use the justfile? | 08:44:06 | |
| woobilicious: https://github.com/casey/just | 09:27:18 | |
| https://phabricator.services.mozilla.com/D135871 | 15:32:10 | |
| Looks like this was what caused the Firefox "outage" | 15:32:15 | |
| 15:53:26 | ||
Excuse me, but this code doesn't even attempt to be correct. Totally-Not-Content-Length: would be matched, and so would X-Some-Header: Content-Length: | 19:59:40 | |
| I'm very, very disappointed that this made it into Firefox in the first place. | 20:00:34 | |