@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

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)

What's the purpose of this other VNC daemon on TCP/9500? From the Xen Project wiki page on XCP: The ports used for VNC console are 5901-5999, and the ports used for text console are 9501-9599. AFAICT: TCP/5900 & TCP/9500 belong to Dom0... # xenstore-ls /local/domain/0 control = "" feature-poweroff = "1" feature-reboot = "1" feature-suspend = "1" domid = "0" name = "Domain-0" vncterm-pid = "1276" console = "" vnc-port = "5900" tc-port = "9500" vm = "/vm/7a4488c6-d4ac-4aaf-83f0-fb6d3f557f48" But I don't know how to connect to DomU #1's console because there is no entry in Xenstore for DomU #1: # xenstore-ls /local/domain/1 xenstore-ls: xs_directory (/local/domain/1): No such file or directory Ideas? Suggestions? Eric P. Reno, Nevada

@olivierlambert Refreshing the status log and updating a second time retrieves/installs more updates. After that: The '+ New' menu button appears in the menu on the left side of the window! Thank you! Eric P. Reno, Nevada