cjnot's Posts

I didn't think I would have another update around this issue, but I stumbled on something related to this issue.  I have been running the 7.0.0 Build 16324942 code for some months now on these machines with no issue.  Under this release, the microcode versions are all correct/consistent on all cores shown in the output below.  It is only when I try and move to 7.0.1 does the microcode version become inconsistent.  This now leads me to believe that this is not bios related, but related to the microcode update done by ESXi. I tried catching one at the first boot after upgrade from 7.0.0->7.0.1 and inserting "microcodeUpdate=FALSE" at the end of the boot string, but I am still getting a purple screen showing microcode mismatch. Is there another way to prevent/disable the microcode update at boot time? [root@esxi3:~] vmware -l VMware ESXi 7.0 GA [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/0 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/1 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/2 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/3 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/4 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/5 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/6 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d [root@esxi3:~] vsish -e cat /hardware/cpu/cpuList/7 | grep -i -E 'family|model|stepping|microcode|re vision' Family:0x06 Model:0x4d Stepping:0x08 Number of microcode updates:0 Original Revision:0x0000012d Current Revision:0x0000012d  

I found two things out related to this issue: 1.  The Supermicro systems we are running (i.e. SYS-5018A-FTN4) are running with a HCL supported processor (Atom C2758), but the motherboard that comes with this system apparently is now only supported to vSphere 6 (https://www.vmware.com/resources/compatibility/search.php?deviceCategory=server&productid=43366&deviceCategory=server&details=1&partner=105&keyword=atom&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&b=1603451106826) 2.  Supermicro doesn't seem to see this as an issue and won't be releasing a firmware update to fix it. Is there a way to disable the microcode version check at boot time for these systems?   

I tried taking the latest BIOS from Supermicro on a test machine in the lab, but the microcode still differs between core 0 and 1-7.  Every C2700 series machine I've checked also has this microcode behavior, so I'm guessing that its going to get acknowledged as a bug.  These processor is extremely common and HCL for vSphere 7, so I'm guessing we will see a patch soon.