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

olivierlambert created this issue in xcp-ng/xcp

closed Build components from the sources #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)

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.

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:

• Debian 10 cloudinit ready/disk growable/DHCP
• CentOS 8 cloudinit ready/disk growable/DHCP
• PfSense 2.4
• Alpine Linux 3.10

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.

A new prompt

• removed the current user (because it's an "appliance", with only root
• added current time, very handy to know how long your command took (eg export)
• using XCP-ng colors

New vs old:

Obviously, we got a fallback for terminal without color support.

Also, it also works on white background terms:

A new console theme (xsconsole)

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?

https://www.citrix.com/blogs/2019/04/25/citrix-hypervisor-8-0-is-here/
and
https://docs.citrix.com/en-us/citrix-hypervisor/whats-new.html

So this is the starting point of a LOT of things for us. We'll keep you posted on what's new regarding SMAPIv3 perfs, UEFI and everything else.

Stay tuned!

https://xenproject.org/2019/04/02/whats-new-in-xen-4-12/

In short:

• 1446 commits from 364 patches
• possibility to build for PV or HVM/PVH only (reducing attack surface)
• QEMU deprivilege (also reducing attack surface)
• Argo (new inter-domain communication, @ronan-a will take a look)
• Improved VM introspection (less overhead)
• Credit 2 schedule by default
• PVH dom0 in tech preview
• Better IOMMU mapping for improved EPYC boot time
• auto dom0 sizing (% of total system RAM or static+percent)

Details: https://wiki.xenproject.org/wiki/Xen_Project_4.12_Feature_List

1. Can you restart the toolstack and see if it changes memory footprint?
2. Anything suspicious in dmesg?

htop will be better to spot things You can alternatively use Netdata

Same problem with XOA @othmar ?

This is a message for XO team, it should do that normally.

It's a bit less flexible than using a NFS share (because it's easier in case of XOA loss, to just reconnect to a NFS and fine all your backup), than having to reconnect the iSCSI to your XOA.

But it will work, yes.

Hi!

1. I would suggest to use a more recent XenServer version (Citrix Hypervisor) or ideally XCP-ng
2. It's Xen Orchestra, not orchestrator (even if it makes less sense )
3. CR (Cont. Replication) doesn't care what's on destination, as long it's a storage repository in your host.
4. Delta backup (and backups) are files. If you want to do a backup directly on a iSCSI storage, you need a file system on top. So if you really want to use an iSCSI storage for that (NFS would be easier), you need to attach the iSCSI storage to your XOA, format it as ext (for example) and use it as a "local remote".

I would suggest to create a support ticket so we can assist you in a more efficient way.

You need to unplug before remove it. XO does that automatically.

Same answer as the other topic, as I exactly said in my previous post here: you can solve this in XO, Dashboard/health view.

This is already something visible in Xen Orchestra, in Dashboard/Health view, we exposed all VDI attached to a control domain, it's one click to solve it.

If you lack Linux skills, it might be a bit too soon to try to build XO on ARM.

I think we had people already built XO on ARM, but you first need to understand that's not the same CPU arch, and get an OS correctly installed first. I think Debian might be easier (Raspbian?)