Failed to create system : No suitable running host systems are available

We searched for this problem and all we could find was Add System > Add Physical System. However these options do not exist on my cloudmin system.

Hosting with Hetzner. Used install script for gpl license. Completed with no errors.

Can you please point me in the right direction.

Thank you. Ettienne



So are you running the single-system GPL KVM version of Cloudmin there?

Forgot to mention I'm using Xen.

On the host system I've got virtualmin, cloudmin & webmin installed. Please see image below for a screenshot: On the left menu you can see status: virtualmin which means what exactly?

The status of "Virtualmin" means that Cloudmin can see/access Virtualmin running on that VM.

Just to clarify though, is it Cloudmin Pro or GPL that you're using there?

This message can also mean that Cloudmin thinks that your system isn't ready to host VMs because something is missing. If you go to the "Edit KVM Host" from the left menu, does it display any errors?

I don't have "Edit KVM Host".. Also, everything installed is GPL..

All I got is "Host Systems" > "Xen Host Settings" & "Ip Address" Or "New System" > "Add Xen Instance" & "Create Xen Instance"

Sorry, I meant "Xen Host Settings". If you visit that page and click "Save", does it report any errors?

Nope I've done that multiple times. It saves successfully and goes to "Cloudmin Managed Systems". I only get an error on "Create Xen Instance".

I wanted to click "De-Register" button and redo the host, but not really sure if that will help or make things worse..

There's not other errors and that is the problem nothing to fix.

Please tell me if I purchase a cloudmin license, would I have to re-setup from scratch?

One thing you could try is creating a VM from the shell by running the cloudmin create-system command as root - this should output a more useful error message.

The full command will be something like :

cloudmin create-system --type xen --host yourvmname --image some-image-name --ssh-pass foo

Ok got an error:

Host system cannot be used : Only 32.01 MB RAM would be free after creating this system, but the minimum is 2 GB

Please can you explain to me what the following settings under: Xen Host Settings > Virtual system resource limits > Memory to leave free?

I can make it anything I want but still get the error? We've got 24gb on this server but unable to create one instance..

I tried to allocate memory to the plan or make it unlimited but still gives error. In the cloudmin documentation all I can find is just another option (resource > resource limits) which does not exist in my cloudmin.

Make sure that the "Memory to leave free?" is set to something reasonable, like 1 GB - just enough to allow Cloudmin itself to continue to run.

Also, make sure that when creating the VM that you enter a reasonable RAM size, like less than 20 GB.

[ ]#cloudmin create-system --type xen --host --image xen-centos6.0-base --xen-memory 1000 --owner in2fowner --ssh-pass 123456

Host system cannot be used : An extra 693.04 MB free RAM is needed to create this system

Looks like it's saying I can only make a system with less than 300mb? Why is that? Where do you set how much can be allocated per system? I also tried with 512mb then the error states 203.27 MB free RAM needed.

Tried to set the account plan to 10gb and tested the unlimited option, but no change in the error.

It must be a xen limitation somewhere for per xen instance?

So I tried to create a 300mb memory vm, see below:

]# cloudmin create-system --type xen --host --image xen-centos6.0-base --xen-memory 300 --owner in2fowner --ssh-pass @wsXzaQ1

Host system cannot be used : Only 10.23 MB RAM would be free after creating this system, but the minimum is 1024 MB

It looks like Cloudmin is getting the RAM available for Xen hosting wrong - perhaps because not all the RAM on the system is usable by Xen. I would be interested to see what the xm info command outputs on your system..

Thanks te create instance helped me diagnose the problem. So eventually I got the vm instance created and started. However the status I get now is ping failed.

I can only use the graphical (VNC) viewer in cloudmin to get into the vm. Not through the net. Any ping requests return with unknown host or could not resolve..

The resolv.conf is fine, exactly like on the host.. Also on host it shows ifconfig vif was created for the vm but I don't see any ip addr for the vif?

I previously reserved the additional ip on the host via adding eth0:1 which is probably not working for xen as then the ip becomes taken and unable to use with instance. But even if I remove it and restart xend and the vm then the recreated vif stay the same without any ip/netmask or broadcast config..

I can connect via ssh to that ip or the resolvable hostname however I only to end up logging into the host machine and not the vm guest system.

Then can you tell me what is the peth0 interface that gets created automatically? it also doesn't contain any ip addresses..

What could be wrong, does it have to do with the bridging? or perhaps something to do with my host (hetzner) routing..?

I'm so close, any help you could provide would be greatly appreciated. Would gladly provide root access to you, just let me know.

Thank you. Ettienne

Sounds like a routing issue - make sure that on your VM, a default gateway is set (it should be visible with the netstat -rn command), and that the gateway is reachable from the VM's IP address.

Yes I'm unable to find gateway or any other local address.. so netstat -rn gives no result, no entries..

My ifcfg-eth0 on the vm is as follows:

BROADCAST=        (on the host this usually is "scope")
NETWORK=           (I never specified this ip anywhere, was generated)
GATEWAY=           (Also on the host this gateway not located in eth0, it's in route-eth0)

That config file looks OK - I assume that on the VM that ifconfig shows an IP address for the eth0 interface?

I can ping the host from DOMU, I setup network-route & vif-route in xen conf.
The vm Status is: SSH..

So only problem is getting to the internet. Host doesn't seen to allow the guest system.

See following on DomU:

# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface U 0 0 0 eth0 U 0 0 0 eth0 UG 0 0 0 eth0

Ping the host:

# ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.085 ms
64 bytes from icmp_seq=2 ttl=64 time=0.062 ms

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:56:00:79:F2
inet addr: Bcast: Mask:
inet6 addr: fe80::250:56ff:fe00:79f2/64 Scope:Link
RX packets:12214 errors:0 dropped:0 overruns:0 frame:0
TX packets:17535 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1824384 (1.7 MiB) TX bytes:2956267 (2.8 MiB)

lo Link encap:Local Loopback
inet addr: Mask:
inet6 addr: ::1/128 Scope:Host
RX packets:3502 errors:0 dropped:0 overruns:0 frame:0
TX packets:3502 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:290876 (284.0 KiB) TX bytes:290876 (284.0 KiB)

Following on host:

# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface UG 0 0 0 eth0 UH 0 0 0 eth0 UH 0 0 0 vif8.0 U 0 0 0 eth0

The Vif on host:

vif8.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr: Bcast: Mask:
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
RX packets:17539 errors:0 dropped:0 overruns:0 frame:0
TX packets:12218 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:2711057 (2.5 MiB) TX bytes:1995716 (1.9 MiB)