search for: rumpkernels

...many of which I expect have their own dependencies etc. For another metric consider for the regular x86 binary: $ ldd /usr/bin/qemu-system-x86_64 | wc -l 87 $ So without a normal looking cross env we are talking about asking maybe 60 -90 different library maintainers to do something special for rumpkernels. (Surely some of those 60-80 are things you would omit from a rump build for various reasons, but still...) > If the above didn't explain the grand scheme of things clearly, have a > look at http://wiki.rumpkernel.org/Repo and especially the picture. If > things are still not clea...

Hi, Wei Liu hinted that I should "chime in and / or provide corrections" (his words). I'll attempt to do exactly that by not really replying to anything specific. For the record, when I say "we" in this mail, I mean "people who have contributed to the rump kernel project" (as also indicated by the email-hat). First of all, there's a difference between

...#39;t seem like a particularly big deal to me, not that I'm questioning your statement. >> If I were you folks, I'd start by getting qemu out of the door > > That's certainly the highest priority, at the moment I don't think we > actually have a QEMU Xen dm based on rumpkernels which anyone could package > anyway, irrespective of how hard that might be. > >> , and >> worry about generalized solutions when someone wants to ship the second >> unikernel (or third or any small N>1). > > Unfortunately I think the N==1 case is tricky already fro...

...ve has clarified a bit why it is a big deal to (binary) distros? > > > > If I were you folks, I'd start by getting qemu out of the door > > > > That's certainly the highest priority, at the moment I don't think we > > actually have a QEMU Xen dm based on rumpkernels which anyone could > > package > > anyway, irrespective of how hard that might be. > > > > > , and > > > worry about generalized solutions when someone wants to ship the > > > second > > > unikernel (or third or any small N>1). > > &g...

...build a bootable image, perhaps capable of running either on Xen or > KVM. > > That's obviously not going to happen overnight -- but it would be > interesting for Someone to give a try, just to see how difficult it is. > If it's not that difficult to build libraries against rumpkernels and > package them up so they can be linked to from applications, then the > road to Debian / Fedora-built unikernel applications (including qemu) > may not actually be that long. ----------------------------------------------------------------------- Wei and I both replied. Wei said: &...

Xen upstream BoF ================ We had a discussion around Xen and packaging at Debian's annual developer conference (Debconf) a few weeks back: https://summit.debconf.org/debconf15/meeting/279/xen-upstream-bof/ These are my notes, I think there is probably stuff of interest to most distro people, not just Debian folks. The session was scheduled in a small, out of the way, room. Around 2

Hello LLVM Developers, Within Google, we have a growing range of needs that existing libc implementations don't quite address. This is pushing us to start working on a new libc implementation. Informal conversations with others within the LLVM community has told us that a libc in LLVM is actually a broader need, and we are increasingly consolidating our toolchains around LLVM. Hence, we