I just want to add that I am seeing the same issue with Ubuntu 24.04.3. Creating a VM does work, but it crashes immediately when trying to start it for setup. I have not yet tried the approach of starting with 24.04(.00) and then upgrading to the lastest version due to lack of time. We are still using XCP-NG 8.2.1 on the server in question. If an upgrade to 8.3 solves the issue, please let us know. Reading the thread, it appears to have the same problem, though. Processor is an AMD Ryzen 9 3900X. We have not had any other issues with the system and it's been running for a few years.

My current findings regarding this: https://github.com/xcp-ng-rpms/microsemi-aacraid/issues/2 0nelight created this issue in xcp-ng-rpms/microsemi-aacraid open Microsemi Adaptec Series-8 Card not working in XCP-NG 8.3 #2

@jkatz So everyone is cleared since I just experience the same issue not allowing me to create a new vm using the template. Before you use the Windows 11 Template and you have it with SYSPREP ready. You need to go down to advanced and make sure you delete the VTPM [image: 1769552292859-5d61aad5-013e-4cff-af7c-adbb4c4ca809-image.png] then create the Template. Once you create the vm again you will not receive the error and a vtpm will be created for the new VM with no issue. Hope this helps.

I had the same question but the responses here was amazing and the following blogpost nailed it. I hope it helps someone else too: https://techdirectarchive.com/2026/01/25/a-z-of-xcp-ng-and-xen-orchestra-setup-and-vm-creation/

@majorp93 I've updated and added a node.js-installation to the role. Targeting the LTS-24 version. I hope you find it to your liking.

@wlp94114 said in Intel x710-t2l Problems: The x710 series has a reputation for being picky about driver and nvram versions. Out of curiosity, is there anything reported by the linux driver that would allow make the situation obvious?

@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'

Resolved by rebuild, and doing VM backup and metadata to trunas dataset.... Start Backup earlier. Be better then me

@dalem That looks awesome ! Glad to see nix/nixos getting more and more adoption. It must have been a pain to build the pkgs, thanks a lot for working on this. I'll give it a try when I manage to free some time. Have you considered upstreaming the module/pkgs to nixpkgs or is this too much work ? I have not contributed there yet so I don't know if it would get merged as is.