Archive for the ‘ESX 3.5’ Category
Posted by Marek.Z on 21 June 2010
“Turn off what you do not need” is my motto 
. So, if you are not using the VMFS-2 (which you probably aren’t using since ESX 3.x) and/or NFSClient in you environment than you can safely unload these modules from your ESX host. You can list currently loaded modules with #esxcfg-module –q and if you want to disable the modules mentioned above then:
- Login to you ESX host as root user
- First, unload the modules by typing:
- #esxcfg-module –u vmfs2
- #esxcfg-module –u nfsclient
- Next, disable the modules:
- #esxcfg-module –d vmfs2
- #esxcfg-module –d nfsclient
- Reboot your ESX host: #shutdown –r now
- After reboot, login and verify that the modules are not loaded by typing: #esxcfg-module –q |more
- Logoff your ESX host
If you want to load the disabled modules, simply use the esxcfg-module –e <module_name> command and reboot the host.
Cheers!
Marek.Z
Posted in ESX 3.5, ESX 4, VMware | Leave a Comment »
Posted by Marek.Z on 18 June 2010
The tail command displays last 10 lines of a file and with the –f (follow) parameter you can see the data appended to it. So, if you want to see what is going on in the vmkernel of your ESX host:
- Login to you ESX host
- Type: #tail –f /var/log/vmkernel
- Watch for new events to appear
- If you want to terminate the process, press CTRL + C
Nice & simple
Cheers!
- Marek.Z
Posted in ESX 3.5, ESX 4, Uncategorized, VMware | Leave a Comment »
Posted by Marek.Z on 11 February 2010
If you want to kill an unresponsive VM on an ESX server and it cannot be turned off with the vmware-cmd stop hard command then try the following:
- Logon the ESX server as Root and type: #vm-support –x to find the VMID of the unresponsive VM.
- Next, type: #vm-support –X <VMID> to kill the VM. Answer the questions as desired and wait until the ESX server finishes the job.
Cheers!
- Marek.Z
Posted in ESX 3.5, ESX 4, VMware | 1 Comment »
Posted by Marek.Z on 24 September 2009
I have encountered this error after a clean installation of ESX 4 server on a new HP DL 380 G6. When you access your ESX server through web interface and you try to log in by clicking on the “Log in to Web Access” link, you get the “503 Service Unavailable” error in your web browser. Here is how I solved this issue:
- Log in to the console of the affected ESX server (or through puTTY) and check the status of the vmware-webAccess service by typing: #service vmware-webAccess status
- If the service is not running, start it with: #service vmwware-webAccess start
- If you want to start this service automatically when your ESX server starts, type: #chkconfig – - level 3 vmware-webAccess on
- Now, try again to log in to the Web Access of you ESX server and the issue schould be solved.
Cheers!
- Marek
Posted in ESX 3.5, ESX 4, VMware | 4 Comments »
Posted by Marek.Z on 11 September 2009
Follow these steps to start or stop a VM from the CLI of your ESX server:
- First, find the full path to your virtual machine by typing: #vmware-cmd -l
- To start a VM type: #vmware-cmd <path to your VM> start
- To stop a VM type: #vmware-cmd <path to your VM> stop (hard). This option is optional. It will force a hard stop of your VM.
Cheers!
Marek
Posted in ESX 3.5, ESX 4, VMware | Leave a Comment »
