plam503711

8 ms·

31.
Please stop planting only corn(virtualize.sh)
12 points by plam503711 2y ago|0 comments
32.
Making Rust a first-class citizen for Xen(xcp-ng.org)
17 points by plam503711 2y ago|0 comments
33.
XCP-ng 8.3 is now available(xcp-ng.org)
15 points by plam503711 2y ago|0 comments
34.
Advancing Xen on RISC-V: key updates(xcp-ng.org)
2 points by plam503711 2y ago|0 comments
35.
ASID Allocator and TLB management in Xen for x86(vaishalithakkar.in)
1 points by plam503711 2y ago|0 comments
36.
The reality of OSS maintainer fatigue(virtualize.sh)
2 points by plam503711 3y ago|0 comments
37.
Building a business with almost only self-hosted and Open Source software(vates.tech)
6 points by plam503711 3y ago|0 comments
38.
by plam503711 3y ago
Xen provides a great security design and a protocol to do hypercall that makes sense (unlike kvm+virtio which is DMA all the way, with all the plus in terms of simplicity but the bad on the isolation aspects). If I wanted to caricature the
39.
by plam503711 3y ago
I don't think it will be "instant change". I agree on the gradual result, but I think it might be faster than we think. Yes, it also depends on the ecosystem, but I think the world is more ready for ISA diversity than ever.
40.
by plam503711 3y ago
(XCP-ng founder here) I'm more optimistic for RISC-V. For all the devs who worked on it here (at https://vates.tech ), they told me it's very easy to work with since it's close to many Arm design principles. That&#
41.
Open Core is the new shareware (The Moral Contract)(virtualize.sh)
1 points by plam503711 3y ago|0 comments
42.
New Xen Guest Tools in Rust(xcp-ng.org)
1 points by plam503711 4y ago|0 comments
43.
Bringing Rust to the Xen Project(xcp-ng.org)
19 points by plam503711 4y ago|1 comments
44.
Using SPDK with Xen: performance AND security(xcp-ng.org)
5 points by plam503711 4y ago|0 comments
45.
Project and Release Tracking for Xen – Part 1(xcp-ng.org)
9 points by plam503711 4y ago|0 comments
46.
by plam503711 4y ago
Thank you, both for being kind and also providing a constructive feedback. "So" is very common trap for French speakers :D
47.
by plam503711 4y ago
It's not a custom Xen: it's *is* Xen (AFAIK, with possibly their own patch queue for some specific needs on top of it). What's custom is the toolstack around it :)
48.
by plam503711 4y ago
Xen Project is far being dead (there's a lot of activity in the mailing list, and now, thanks to new contributors like Vates/XCP-ng, there's also more initiatives to have a decent project tracking, see https://gitl
49.
by plam503711 4y ago
"The reports of my death are greatly exaggerated" Regards, Xen.
50.
by plam503711 4y ago
You can read the original conversation from 2018 here: https://lkml.org/lkml/2018/1/21/192
51.
by plam503711 4y ago
The real golden-"I told you so" (that triggered the idea to write this very blog post) comes from a tweet of David Woodhouse last July: https://twitter.com/dwmw2/status/1549042968320811008
52.
by plam503711 4y ago
Yes, sorry for that, I was really more focused on getting the story details than the spelling (plus I'm not a native speaker as you probably guessed).
53.
by plam503711 4y ago
A spectre silently fixed the spelling, thanks for the feedback ;)
54.
Why Xen Wasn't Hit by RETBleed on Intel CPUs(xcp-ng.org)
130 points by plam503711 4y ago|60 comments
55.
Grant Table in Xen(xcp-ng.org)
2 points by plam503711 4y ago|0 comments
56.
by plam503711 4y ago
I agree on the automation part, that's an important objective in our backlog (like we did with Terraform plugin etc.)
57.
by plam503711 4y ago
But if you buy only for support when you need, it defeats a bit the purpose of also paying the project to get security updates and new features (and more QA). And to get enough money inside, this needs to get TONS of customers. Check at Pro
58.
by plam503711 4y ago
I understand your point. However, anything else might require time to maintain it (a script, a container, a VM, whatever you want: people will expect it to work obviously, so this needs time/effort to test it, unlike a simple documenta
59.
by plam503711 4y ago
This. This is VERY true. Pricing is capital if you want to have some respect. The worst "customers" are often those paying nothing or the cheapest price.
60.
by plam503711 4y ago
How difficult is to make a `yarn && yarn build`? Also this is important to have a validated/tested environment to deploy your code (that's why a VM is really handy). Regarding XO website, it was again for historical reason

More ›