Install ESX server 3.5/3i onto ESX Server Installation Method _ website Application

# in the following article, the ESX server, which is installed directly on the hardware, is called "Host ESX Server", and the ESX server installed on the Host ESX server is called "Guest ESX server"

1. Do the guest ESX server settings

Just like installing other guest OS, connect to host ESX Server via VI client or VirtualCenter and create a VM. When created, the OS type selects "other", the VCPU is 2, and the memory is 1GB or more.

2. Change the NIC type to e1000

After creating a good VM, don't rush to install it.
When you install the guest ESX server, the default AMD network card is not recognized by the ESX server, and you need to manually edit the. vmx file to change the NIC type to "e1000" that ESX server recognizes.

Log on to the service Console of host ESX server, locate the. vmx file of the created VM under/vmfs/volumes/, and add the following lines in the VI editor:

Ethernet0.virtualdev = "E1000″

Here, Ethernet0 is the first virtual network card, if you set up a VM with more than one network card, you need to set up separately. Once set, you can confirm it by booting the VM boot menu.

Default NIC type: AMD am79c970a

Changed NIC type: Intel E1000

3. The CPU of Host ESX server hardware must support VT (virtualization Technology) (if it is an AMD CPU, it is amd-v)

Intel's VT or AMD's AMD-V is a technology that provides virtualization support at the CPU level. When you install a 32-bit operating system on ESX server, such as Windows XP, turning on or off the VT feature does not affect performance, but when you install ESX server on the ESX server, no VT is used to make the ESX Server virtual machine startup time slows down to more than 10 times times.

(I am not open VT, in a dual Xeon CPU,12GB memory Esx server 3 on the installation of ESX server 3i, after 4 hours of 100%cpu occupancy rate I gave up)

4. Open the back door of VMware

To make ESX 3.5/3i run smoothly on the host Esx server, you will also need to open the "back door" of VMware, or you'll likely see "purple screen" in VMware (which can match the "blue screen" in Windows).

To open this backdoor, allow the ESX Server to be installed on the virtual machine and add the following two lines to the. vmx file:

Monitor_control.vt32 = "true"
Monitor_control.restrict_backdoor = "true"

This backdoor not only avoids the "purple screen" and so on, instability, and so on, but also the starting speed is raised 10 times times. It took me 30 minutes to start the guest ESX server with VT, and it took only 2 minutes to open VT and open the backdoor options.

5. Allow promiscuous Mode on host ESX server

After doing the above, you should be able to successfully install the guest ESX server. However, after the installation has been started, it is found that it cannot be managed through VirtualCenter-even the service console ping Guest ESX server does not ping! What is this for?

The reason is that the vswitch settings for the guest ESX server are connected to the host Esx server. Vswitch default is to not allow promiscuous mode (which allows the NIC to listen for packets destined for other MAC addresses). However, in the guest ESX server, the NIC is only a bridging (bridge) function and does not bind directly to the MAC address. Therefore, the promiscuous Mode,host ESX server must be allowed in the Host ESX server to properly deliver the package to the guest ESX server's service Console (3i is managed with IP).

Here, you can experience the magical world of Esx 3.5/3i.

-->