On 2/13/19 1:31 AM, Rich Persaud wrote: >> On Feb 11, 2019, at 05:05, Lars Kurth <lars.kurth....@gmail.com> wrote: >> >> Hi all, >> >> we have the community call for February coming up this Wednesday. My sincere >> apologies, that I have not asked for agenda items last week. A current >> agenda (primarily a skeleton) is available at >> https://docs.google.com/document/d/15ZLzQcH794jufDZW1oNYVY2D12CnVqxQ-klFAqkd2bU/edit#heading=h.mz1wjb9vekjn >> >> Please propose topics by either editing the running agenda document at >> https://docs.google.com/document/d/1Ufv9XcQO0zIAVeFbFCAHAeEIB9Ap4Y4srAm4vI8I01I/edit# >> or by replying to the mail. Ideally by a few hours before the meeting! > > Proposed agenda items: > > 1. Tailored instances of Xen: continuing the Nov 2018 discussion of > KCONFIG/L0 hypervisor use cases. More details upcoming via wiki page. > > 2. Macro supply chains: what are best practices for maintaining Xen macros > which originate in other open-source communities, e.g. QEMU or Linux? Would > each macro benefit from a documented status (e.g. "Ignore upstream changes", > "Monitor upstream changes", "Mirror upstream changes") with associated > tooling? > > 3. Go toolchain: is there community interest in collaborating on the > development of golang tools for local management of Xen? Historically, > OpenXT used a combination of Haskell and Ocaml tools. Some OpenXT community > members are using golang with Xen. Could these new tools find a home in > upstream Xen?
FWIW we did start to make golang bindings for libxl (see xen.git/toools/golang/xenlight). I think golang is an obvious language to write Xen control stacks in. The main issue I see at the moment is that while the *API* between a toolstack and libxl is backwards-compatible, the *ABI* between the resulting binary and Xen is not; meaning that every time you change your Xen version, you need to recompile your golang programs. (This of course is not limited to golang, but it was highlighted to me when I started to use go-xenlight.) But I'd definitely be interested in seeing what your community members are doing, and if we can come up with a useful solution. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
