I ran across this the other day while onsite at a customer. After performing an upgrade from ESX 3.5 to vSphere 4, the console would show the message:
"Significant Imbalance between NUMA nodes detected. Performance may be impacted."
I ran across this the other day while onsite at a customer. After performing an upgrade from ESX 3.5 to vSphere 4, the console would show the message:
"Significant Imbalance between NUMA nodes detected. Performance may be impacted."
This lesson describes how to reset a lost password on vSphere 4 and ESX 3.x. This information is based off of VMware KB article 1317898 which can be found here:
http://kb.vmware.com/kb/1317898.
1.Reboot the ESX host.
2.When the GRUB screen appears, press the space bar to stop the server from automatically booting into VMware ESX .
3.Use the arrow keys to select Service Console only (troubleshooting mode).
4.Press the 'a' key to modify the kernel arguments (boot options).
5.On the line presented, type a space followed by the word single.
6.Press Enter. The server continues to boot into single-user mode.
7.When presented with a bash prompt such as sh-2.05b#, type the command passwd and press Enter.
8.Follow the prompts to set a new root user password.
9.When the password is changed successfully, reboot the host using the command reboot and allow VMware ESX Server to boot normally.
1.Reboot the ESX host.
2.When the GRUB screen appears, press the space bar to stop the server from automatically booting into VMware ESX .
3.Use the arrow keys to select Service Console only (troubleshooting mode).
4.Press the 'e' key to modify the kernel arguments (boot options).
5.On the line presented, type a space followed by the word single.
6.Press Enter then press the 'b' key to boot the ESX host in single-user mode.
7.When presented with a bash prompt such as sh-2.05b#, type the command passwd and press Enter.
8.Follow the prompts to set a new root user password.
9.When the password is changed successfully, reboot the host using the command reboot and allow VMware ESX Server to boot normally.
1.Reboot the ESX Host.
2.When the LILO screen appears, press the space bar to stop the server from automatically booting into VMware ESX.
3.At the LILO prompt select linux, adding the -s to the end of the line. For example: linux -s.
4.Press Enter. The system begins to boot. The server continues to boot into single-user mode.
5.When presented with a bash prompt such as sh-2.05b#, type the command passwd and press Enter.
6.Follow the prompts to set a new root user password.
7.When the password is changed successfully, reboot the host using the command reboot and allow VMware ESX to boot normally.
If there are disk array or networking issues in VMware ESX 3.x or vSphere, some virtual machines (VMs) may appear in the vSphere Client as being Invalid and are greyed out. The following steps will fix this issue.
When using Virtual Machines (VM's) from other VMware products, the easiest way to get these VM's into ESX/vSphere is to use VMware's product called vCenter Converter Standalone. vCenter Server does include a version of Converter, however I've had better success in using the standalone version to do VM conversions as it is (typically) a newer version with more features than the one included with vCenter. This lesson describes how to use vCenter Converter Standalone to import VM's or VMDK files from other VMware Products, such as VMware Fusion, VMware Workstation and VMware Server.
