Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
ESX 4.1 host stops booting at: * vmnix ... (2030715)
Symptoms
- ESX 4.1 host fails to boot
- ESX 4.1 host fails to boot with this message on the screen:
* vmnix ...
Cause
If there is a double-byte character in /etc/vmware/esx.conf (for example, "" ), ESX fails to boot.
For example, this command caused the esx.conf to be updated incorrectly:
esxcfg-firewall --openPort 162,udp,in,"snmptrap”
The correct command is:
esxcfg-firewall --openPort 162,udp,in,snmptrap
Resolution
To resolve this issue:
- Boot the ESX host and select Troubleshooting mode on the Grub menu.
- Log in to the host as the root user. For more information, see Connecting to an ESX host using a SSH client (1019852)
- Make a backup of the esx.conf file:
cp /etc/vmware/esx.conf /tmp/esx.conf.bkup
- Open the esx.conf file for editing:
vi /etc/vmware/esx.conf
- Find the double-byte characters and remove the characters. For example, change:
/firewall/openedPorts[0003]/name = ""snmptrap""
To
/firewall/openedPorts[0003]/name = "snmptrap”
- Save and close the file.
- Restart the ESX host.
See Also
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

