@Thiago_FS_Dantas hi, did you check NESTED VIRTUALISATION in the advanced tab of your VM ? [image: 1767872120619-3f93e473-b1eb-4a92-aca7-a684ff9a23ae-112fdd1c-a3bf-4636-81a9-f24aecd818f7.png]

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

Hi! Thanks for the feedback. Can you be more specific? This might be helpful if others would have the same issue Thanks!

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