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

@akurzawa Indeed. The XO log is how I know it stops after 10 minutes. I'm hoping for a log which will tell me WHY it stops.

When I run XCP-ng (8.2), my XOA (5.61.0) appeared not to be auto-running. Auto-run is checked. On inspection of the XOA log, I can see that it does start, but then stops again about 10 minutes later.

*** EDIT: I think the log that it was stopping was me rebooting the server.
On reflection, it was simply never auto-starting. ***

xsconsole says XOA is "Unavailable". If I manually XOA from xsconsole, it runs perfectly well and keeps running.

Does anyone have any idea what's going on, or is there an enhanced log I can look at?

Thanks.

Cancel that. CTRL-F5 fixed it! Thanks again.

That's what I thought. I registered with that service a few months ago when I started using XOA. I used the same details today as last night, and it appears to have "registered" me. (Or more probably my instance of XOA.)

It says I's on a trial and it's going to time out in 2 weeks. I've not seen that before. What does it mean to upgrade my appliance? There is a green "Upgrade" button, but it's greyed-out.

Thanks.

@olivierlambert I should say the reason for being reluctant to register was that I already had done. I think there was something up with the XOA service yesterday: I did enter my registration details three of four times last night without success.

@olivierlambert There's no reason why I wouldn't I thought I was registering MYSELF. I did not realise I required to register the application instance. I've installed XOA several times on the one piece of hardware as I was finding my feet and didn't have to register repeatedly.

It now says I'm on a trial period. This is also new to me.

@olivierlambert I've ceased using my previous hardware. Do I need to register this as a new instance? Thanks.

Through no action on my part (that I know of) today it seems to be working, BUT, only after I manually star the XOA VM.

After bootin xcp-ng, xsconsole tells me that the XOA VM is "halted." In the Advanced Tab, it is set to "Auto Power On". The log says "VM_SHUTDOWN" about 11 minutes after it powered up.

Has anyone any clue what might be going on, or where I should look for a detailed log file?

I've just moved XCP-ng (8.2) onto fresh hardware. Having installed XOA (20210823), I can't do anything in the web GUI. I'm told "Your xoa-updater service appears to be down. Your XOA cannot run fully without reaching this service." I have entered the correct email address and password.

If I Check XOA, I see:

 Appliance registration: [Error: ENOENT: no such file or directory, open '/var/lib/xoa-updater/registration.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/var/lib/xoa-updater/registration.json'
}

I'm not sure if it's related, but this installation has also ben affected by the EFI_MEMMAP issue, but I'll raise that in a separate question.

Can anyone give me a pointer, please?

I'd like to help: I plan to test this against my Mint Linux 20.1 VM and my openmediavault 5 VM.
Question on "3.3 clean shutdown and reboot working". Any time I shutdown XCp-ng, I normally shutdown each VM first. Since I have guest tools installed, should I be able to simply shut down XCP-ng and rely on it to politely shut down my VMs?
Thanks.