Xen Orchestra and XCP-ng founder. Vates CEO and co-founder.
This is not just a powerful symbolic thing: by closing issue nĀ°1, we are really reaffirming our independance and our capacity to build everything without using any binary provided by Citrix.
It's really a great news for XCP-ng's future!
https://github.com/xcp-ng/xcp/issues/1
Since last week, we have a new team member 
@ronan-a is now part of Vates XCP-ng team, with @stormi and myself.
@r1 and @johnelse are still with us as external contributors.
@ronan-a , feel free to introduce yourself here (and the stuff you are working on)
It's far from being complete, but it's a great first step in improving XCP-ng existing documentation and also visibility/credibility!
Everyone can still contribute (link on the bottom of each page), even if it's a bit more difficult than the wiki.
Let me know what you think about it
What about the wiki? We'll probably to continue to have very specific content there, and "promote" content to the doc if it "fits" for enough people.
https://xcp-ng.org/blog/2020/04/17/100-000-downloads-for-xcp-ng/
So you probably spotted the news, feel free to comment here 
To avoid splitting the community, we'll merge XO forum in this category. It seems not possible (or very not trivial) to fetch the previous XO threads here, so we'll probably have a transition time until we redirect directly XO forum URL toward this category directly.
Maybe it wasn't clear? French gov won't do anything in the project, they just support it as a research and dev project boosting innovation, and indirectly contributing to create more jobs that can't be replicated easily elsewhere.
There's no "control" on how we decide to do the R&D, as long as we put resources into it as we said.
XCP-ng is a free and community project, and everybody who want to contribute can do it. There's no "link" between us and any government.
So far we got 4 templates available:
Would you like other OS? Or even apps installed in those OS? Let us know!
Less yellowish terminal to use less different colors and keeping the variations in the logo:
For XCP-ng 8 we thought that it might be interesting to get a dedicated visual identity outside the boot splash: the prompt and the "ncurse" display.
rootNew vs old:
Obviously, we got a fallback for terminal without color support.
Also, it also works on white background terms:
New vs old:
There is also a fallback on terminals without color support (unchanged)
Maybe you could think it's a minor thing, but in the end, that's how we show XCP-ng is not just a clone of CH/XS
Obviously, you can still configure this easily (especially the prompt, because you can override it).
What do you think?
This is question for @BenjiReis when he's around
Eg: xe pool-ha-enable heartbeat-sr-uuids=<SR-UUID> ha-config:timeout=90
That's because UEFI is almost by default on HyperV since longer in XenServer/XCP-ng. When Windows 2012R2 was out, only BIOS was available on XenServer. So they put the template using UEFI.
Again, with Xen Orchestra, you should have been able to enable UEFI with it.
This is not the best way to do it.
You need to upload the VHD via Xen Orchestra, not putting it directly into the XCP-ng SR. In general, don't try to bypass XAPI, it's NOT a good idea.
Also, what kind of template did you use when you created the diskless VM on XCP-ng? Double check there's no discrepancy, I have the feeling it might be related to UEFI vs BIOS.
You can set a larger HA timeout on the heartbeat if I remember correctly.
Also, HA might use a dedicated file, maybe /var/log/xha.log, so interesting info can be there.
Mounting might require some extra permissions, depending on your system configuration. So it's tricky to answer because this is your own system/environment.
Sounds like a memory leak. It's hard to pinpoint in general. I would say that investigating on 8.2 as soon it's out would be probably a better thing to do (it will be an LTS).
It will be out in beta soon
Be sure to use:
xe vm-param-get param-name=PV-drivers-version uuid=<VM UUID>
Output example:
# xe vm-param-get param-name=PV-drivers-version uuid=1c970fff-a74c-2f9d-21fe-9a9259e333e1
major: 8; minor: 0; micro: 50; build: 1