@Greg_E Interesting, I've not had a play with RPUs yet, sounds pretty handy though. I can see how that could work when using Truenas as the HostOS on the Bare Metal, whereas I've got XCP-ng on the Bare Metal so I'd need to get some more machines to give that a go in due course.

@olivierlambert Using the prebuilt XOA appliance which reports: [08:39 23] xoa@xoa:~$ node --version v20.18.3

@Greg_E If you are referring to the login info admin@admin.net. That is per vates is documentation. It does prompt you to change that password. There is a xo-config.cfg file where you can change most of the defaults but those that apply to install not for do itself.

@Danp alright, thanks. I'll give that a try.

@Emmanuel-V said in Low end devices , share your experiences: I wonder to which extend we could lower dom0 memory According to: https://wiki.xenproject.org/wiki/Tuning_Xen_for_Performance Memory If the host has more memory than a typical laptop/desktop system, then do not rely on dom0 ballooning. Instead set the dom0 memory to be something between 1 and 4GB adding dom0_mem=1024M to the Xen command line. 1GB is enough for a pretty large... IIRC, I couldn't go below 1.6GB (400M was reserved for VM , maybe I should try again with the above tweak to make sure)

@tmnguyen You can open a support ticket and request that we reactivate your XOSTOR trial licenses to match your existing XOA trial.

said in Commit 109e376 Implications: we are currently drafting a procedure to make it the easiest possible. FYI: https://github.com/vatesfr/xen-orchestra/pull/9525 More details to come in upcoming weekS thomas-dkmt opened this pull request in vatesfr/xen-orchestra open docs(sdn_controller.md): document openssl 3 + sdn upgrade path #9525