VMware Cloud Community
sk8erbender
Contributor
Contributor

error after update esxi 6.5

Hello everyone! Im stuck on esxi  6.5.0 Update 1 (Build 7967591)

Manufacturer 

    Intel Corporation    

Model

    S3210SH    

CPU

     4 CPUs x Intel(R) Xeon(R) CPU X3360 @ 2.83GHz

8 gb ram ddr2

When I go updates

esxcli network firewall ruleset set -e true -r httpClient

esxcli software profile update -p ESXi-6.5.0-20180804001-standard \

-d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

esxcli network firewall ruleset set -e false -r httpClient

Then reboot the server. I get purple screen ( photo attached)

Then I have to reboot again and I get back on Build 7967591 . Everything works on that build...A12C769D-4847-418C-9CDA-5789446FE0C5.jpg

Reply
0 Kudos
7 Replies
GayathriS
Expert
Expert

I see there is an annoucement made , check out if that makes any help here

”L1 Terminal Fault” vulnerabilities CVE-2018-3646, CVE-2018-3620 and CVE-2018-3615

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

regards

Gayathri

Reply
0 Kudos
sk8erbender
Contributor
Contributor

Doesnt make any sense at all. The link you provided

Reply
0 Kudos
GayathriS
Expert
Expert

Have you verified the Server model against ESXi 6.5 version and confirmed if thats compatible.

If I am not wrong the physical server that you are using is Intel   S3210SH   correct ?

I dont see this server as compatible for ESXi 6.5

pastedImage_0.png

VMware Compatibility Guide - System Search

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

regards

Gayathri

Reply
0 Kudos
sk8erbender
Contributor
Contributor

But it works 5.5 and 6.5 but not the latest updates

Reply
0 Kudos
Ganeshpal
Enthusiast
Enthusiast

Dear SK,

IT will not supportable.

Reply
0 Kudos
BerndtSchumann
Enthusiast
Enthusiast

That works with the current build you use and is not listed as compatible means it either "might" or "might not" work, and unfortunately there is no guarantee for the first option.

Reply
0 Kudos
a_p_
Leadership
Leadership

As mentioned by the other users, running ESXi on unsupported hardware may, or may not work.

Anyway, since the error message points to the ne1000 driver, you could try to replace this driver with the currently working version, after updating the host.

To do this upload the "old" ne1000 driver to a folder on a datastore, and run e.g.:

esxcli software vib install -v /vmfs/volumes/datastrore1/Patches/VMW_bootbank_ne1000_0.8.0-16vmw.650.1.26.5969303.vib

after updating the host with the command you mentioned, and prior to rebooting it.

No guarantees though.

André

Reply
0 Kudos