– Connect to your ESXi with vSphere client and if necessary, enable SSH by going to configuration > security profile > properties > ssh and start the SSH service.
I have experienced recently some issue while attempting to start vmware machines on Centos OS. (6.6).
When I start the vmware services, (service vmware start) the Virtual machine monitor states as FAILED.
Attending to start a vmware, this error appears:
Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded.
I have been using a script for a while switching off the esxi to a certain time. Crontab in used to do it, as this post
Unfortunately, this script does not do much than poweroff the vms and switching off the esxi; As a consequence the vmware’s running at that time would have been stopped roughtly;
All the work done would have been lost, so I decided to review this script to do the following;
– List of Machines currently running
– Retrieve ID’s for each Machines
– suspend command for each IDs.
– Then Poweroff the Esx(i).
- Boot OS X
- Open the TextEdit program in the Applications folder
- With TextEdit, open the file: /Library/Preferences/SystemConfiguration/com.apple.Boot.plist
- Open the file, and add these two lines (right after the <string>Yes</string> line if you are on Tiger or <string></string> line if you are on Leopard)
This script does the following:
- List of the current machine’s name based/stored on the target destination.
- Ask for the name of the new machine.
- Type of machines (Windows 2003 / Centos / etc…)
- Create the image based on the template’s machines.
- Register the vm into the Vsphere inventory.
- Asking you if you wish to start or not once created.
This script would be using two commands available on the esxi.
- /sbin/powerOffVms (Stop the current's running vms)
- /bin/poweroff (Stop the Esx host)
Once you have installed VirtualBox, you need to configure the Network
Https.vmware failed to start and it gives you this type of message:
Starting httpd.vmware:-ne failed
Open the vmx file that belongs to your vm machine
Add these two line into the file: