Hyperthreading was Inactive in VMware esxi 6.0.0


Hi Friends,

Problem:- If we are facing problem with Hyperthreading was inactive in VMware Esxi 6.0
  1. After updating the Esxi 6.0.0, 3620759 host with  new patches the new build 15169789 We are facing this issue.
  2.  The logical processors are reduce to 20 actually it was 40
  3. It was problem with Intel Processors Affected Intel Processors Supported by ESXi 
  4. Intel Code NameFMSIntel Brand Names
    Nehalem-EP0x106a5Intel Xeon 35xx Series;
    Intel Xeon 55xx Series
    Lynnfield0x106e5Intel Xeon 34xx Lynnfield Series
    Clarkdale0x20652Intel i3/i5 Clarkdale Series;
    Intel Xeon 34xx Clarkdale Series
    Arrandale0x20655Intel Core i7-620LE Processor
    Sandy Bridge DT0x206a7Intel Xeon E3-1100 Series;
    Intel Xeon E3-1200 Series;
    Intel i7-2655-LE Series;  Intel i3-2100 Series
    Westmere EP0x206c2Intel Xeon 56xx Series;
    Intel Xeon 36xx Series
    Sandy Bridge EP0x206d7Intel Pentium 1400 Series;
    Intel Xeon E5-1400 Series;
    Intel Xeon E5-1600 Series;
    Intel Xeon E5-2400 Series;
    Intel Xeon E5-2600 Series;
    Intel Xeon E5-4600 Series
    Nehalem EX0x206e6Intel Xeon 65xx Series;
    Intel Xeon 75xx Series
    Westmere EX0x206f2Intel Xeon E7-8800 Series;
    Intel Xeon E7-4800 Series;
    Intel Xeon E7-2800 Series
    Ivy Bridge DT0x306a9Intel i3-3200 Series; Intel i7-3500-LE/UE, Intel i7-3600-QE,
    Intel Xeon E3-1200-v2 Series;
    Intel Xeon E3-1100-C-v2 Series;
    Intel Pentium B925C
    Haswell DT0x306c3Intel Xeon E3-1200-v3 Series
    Ivy Bridge EP0x306e4Intel Xeon E5-4600-v2 Series;
    Intel Xeon E5-2400-v2 Series;
    Intel Xeon E5-2600-v2 Series;
    Intel Xeon E5-1400-v2 Series;
    Intel Xeon E5-2600-v2 Series
    Ivy Bridge EX0x306e7Intel Xeon E7-8800/4800/2800-v2 Series
    Haswell EP0x306f2Intel Xeon E5-2400-v3 Series;
    Intel Xeon E5-1400-v3 Series;
    Intel Xeon E5-1600-v3 Series;
    Intel Xeon E5-2600-v3 Series;
    Intel Xeon E5-4600-v3 Series
    Haswell EX0x306f4Intel Xeon E7-8800/4800-v3 Series
    Broadwell H0x40671Intel Core i7-5700EQ;
    Intel Xeon E3-1200-v4 Series
    Avoton0x406d8Intel Atom C2300 Series;
    Intel Atom C2500 Series;
    Intel Atom C2700 Series
    Broadwell EP/EX0x406f1Intel Xeon E7-8800/4800-v4 Series;
    Intel Xeon E5-4600-v4 Series;
    Intel Xeon E5-2600-v4 Series;
    Intel Xeon E5-1600-v4 Series
    Skylake SP0x50654Intel Xeon Platinum 8100 (Skylake-SP) Series;
    Intel Xeon Gold 6100/5100 (Skylake-SP) Series
    Intel Xeon Silver 4100, Bronze 3100 (Skylake-SP) Series
    Broadwell DE0x50662Intel Xeon D-1500 Series
    Broadwell DE0x50663Intel Xeon D-1500 Series
    Broadwell DE0x50664Intel Xeon D-1500 Series
    Broadwell NS0x50665Intel Xeon D-1500 Series
    Skylake H/S0x506e3Intel Xeon E3-1500-v5 Series;
    Intel Xeon E3-1200-v5 Series
    Kaby Lake H/S/X0x906e9Intel Xeon E3-1200-v6













Enabling the ESXi  6.0.0, 15169789 using the vSphere Web Client or vSphere Client
  1. Connect to the vCenter Server using either the vSphere Web or vSphere Client.
  2. Select an ESXi host in the inventory.
  3. Click the Configure tab.
  4. Under the System heading, click Advanced System Settings.
  5. Click Edit
  6. Click in the Filter box and search VMkernel.Boot.hyperthreadingMitigation
  7. Select the setting by name
  8. Change the configuration option to true (default: false).
  9. Click in the Filter box and search VMkernel.Boot.hyperthreadingMitigationIntraVM
  10. Change the configuration option to false (default: true).
  11. Click OK.
  12. Reboot the ESXi host for the configuration change to go into effect.

     

    Note:- It show a waring message in summary tab  open the web browser and login to the vsphere superseded the warning   BUT this not recommended by VMware 
    Update the host to 6.7 or 6.5 
    https://kb.vmware.com/s/article/55806

Comments

Post a Comment

Popular posts from this blog

Zabbix Server is not working: the information dispaly may not be current

Image
  Details  Cannot display item queue. Connection to Zabbix server "localhost:10051" refused. Possible reasons: 1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. Connection refused Observation:- In Centos 9 [root@nmtool ~]# systemctl status zabbix-server.service ● zabbix-server.service - Zabbix Server      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: d>     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 10:36:52 IST;>    Process: 57289 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCC>    Process: 57295 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)    Main PID: 57291 (code=exited, status=0/
Read more

How to install VNX Launcher that has embedded java and Firefox

Image
  Alternative for Adobe Flash Player to access Unisphere. Symptoms VNXe Unisphere in older OE revisions is not accessible after December 31, 2020. The Adobe Flash Player plug-in is no longer supported in browsers. VNXe Unisphere used to require a browser with the Flash Player plug-in. Cause When VNXe is running an older OE revision, Adobe Flash Player is required by Unisphere. Refer: https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf?key=1588743011568 Adobe has expired Flash Player as of December 31, 2020.   Details: https://www.adobe.com/products/flashplayer/end-of-life.html Resolution Newer VNXe OE revisions support HTML5. Once the VNXe is upgraded, Unisphere will work. Since December 31, 2020 browsers do not support Adobe Flash Player. Most browsers support HTML5. VNXe Unisphere must also support HTML5 in order to use VNXe Unisphere. HTML5 support is delivered in these VNXe revisions:       VNXe3200: VNXe Operating Env
Read more

DHCP FAILED APIPA IS USED

Image
Hi to all, In a Cisco packet tracer while i am trying to connect the dhcp server to pc it will getting the error like dhcp failed. APIPA is being used. For this issues this is also one reason.dhcp is not configured correctly. If we create a  vlan's in the switch's and we configured dhcp server in the layer 3 switch or layer 2 switch or in router. VLAN 10 NAME SALES VLAN 20 NAME DATA We created two vlan's now creating dhcp server for that  Switch(config)#ip dhcp pool name sales (should be the vlan name. not any other name.) Switch(Dhcp-config)#network 192.168.10.0 255.255.255.0  Switch(dhcp-config)#default-router 192.168.10.1 Switch(dhcp-config)#exit Swithc(config)#ip dhcp pool name data Switch(dhcp-config)#network 192.168.20.0 255.255.255.0 Switch(dhcp-config)#default-router 192.168.20.1 Switch(dhcp-config)#exit
Read more