Skip to main content

ESXi 6.5.0 fails to start a VM with a message "Maximum virtual machines limit reached: ## (#### worlds)"

By

Maximum virtual machines limit reached: ## (##### worlds)

ESXi 6.5.0 by default determines the maximum number of VMs dynamically at runtime. In certain scenarios this might be too conservative and you will not be able to start a virtual machine. If you are observing a message like below when starting a VM then you have hit the limit.
Maximum virtual machines limit reached: ## (##### worlds).
This behavior is controlled by VMkernel.Boot.maxVMs in Advanced settings. Change this to a value that might be reasonable based on CPU, memory and network capacity. The same setting can be changed from SSH shell like below: 
[root@localhost:~] esxcli system settings kernel set -s maxVMs -v 1024
Reboot the server for this change to take effect.
Tag: ESXi
Labels:

Comments

Post a Comment

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

By
Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re
11 comments
Read more

The following add-ins could not be started MonoDevelop.GnomePlatform

By
Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.
21 comments
Read more