Thank you! So in this case, if better option for me to join the hosts to existing pool and then shutdown VMs and start it on host with older CPUs. Thank you again!

Thanks!

We are not energy efficiency experts, while EasyVirt people are. I think they already have some stuff and it might be just a matter of plumbing.

@Bastien-Nollet new day without false INTERRUPTED [image: 1767808672598-94dbb451-6567-4d1e-af0a-6d28573416bb-image.png] the scrutiny of backup email reports made me find a new bug in backups (not reports this time) i'll create a new topic about the dreaded BACKUP FELL BACK TO A FULL --> can provoke it on purpose !

@andSmv I definitely think it would be nice with support even though i repurposed my M2 Coral for other uses. But one thing to keep in mind regarding resources is that the product would appear to be heading to https://killedbygoogle.com coral.ai redirects to their new NPU offering and no updates have been made from google to the driver since 2022... Mouser still has plenty of stock though. Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either.

@florent, I had to do the same for Xen Orchestra Community Edition. In my case, config.toml already contained the [authentication] section, so adding a separate config.tokenValidity.toml file did not work. Instead, I had to modify the existing config.toml located at /opt/xo/xo-server. In my opinion, it is best to keep defaultTokenValidity set to 30 days as a fallback in case no value is specified. You can then simply increase maxTokenValidity to the duration you prefer. [authentication] defaultTokenValidity = '30 days' # default value of 0.5 years # comment out and increase to 5 years #maxTokenValidity = ' 0.5 year' maxTokenValidity = '5 year'

@bvitnik Thanks for giving more details. I will give a try with each of them (netplan, ..etc)