No Hosts Available When Creating New VM

kagbasi-wgsdac

Good-day folks,

I'm running into the following error when attempting to create a new VM via XO:

NO_HOSTS_AVAILABLE()
This is a XenServer/XCP-ng error

Unfortunately, there's nothing else in the log. I've already rebooted the host, and XO, still the problem persists. Anybody else seeing this on their system?

My Environment:
1 Pool, 1 Host
Git commit 42432
xo-server 5.103.1
xo-web 5.104.0

olivierlambert

Try to boot the VM with xe vm-start uuid=<UUID> to get more details.

Likely not enough memory to boot the VM here or something similar.

kagbasi-wgsdac

@olivierlambert That's what's strange, Olivier. The host has enough RAM (about 20GB of 64GB available). I can stop and start existing VMs without any issues.

The problem I'm having is specifically with trying to create a new VM from the XO UI. I will try using xe to create it from the CLI and see what happens.

olivierlambert

No need to create the VM with xe. Create it with XO, just uncheck "boot after create". Get the UUID, and then just xe vm-start uuid=<VM UUID> in XCP-ng.

kagbasi-wgsdac

@olivierlambert Thanks for that information, will use it next time I run into the issue.

Before I read your above reply, I was poking around and noticed that the only SR I had added was disconnected, somehow. So I researched into it and discovered that this was my own doing. Without going into too much detail, I had converted my Active Directory environment from a Zentyal server to a Windows Server and I was hosting the SMB share on the old domain controller. So I had made a DNS error which was causing the SR to not be reachable from the XCP-ng host.

So I deleted the SR and recreated it and viola I was able to create the VM. Honestly, I'm not sure how the two are connected since I'm not storing any disks on this SR; I only use it for ISOs which I mount into the newly created VM to install an OS and then I eject it.

Long story short, my problem is solved but I'm still confused as to how it happened.