The XOSTOR SR will continue to operate even if the XOA is down, removed, etc.

@carloum70 You're welcome! It's always best to test using the latest source to avoid reporting an issue that has already been fixed.

@carloum70 What is your current commit? Can you show us the complete error log (check under Settings > Logs)?

The bash prompt may be displaying the incorrect time due to these lines in /etc/bash.bashrc --

# Default user timezone is EST
if [ -z "$TZ" ]
then
  export TZ=EST
fi

Are you getting the expected result if you comment out this section of code and then reboot?

@DustinB Could be. Adding more RAM to dom0 can be done if needed.

@DustinB said in Alarms in XO:

The issue is host hst150 in pool HST150 is using more than 95% of the available memory

Isn't this related to the dom0 memory, not the host's total memory?

@bikemuch As mentioned previously, you don't need a CentOS 10 template in order to deploy a VM with this newer version of CentOS. It will work just fine using a template from an earlier version of CentOS.

There is actually a good bit more available in the hub as seen in the screenshot below. You may need to register the appliance in order to access this feature.

@bikemuch Those base templates don't yet exist. You will be fine using the closest available template (ie: Centos 9 / Debian 12).

FYI, there is a cloud-init enabled Debian 13 template available in XOA's Hub.

Have you checked under Settings > Logs to see if there is any relevant information there? You could also check the XO logs by issuing journalctl -u xo-server -f -n 50 from the CLI.

There is some information available in the docs -- https://docs.xen-orchestra.com/backups#restore-a-backup

A new VM is created when you restore a VM from backup. The log entry should have a link that you can click to go directly to the new VM unless you have already deleted it, which is when the "VM not found!" message will appear.

@TheLittleDuke You mentioned that the host is now back online. Is the issue resolved or are you still having troubles with starting VMs?

• Did you try using the Start on... option on the VM's Advanced tab?
• Was the offline host the pool master?
• Are the VM's VDIs on shared or local storage?

@TheLittleDuke Please show us the full error message that you are encountering if you want help with this.

@DustinB said in Migrating logs and history between XOA instances?:

Every action that has taken place on the pool by XO, is what we were wanting to keep. But if you replace XO, you lose the logs as they are retained on the original XO.

If you are using the Audit plug-in, there is a way to move these entries to a new XOA deployments.

I assume that you are referring to other logs, like the ones appearing on a VM's Logs tab, correct?

@olivierlambert said in Update XOA OS via apt update?:

unintended updates

I think Olivier meant "unattended".

The latest XOA release is based on Debian 12. If your XOA is using an earlier version of Debian, then you should deploy a new instance of XOA to switch to the newer Debian version.

@Forza This isn't needed because the XOA VM is already performing these OS updates using unattended-upgrade.

For deployment on ESXi, you need to also do the following --

sudo -s  
cd /usr/local/bin  
curl -O https://gist.githubusercontent.com/julien-f/a6f98de3bd5a775f3f04b2fa14a9a102/raw/xenstore-read
chmod +x xenstore-read

@McHenry You always have to select a template when creating a new VM. By select the template as a first step, you will avoid this type of problem.

Are the SRs listed correctly if you first select a template?

@Vagrantin Have you tried restarting the host's toolstack with xe-toolstack-restart and then try starting the VM again?