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 
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.
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.
The release blog post with more details:
https://xen-orchestra.com/blog/xen-orchestra-5-79
Hello there! We will announce very soon the first preview of our VMware migration tool, using only the VMware API (via Xen Orchestra).
We did some tests, but we need broader feedback from VMware users in our community.
master) or latest release channel (XOA, latest channel)xo-cli (see below)xo-cli vm.importFromEsxi host=<VSPHERE_IP> user=<VSPHERE_USER> password=<VSHPERE_PWD> sslVerify=<true|false> vm=<VSPHERE_VM_ID> sr=<SR_UUID> network=<NETWORK_UUID>
Right now, we are facing various challenges. If you have some VMware experience, we'd like your point of view.
See https://xcp-ng.org/blog/2021/09/14/runx-next-generation-secured-containers/ for more details.
If you want to test high level of security with your containers, yes. Or if you like to play with shiny new techs and report bugs 
THIS IS A TECH PREVIEW
It's not meant to run in production. Play with it in your lab, not in production. You have been warned 
Follow the next section.
Create the file /etc/yum.repos.d/xcp-ng-runx.repo with:
[xcp-ng-runx]
name=XCP-ng runx Repository
baseurl=http://mirrors.xcp-ng.org/8/8.2/runx/x86_64/ http://updates.xcp-ng.org/8/8.2/runx/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng
Then, install all the packages:
yum install --enablerepo=epel -y qemu-dp xenopsd xenopsd-cli xenopsd-xc xcp-ng-xapi-storage runx
yum install --enablerepo="base,extras" docker podman
xe-toolstack-restart
mkdir runx-sr
mkdir -p /root/runx-sr
xe sr-create type=fsp name-label=runx-sr device-config:file-uri=/root/runx-sr
You must create a VM template with the desired amount of ram an the number of cores to use. Make sure the vm type is: PV.
It's not necessary to add disk to this VM.
Open /etc/runx.conf and modify these variables: SR_UUID and TEMPLATE_UUID.
Using podman:
podman pull archlinux
podman container create --name archlinux archlinux
podman start archlinux
With docker:
podman with docker.docker -b none.Please test and report any problem
So far we got 4 templates available:
Would you like other OS? Or even apps installed in those OS? Let us know!
Yes, if you removed the master without tell it to transition the master role to another machine, you have to promote manually your current slave if your "old master" isn't there anymore
Hi,
That's weird. do you have the same view in Xen Orchestra? Can you screeshot htop in the Dom0?
Packer is probably what you need @AtaxyaNetwork worked on it for some VMs here, feel free to ask her if you have question.
PV guests should be avoided as possible, it's not officially supported anymore.
Adding @stormi
I think it would be more reasonable to start patching on 8.3, because it seems to be a lot of modification for a LTS. Anyway, we'll take a look and come back to you, please do the same in terms of Ceph stability in your own tests! Thanks