Yes, you can always export/import the config on a working install. So it's a problem on your build, it's really hard to tell where's the culprit (because you built it, you see why we distribute it via XOA for production/professional usage 😄 )

@olivierlambert Yes, this worked great! I’ll just keep both until v6 releases.

Hello @someone2b,

Marc here, CMO of Vates. I wanted to provide some clarity on our new pricing structure and the reasoning behind these changes.

Here are a few key points that led to our decision:

In 2022, half of the support requests from Xen Orchestra customers were actually related to issues with the hypervisor layer, which aren't covered by standalone Xen Orchestra support.

We've seen an increase in requests for XCP-ng support from users who only seek help after encountering issues in their infrastructure.

XCP-ng and Xen Orchestra have become deeply integrated, making it increasingly challenging for our team to effectively support Xen Orchestra without also addressing the virtualization platform.

We’ve also redesigned our business model to be more equitable, particularly for smaller infrastructures. For those with 10 hosts or fewer, the new pricing is actually lower than the previous cost of purchasing XCP-ng and Xen Orchestra separately.

That being said, we didn't forgot as well all the remaining XenServer users out there and we are currently working on to have a secure and affordable path forward for them as well. If you have any questions or would like to discuss this further, please don’t hesitate to reach out to our sales team at sales@vates.tech.

Marc

@omatsei I figured out the problem. There appears to be a bug in XO that requires you to check "Check Certificate" and/or "Start TLS", save the configuration, then uncheck them, then save again. Then it should work. The bug is that they're unchecked by default, but apparently they're enabled in the background.

@caponate yup, I ended up doing the same

@splastunov
Great idea! Thank you!

The doc is now updated: https://xen-orchestra.com/docs/supported_hosts.html

what about xcp center v20, after enabling the checkbox, it can't work like if we enable power_on:true via command line? is xcp center not patched?

The SR won't store the metadata. Maybe you have a metadata backup saved for this pool?

@abudef Indeed, the delay is in milliseconds.

Hi @BenjiReis,
Yes. Problem solved by adding the following lines to the resolv.conf file:

@julien-f Maybe we do not differentiate "attaching" a disk and "connecting" a disk. I just created a new disk then went to a VM to attach it, then did the same on another VM without problem on XO UI.
BUT it seems that I cannot "connect" it on both VMs, which is not a problem, I only need to know what's possible, and what's not to be able to handle it.

Regards 🙂

Thank you @olivierlambert.

@planedrop Ignore me, I did make a dumb mistake, all is working now.

Having XO from source or XOA act as a certification authority for the XCP-ng hosts is for sure a good approach. Would be great if that could include the VMs running on the XCP-ng hosts, which is my main goal (apart from being able to HTTPS into XO from source of course).

I've acctually got a PR to help solve the documentation regarding the yarn forever part. Since I never could get that to work, I implemented a systemd variant instead.

#7848

Ping @olivierlambert for visibility 🙂

Hi,

I am currently looking for exactly this function.
If there is a solution here, I am very interested.