stormi Microcode updated on affected Gen11 i7. Running normally.

gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.

I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!

bleader Installed and running.

bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.

bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.

abudef olivierlambert thomas-dkmt I agree. I read block the same way... how about disable or prevent. (French? empêcher)

julien-f olivierlambert

Thanks for the ability to delete XO task logs feature! (XO commit f6e6e)

gduperrey I have several hosts updated and running. I'm happy to see 8.3 updates on parity with 8.2.

stormi Installed on several test and pre-production machines.

olivierlambert Current version: 5.106.1

On the XOA page, I enter my email/password in the Registration box.
There's no way to 'unregister' and just use the free version.

XOA knows I have a 'trial' but the license is not activated (because it is active on another XOA VM) and it locks into the XOA page only.

olivierlambert I understand enforcement, but this is now draconian.

As a test:

I deployed XOA from the web. Fine.

But I can't update it without registering it. Fine.

I login with my Vates XOA account, now it says I'm registered and can update. So I update XOA.

Now I'm registered but not licensed and I get the error and can't use XOA Your current Xen Orchestra license has expired (Dec 31, 1969). Please reach out to your vendor.

I try to unregister, but that's not an option. I enter a bad email/password so registration fails, but I still get an error and am restricted.

So, there's no way for me to use and update a "free" XOA without forced registration on to a new account? I could use trial XOA and update without registering before. I could register but not use a XOA license and use the free version before...

Danp Activate license resolved that issue, but this is different than before! Just having the trial license was enough to make everything work without error. So, trials will no long work without activation (may be that how it always should have worked).

michael.manley Thanks for the update! I still use it, mostly for the direct (not web based) console and it can still do a few things XO does not.

The update did not replace the old version (also different install location), but that's ok. I just uninstalled the old one and reconnected to the XCP servers.

Danp Two steps forward, one step back. The update to 5.106.1 worked and XOA is reachable, but not usable...

Now I get the error at the top:
Your current Xen Orchestra license has expired (Dec 31, 1969). Please reach out to your vendor.

But for Registration I have:
You have a Xen Orchestra Appliance granted under trial. Your trial lasts until 12/31/2025, 10:59:31 AM

olivierlambert After upgrading XOA to 5.106.0, now all I see is an error has occurred.

XOA was working, I did the normal self upgrade. XOA runs and after I login, it starts to load the normal page, I see the left side menu show up and then tries to load the normal normal VM running page URL of https://xoa/#/home?p=1&s=power_state%3Arunning+ and then drops to an empty page of an error has occurred. Any XOA page I try to access (including support) ends up dropping out to the same error page. I rebooted the XOA VM and the same issue happens.

NOTE: XO from source (current master 3bb5900, same as release 5.106.0) works correctly.

DustinB The goal is if the primary host is down then XO will connect to another host. If XO connects to a slave host then it will be redirected to the new master but it needs to connect to a working host in the pool.

The idea is to have one entry per pool rather than per host since XO does not need to (or want to) connect to ever host in a pool, but needs to reach one working host per pool.

olivierlambert I'm just one user with an idea... If you found it caused more problems than it solves then maybe it's not a good idea. It's up to your team.

florent No. The dashboard health is clean. No VDIs attached to control domain

Murf You need to upgrade NodeJS to at least version 20.x

Current version is 22.x, so you should just upgrade to that.

When setting up a XCP server in XO, is it possible to enter multiple IPs or host names for a single server entry? If I have a pool of 3 hosts then I can enter the 3 hosts individually and one will work and the others will show an error. I just want just have a single pool server entry with the three IPs (or hostnames) so XO will contact any/all of the a hosts to find a working master from a single entry.

Like: 192.168.1.11, 192.168.1.12, 192.168.1.13