New Installation ESXi 6.0 U2 does not correctly identify the workaround for eVC mode

New Installation ESXi 6.0 U2 does not correctly identify the workaround for eVC mode

Vsphere 6.0 U2 released, and the new version improves some of the errors in Vsphere 6.0 u1b, and the new version supports Vsan 6.2. The first time I downloaded and upgraded my lab environment to the 6.0 U2 version, I found some problems.

My experimental environment is composed of 4 PCs, each PC configuration, connection 1-1 is shown.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7E/01/wKioL1b07a-BLT3GAAIQvB-PmMs508.png "/>

Figure 1-1 Experimental environment

These 4 PCs were originally installed with the Vcenter Server 6.0 u1b version, which works well.

After upgrading vcenter server and ESXi to 6.0 U2, we found that the eVC of the ESXi01, ESXi02, and ESXi03 three hosts in Figure 1-1 were identified incorrectly, and the correct one should be "Intel Haswell Generation". Now, after the upgrade, the current EVC mode only recognizes "Intel Nehalem Generation", as shown in 1-2.

650) this.width=650; "Width=" 1012 "height=" 623 "title=" Snap055.png "style=" WIDTH:737PX;HEIGHT:479PX; "src="/HTTP/ S5.51cto.com/wyfs02/m00/7e/01/wkiol1b07q7hghgzaaergaezyo8921.png "alt=" Wkiol1b07q7hghgzaaergaezyo8921.png "/>

Figure 1-2 eVC mode for identifying errors

Another ESXi host, ESXi04, is identified correctly, as shown in 1-3.

650) this.width=650; "Width=" 1031 "height=" 841 "title=" Snap056.png "style=" width:803px;height:615px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/7e/04/wkiom1b07bdyovj1aafgwwlp0xo402.png "alt=" Wkiom1b07bdyovj1aafgwwlp0xo402.png "/>

Figure 1-3 identifies the correct

For this kind of error, I think it should be the CPU setting problem in the BIOS option. Entering the BIOS settings, in the CPU options, I see that the Intel VT, Intel XD bit is enabled, and only Intel Aes-ni is disabled, as shown in 1-4.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/7E/04/wKiom1b07RbBkfpdAAGLU4I10jU294.jpg "/>

Figure 1-3 CPU or Advanced chipset settings

Try to change the Intel Aes-ni to "Enabled", as shown in 1-4, and press F10 to save the exit.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/7E/04/wKiom1b07RfR-GV9AAEH-Ozn_nU103.jpg "/>

Figure 1-4 Modifying BIOS settings

Once again into the system, it is found that eVC recognition is normal, as shown in 1-5.

650) this.width=650; "Width=" 1031 "height=" 841 "title=" Snap056.png "style=" width:698px;height:555px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/7e/04/wkiom1b07bdyovj1aafgwwlp0xo402.png "alt=" Wkiom1b07bdyovj1aafgwwlp0xo402.png "/>

Figure 1-5 eVC mode that correctly identifies the CPU

For more information on Vsan, watch "VMware vsan real-start video course" with link address http://edu.51cto.com/course/course_id-5248.html

This article from "Wang Chunhai blog" blog, declined reprint!

New Installation ESXi 6.0 U2 does not correctly identify the workaround for eVC mode