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)

Hey everyone,

Just to let you know I'm finally taking a 2 weeks break, and it's really needed (thanks Broadcom for the extra work those last months )

I will make sure that everyone with admin powers will review often the registration waiting list. For the rest, it's up to you, the community, to demonstrate you can help each other without having me around. I don't doubt it, but I wanted to tell you why you won't see me for the next 2 weeks

Enjoy and see you then!

https://xcp-ng.org/docs/

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.

What about this one?

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.

Thanks for all your work @borzel ! We are doing our best to improve our capacity to quickly review and structure external contribution in XO Lite: we are currently working on a dedicated CONTRIBUTING.md with links to the Figma UX design and such, so everything can be developed in the open to everyone.

RunX tech preview

What is RunX?

See https://xcp-ng.org/blog/2021/09/14/runx-next-generation-secured-containers/ for more details.

Do I need it?

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

How to test it

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.

Installation

1. Create the repo, install packages + restart toolstack.

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

2. Create a 9p SR

mkdir runx-sr
mkdir -p /root/runx-sr
xe sr-create type=fsp name-label=runx-sr device-config:file-uri=/root/runx-sr

3. Create a VM template

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.

4. Modify the runx config

Open /etc/runx.conf and modify these variables: SR_UUID and TEMPLATE_UUID.

5. Start a VM.

With Podman

Using podman:

podman pull archlinux
podman container create --name archlinux archlinux
podman start archlinux

With Docker

With docker:

• Use previous commands and replace podman with docker.
• Also you must start the docker daemon using an empty bridge using docker -b none.

Feedback

Please test and report any problem

No, it's fine, as long the issue contains all the relevant details it's fine

Hi,

Please contact the sales via https://vates.tech/contact/

They will help you to provide everything you need for your tests

Can you open an issue on the Github repo for the CCM?

Can you use another way than dmidecode to fetch the UUID? Because it's not the right way to get VM UUID (instead you should use xenstore read with the UUID key

It's better to have it to get handy options like IP addresses displayed and so on.

It's likely because the VM UUID from a XAPI perspective is different (generated by XAPI) and you can fetch it by reading the appropriate xenstor entry.

You can also avoid using PV drivers, it will work.

So that explains it then Free BSD boots and since the kernel loads successfully the PV drivers, it's fine by us.

Excellent news! I suppose we should document it somewhere, ping @thomas-dkmt

Maybe because SM version used for XOSTOR is a bit different? @dthenot do you confirm?