@olivierlambert You inadvertently solved this one, too, n parallel with @tony .

So, basically, as suspected, a template is nothing more than populating stuff that's in the basic and advanced webforms on Orchestra, anyway.

@tony Yes, that's the setting I was talking about. OKay. I've no idea what VIF-locking is, so I'll leave it there! Thanks again.

@tony Is that the same process which happens when I modify the network parameters within XOA's Network tab?
Thanks again.

@olivierlambert Must the RAM be hard-allocated uniquely to each VM?
I'd swear my previous hardware had 2Gb allocated to each of 4 VMs (=8Gb) but it only had 4Gb RAM.

@olivierlambert Single host: One computer in the pool. HA: Home Assistant. Probably not relevant, but I can't seem to get the right balance of useful information in support requests!

4Gb RAM and 1Gb reserved for each VM. 2 cores and 1 core reserved for each VM, but I can't run more than 2 VMs.

Thanks!

I have single XCP-ng host in my pool. It's a small footprint dual core host with 4Gb.
It contains 4 VMs (XO, Home Assistant, Linux Mint and openmediavault).
By default, XOA and HA are running. When I try to start Linux from XO, I'm told NO_HOSTS_AVAILABLE(). If I try to start Linux from xsconsole, I'm told "Not enough memory available."
No two of these VMs will be used in anger at the same time; it would simply be nice to have them all available.

Is there something I can do to get all four of them running?

(I have reduced the number of CPUs used by XO to 1, but in xsconsole, it still show 2 cores in use.)

@tony Perfect. That's exactly what I wanted. Thanks.

@tony The log showed a record of it stopping. on reflection, I think that was probably me rebooting the server, though. I don't believe it actually ever started itself. (Not even the first time after it was installed.)

Either way, It started working after I created a second VM. It's entirely possible that the suggestion of switching auto start off and on again would have fixed it.

Thanks.

@olivierlambert I don't get it. I've rebooted about 12 times in the last few days and the effect was repeatable and very predictable. Tonight, I installed an additional VM in order to see if it would autostart and .... (drum roll) they BOTH autostart. Despite my not having taken any specific action on my XOA instance.

Ho hum.

@tony I don't understand option 2. I think it's the option I want to use, but I'm told how to NOT do it. I have commandline access on the XOA VM. Thanks.

@olivierlambert OKay. I've overcomplicated this.

XOA does not auto-run. I must start it manually from xsconsole.
Once running, it runs fine.
It is set to auto-run.

In the logs, all I can see is when XOA starts up (manually) and when it shuts down (by me shutting down XCP-ng).