_--MAX--_
Contributor
Contributor

Upgrading to 3.0.2 or 3.5 causes vmkernel failures (serious problem!)

Hi everybody

I've just tried to upgrade a small esx system to 3.0.2 and later to 3.5 version.

Unfortunatelly vmware esx 3.0.2 and 3.5 have killed the box :smileyangry: :smileyangry: :smileyangry: !!!

After the 'successful' upgrade my esx server does NOT work.

The whole network connections are dead... :_| :_| Smiley Sad

All I'm getting is: vmkernel failures --> vmkernel autorization warning

--> MOD 2558: Initianization of vmkernel failed

--> vmkernel not loaded --> several modules fail to load in a row ... (hence no network ! )

--> vmnix modul not loaded ...etc.

and when I do a REBOOT.... the server simply stops to rebooting at 'stopping vmware-autostart' Smiley Sad

how can I fix this vmkernel-problem? With 2.5.X everything worked fine and now with 3.5 (the better version???) all of sudden I have the complete vmkernel-OVERKILL?

Can't solve this hard task alone...:-(

0 Kudos
2 Replies
Texiwill
Leadership
Leadership

Hello,

VI3.5 is very sensitive to the hardware revisions in your system. I would ensure that your firmware revisions on all your hardware are running at the most recent version. I had a similar issue until I updated my local disk and network cards firmware to the latest. Give that a try and then reinstall ESX v3.5.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIII: 2009-2021,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
_--MAX--_
Contributor
Contributor

Thanks for your reply.

Your local disk...was it an IDE disc? And than you have changed to SATA, right?

Cause I'm using IDE disc right now (for ESX Server).

0 Kudos