Thanks Olivier! That is what we assumed, but with how the 3 hosts per pool was in there under the essentials licenses it was up for debate

But giving your feedback on how you solved it might help many people in the future Thanks!

@MathieuRA The context for my question is I created an app to control my VMs and though my app said a VM started it really didn't. When I went into the logs I noticed an error, so my thought is to be able to check the logs would be helpful to find out if there is an error or not. Let me update my app because I'm thinking I can get around not having access to the logs. Thank you for the prompt response! Have a blessed day!

In other words, you can safely remove them.

@Forza you will have to switch to LATEST to profit from end month release STABLE is one version behind LATEST both are production ready.

@olivierlambert Sadly, no. And now that I'm in the middle of upgrading, I can't create storages. I could stand up an NFS server with some shared storage to help. Unfortunately, every attempt at creating a storage (NFS or otherwise) results in NOT_SUPPORTED_DURING_UPGRADE(). If I had created shared storage before I upgraded the master, I could use it. But now that I'm part-way through the upgrade process, I can't.

Great! Keep us posted

If one day, some sad soul encounters these errors and nothing seems to be working or making sense you may have the same issue I did. Back story: Earlier this year, I had a Pool with 3 hosts. Through a series of unfortunate events. The Master died, I recovered as best as I could and assumed all was well as I rebuilt the environment since all of my vm's appeared to be working (except Xen Orchestra). I tried different versions (Ubuntu, Debian, XOA, XO via Docker, etc.). Error: backupNg.runJob { "id": "ea4a9d00-db35-45a9-8a15-f700891d55c6", "schedule": "0811579b-8ad3-4f29-8581-15a35c9c4597" } { "library": "SSL routines", "reason": "tlsv1 unrecognized name", "code": "ERR_SSL_TLSV1_UNRECOGNIZED_NAME", "call": { "duration": 21, "method": "session.login_with_password", "params": "* obfuscated *" } } [image: 1765346178618-a19c2386-f194-4268-af87-3c2307bb9cdd-image.png] In my case, my database was corrupted. By rejoining host to the same damaged pool, the issue remained. In was confusing since an old instance of xen orchestra running Ubuntu 18.04 was the only instance that could run backups successfully. Newer instances could do everything except run backups. Either way, hopefully this never happens to you. If it does, your servers backend database might be the issue. Thanks again to everyone that helped me figure this out throughout the year!

I'm also trying to pass through my Intel iGPU to a VM, but running into issues. It does work on Debian, however not on Fedora Server which I'd like to use. I have tried changing to BIOS mode, even plugged in a dummy HDMI plug, but nothing helped. SELinux is disabled on Fedora to rule out any issues related to that. I even tried using XCP-NG Center which was suggested in an older post, but that didn't help either: https://xcp-ng.org/forum/topic/6211/intel-gpu-passthrough-question/3 I also posted this on the Fedora forum with further details: https://discussion.fedoraproject.org/t/intel-igpu-in-containers/176029 Are there any other things I could try to investigate this further?