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:
First, you need to check if it's a guest issue or not. Boot your failed restored VM with a live CD (Ubuntu or something else) and check if you can access the disks.
When you connect to a working, machine, yes it does
But XAPI connection isn't persistent: it means, when the pool is disconnected, XO has no recollection whatsoever on who was the "real" master the last time it was connected. The only info we store is the IP address you entered in Settings/server.
I agree, functionally speaking, it can be limiting in your case. A viable option would be to save all existing hosts IPs in the XO database, as fallback if we can't connect to the IP you entered. This is not a very common case, that's why it wasn't done before
That's because the effort to change this will be taken into account in XO 6
Alternatively, you can indeed contribute, this will be very welcome!
And how could it guess that?
Right now, if you target a slave, XO will connect to it, but XAPI will answer: "I'm not the master, here is master's IP" and then XO will redirect to the master.
But since the slave is down, XO has no meaning to "know" anything, so it will fail.
If XO got a timeout on this IP, it's because the master host is probably redirecting XO to it. So it's not XO, it's redirected there for a reason. It's hard to tell why without digging further.
Do you have VMs to backup that are only available on a halted host?
Is the IP address displayed is available?
Hi,
I think this is not a Xen Orchestra limitation. Can you paste the error please?
Sure.
