That's weird, but OK. Maybe it's because even when you update, the old/existing RRDs data won't be "replaced".

Yes, even if there no code, there's a lot of pushing on our end to make it happen on their side

Thanks for engaging! In this thread I would say: Storage I need it to get ISO files uploaded without going native (CLI). Or in other words, the basic stuff you would expect of a web-interface to be able to launch working VM's.

I have no idea what this flag is doing, so my gut feeling is: no, it's not on XO side but a "problem "on the reverse proxy itself.

@Andrew said in XOA suddenly "empty" during rolling update: @halvor Yes, kind of... The pool master must be updated and rebooted first. If you move the master to a different host then you are no longer rebooting the pool master first. XOA is just a very smart client and needs the pool master to provide all of the pool information. Secondary machines will just redirect to the master, so if you try to connect XOA to one as a backup it won't work. You just need to wait for the master to reboot and return to a functioning state and wait for XOA to automatically reconnect. The everything will start happening again. If your master host is destroyed (ie. software corruption, hardware failure) then an existing host can be forced to take over the pool as master, but this is not a good thing to do unless the actual pool master is unrecoverable. Ok, great, thank you for clearing this up!

Hello, thank you for your reply @bogikornel @TrapoSAMA . Here are my processor specifications: Intel Xeon E5-1620 v2 (8) @ 3.691GHz. Unfortunately @Andrew , I have to use RHEL 10 on my server ^^ but thank you for providing the link. I will change my processor/server.

@bryonadams said in Trouble Creating VM via API: Is there a place I can submit a feature request to allow setting a description and other settings from the UI to get feature parity when creating a VM? Otherwise, there's not much point since I have to go in and touch the new VM anyway. Unless I'm going about this wrong to begin with? You can create a feature request on Xen Orchestra github repository (https://github.com/vatesfr/xen-orchestra/issues), and if you have subscribed to support via XOA you can send a request through Zammad.

@Forza said in MegaCLI and StorCLI lastest version for 8.3 LTS: @jangar don't they have a statically linked version of storcli that can be downloaded? latest version is for min RHEL 8x i have older version https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/8-07-14_MegaCLI.zip and https://docs.broadcom.com/docs-and-downloads/007.2705.0000.0000_storcli_rel.zip i've installed them and seem work, but i'm not sure other command thank check raid status work tomorrow. wget https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/8-07-14_MegaCLI.zip unzip 8-07-14_MegaCLI.zip rpm -ivh Linux/MegaCli-8.07.14-1.noarch.rpm alternatives --install '/usr/bin/MegaCli64' 'MegaCli64' '/opt/MegaRAID/MegaCli/MegaCli64' 1 alternatives --install '/usr/bin/MegaCli' 'MegaCli' '/opt/MegaRAID/MegaCli/MegaCli64' 1 alternatives --install '/usr/bin/megacli' 'megacli' '/opt/MegaRAID/MegaCli/MegaCli64' 1 wget https://docs.broadcom.com/docs-and-downloads/007.2705.0000.0000_storcli_rel.zip unzip 007.2705.0000.0000_storcli_rel.zip cd storcli_rel unzip Unified_storcli_all_os.zip rpm -ivh Unified_storcli_all_os/Linux/storcli-007.2705.0000.0000-1.noarch.rpm alternatives --install '/usr/bin/StorCli64' 'StorCli64' '/opt/MegaRAID/storcli/storcli64' 1 alternatives --install '/usr/bin/StorCli' 'StorCli' '/opt/MegaRAID/storcli/storcli64' 1 alternatives --install '/usr/bin/storcli' 'storcli' '/opt/MegaRAID/storcli/storcli64' 1

Yes! That's a good guide for what you want to achieve

Hmmm that's a possibility. An interesting lead to explore. Ie trying to do it yourself to see if the result if the same?

Yes, the old method should work

@CodeMercenary hello and thanks for this idea! We will discuss about it with @clemencebx and see what we can propose on new XO-6 design and workflow.

@planedrop While you are connected to the XOA VM, be sure to verify that the required changes have been performed on /etc/systemd/system/xo-server.service when the VM memory was increased. Details can be found in this troubleshooting KB article -- https://help.vates.tech/kb/en-us/31/48

@DustinB Hmm - just got done running mem86+ - 4 passes -- all 14 tests. No RAM errors. I wonder the what would cause this error? I'll probably just save config and reinstall. So strange.

@Danp UEFI

@acebmxer Hello, We’re aware of the Backblaze rate limits and this isn’t the first time it’s been raised. We’ll be looking into this on the XO side, studying different options such as caching restore points to reduce API calls. Longer-term improvements, possibly tied to advanced XO6 dashboards, are more of a 2026 horizon. Thanks for bringing this up!

Hi, Small side note: lately I’ve noticed that some posts look like they were generated by LLMs. This can actually make it harder for the community to help, because the text is often long, unclear, or missing the basic details we really need to assist. I’d really encourage everyone to write posts in their own words and share as much relevant information as possible. The real value of this community is people helping each other directly

On DOM0 (host xcp-ng) traffic is filtered by iptables. So iptables -L will show which ports are open. Everything else will be rejected by default. For testing, you can stop iptables. If that helps, add rules. Keep in mind that XCP-NG is based on CentOS. So you can easily find an answer on Google for any question.

@DustinB Guest tools simply don't support the system I'm running.

@tmk said in Cloudbase-init on Windows: @jkatz I ran into the same issue when trying to configure a network adapter with cloudbase-init. The documentation says that the MAC address value is optional but in reality it is required. In my case I want Xen Orchestra to choose a unique MAC during deployment, and I since I am deploying from a template, the NIC name is a known value. The fix that ended up working for me was to modify the networkconfig.py file in cloudbase-init so that the NIC name is required and the MAC address is optional. I ended up making some additional changes to allow for the network-config v2 format along with the existing v1 support and some additional logic to aid in setting the dns search domains (I can't recall if this was originally supported or not but I had issues getting it to work with the original networkconfig.py file) This file needs to replace the existing one that is installed in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Lib\site-packages\cloudbaseinit\plugins\common\ directory. To replace it you should make sure that the cloudbase-init service is stopped, then replace the file. Once this file is replaced, delete the pycache folder in the same parent folder as networkconfig.py - this will ensure that python recompiles this file on service start. Start the cloudbase-init service and confirm that you see a new pycache get created. I'm not a python programmer by trade so others may be able to point out areas for improvement but this ended up working for me and I wanted to share in case it could help others needing to deploy new servers without manually specifying a new MAC address. Below is an example network-config v2 format that works with the updated file. version: 2 ethernets: Ethernet 2: dhcp4: false addresses: - 10.20.30.10/24 nameservers: addresses: - 10.20.5.12 - 10.20.5.13 - 10.20.5.14 search: - intranet.domain.org - domain.org - public-domain.org routes: - to: default via: 10.20.30.1 Updated networkconfig.py file: networkconfig.py.txt Thank you for posting! I followed your directions verbatim and I'm still having trouble getting the network config to take. Does it work with Windows Server 2025?