VMware
 

Knowledge Base

Search the Knowledge Base:

Products:
Search In:
 

During an ESX Server Upgrade, Old Versions of Upgraded Modules Are Not All Removed

Details

During upgrades of ESX Server to a higher version or during patching, some modules in the /lib/modules directory might not be removed.

Solution

Some modules cannot be removed during an upgrade because they are required during the runtime of ESX Server hosts. The files reside in a subdirectory of /lib/modules. The subdirectories have names in the format <kernel version>vmnix. If all that is contained in the subdirectory are files in the format modules.<module name> and no other files or directories, these files and the subdirectory are not being used by the current version of ESX Server. These leftover files are text, not binaries, taking up about 110kb and have no effect on the ESX Server host.
 
If the subdirectory contains other directories or files not of the format modules.<module name>, the directory is possibly being used by the current version of the ESX Server software and should not be modified or removed.
 
For example, after the upgrade of the ESX Server installation, a directory listing of the /lib/modules directory might result in the following output:
2.4.21-37.0.2.ELvmnix 2.4.21-47.0.1.ELvmnix
This directory structure is the normal result of an upgrade and neither these directories or the files within them should be removed.

Keywords

esx302;relnotes

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions