2 Replies Latest reply on Dec 13, 2018 11:26 AM by srwsol

    William Lam's Maclearn now part of ESXi (causes dependency check on updates)?

    srwsol Enthusiast

      Hi folks:


      I'm not sure if this is the right place to put this question or not, but I've been using William Lam's maclearn vib for a couple of years now because I have a VM that runs OpenVPN in bridge mode, and that needs promiscuous mode.  As with the nested ESXi situation that he wrote maclearn to address, this causes excessive CPU usage on that VM if there is lots of traffic on the virtual switch.  Because of that when I did updates I had to use "software profile update" instead of "software profile install" so that the maclearn vib didn't get removed. 


      I was going through the dry-run of updating to 6.5d and it failed with a dependency check:


      [root@naplesesxi:~] esxcli software profile update --dry-run --depot=/vmfs/volumes/539b4dcd-0d43b62e-2a98-e840f2d1736d/Upgrades/ESXi650-201704001

      .zip --profile=ESXi-6.5.0-20170404001-standard


      File path of '/usr/lib/vmware/vmkmod/dvfilter-maclearn' is claimed by multiple non-overlay VIBs: {'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379'}

      File path of '/usr/libexec/jumpstart/plugins/dvfilter-maclearn.json' is claimed by multiple non-overlay VIBs: {'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379'}

      Please refer to the log file for more details.


      I had read something about a new fling being available that added a better version of maclearn, but it required a Distributed Virtual Switch, and as I only have the essentials package, I didn't have the ability to create a Distributed Virtual Switch, so I was intending to just stay with what I had.  I had not read or heard that the original version of maclearn was going to actually become a standard part of ESXi, but if I am reading the error message correctly, I believe it's trying to tell me that it is.  If I do the command as "install" instead of update, it says that my version will be removed, along with some other ones that I'll need to research:


      [root@naplesesxi:~] esxcli software profile install --dry-run --depot=/vmfs/volumes/539b4dcd-0d43b62e-2a98-e840f2d1736d/Upgrades/ESXi650-20170400

      1.zip --profile=ESXi-6.5.0-20170404001-standard


      You attempted to install an image profile which would have resulted in the removal of VIBs ['VFrontDe_bootbank_sata-xahci_1.10-1', 'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_lsu-lsi-mptsas-plugin_1.0.0-1vmw.600.0.0.2494585', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379']. If this is not what you intended, you may use the esxcli software profile update command to preserve the VIBs above. If this is what you intended, please use the --ok-to-remove option to explicitly allow the removal.

      Please refer to the log file for more details.



      The release notes didn't mention anything about maclearn, but it looks like it's here.  I guess my best bet would be to remove Lam's original vib first, assuming that this new vib is really the old maclearn version that works on systems without a Distributed Virtual Switch, and then apply the update in "update" mode so that I don't remove the others. 


      I guess what I'm looking for feedback on is whether or not that VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379 really is a plug replacement for the original maclearn vib.


      Comments welcome.