Hi, All.

@splastunov Never ran across this before, that's for that screenshot, and command. When I'm able to I'll for sure give this another shot and check these.

@splastunov By 7.3.0 i meant the package version and that version was also in xcp-ng 7.4 so if the package was there and its license hasn't changed since i would assume it means its still free to use.

An update candidate has a fix for this and should be published tomorrow as an official update.

@christopher-petzel Many thanks saved me from hours of searching for a fix

@olivierlambert ah good to know thats fine I'll take a look at the metrics maybe I'll write a small rrd stats pusher script as an interim solution for my usecase until XO6 is available. Thanks for letting me know

@stormi thanks, will look forward to try this out when the update drops.

@MrXeon So, the actual root issue here I believe, is opnsense installs come with an IP and dhcp server already assigned and enabled on the lan interface (I believe it's 192.168.1.1, but don't quote me). If your existing home network already uses 192.168.1.x/24 and already has a dhcp server, booting an opnsense install with it's virtual lan nic set to your existing home lan, there will be a lot of conflicts. Virtual nic order can be whatever you'd like (you can change and move around assignments in opnsense), but if it's preconfigured lan interface gets set to your preexisting lan network, there will be conflicts

@gnpcx What did you end up doing for this? The docs dont seem to have any guidance.

Its not solving it, but you can run echo 3 > /proc/sys/vm/drop_caches to release some of the cache again, without interfering with running processes. [root@host2 ~]# free -m total used free shared buff/cache available Mem: 15958 3308 158 8 12491 2355 Swap: 1023 177 846 [root@host2 ~]# echo 3 > /proc/sys/vm/drop_caches [root@host2 ~]# free -m total used free shared buff/cache available Mem: 15958 3308 2598 10 10051 2751 Swap: 1023 177 846

Agreed, but the downside is to update the template from time to time. We'll probably create a new Packer plugin to work with XO API, so it will be easier to use and rely on (Packer goal is to prep' a template from scratch and up to date for you, that you can use for solution 2. then)

@epretorious I would add that you have to be careful about overprovisioning when NUMA/vNUMA kicks in, that is when you allocate more VCPUs to exceed the number of physical CPUs of a bank of them as well as the associated physical memory (assume, for the sake of argument, you have two banks of physical CPUs and each has directly accessible to it one of two banks of memory) then things get inefficient because a CPU may need to go across to a different bank of memory to access data and there is additional overhead involved. See for example this article and the two preceding it: https://blogs.mycugc.org/2019/04/30/a-tale-of-two-servers-part-3-the-influence-of-numa-cpus-and-sockets-cores-persocket-plus-other-vm-settings-on-apps-and-gpu-performance/ -=Tobias

@Gheppy Thank you very much for the quick reply. I thought so indeed. Will this also be the case running Workstation using Linux?

@olivierlambert its looks like it was not from XCP but from the cloud provider managing it (Cloudstack). as soon as max restrictions were removed i could assign all 128 threads as vCPUs to a single VM.