If you’re a fan of VMware Workstation and you’ve updated to version 17.0.0, you might have run into a frustrating problem where it says, VMware Workstation 17.0.0:”Can’t make vmnet work.” This happens because the software has trouble working with your Linux computer’s brain (kernel). The part of VMware that helps your virtual machines talk to the outside world, called the vmnet module, gets all mixed up and can’t do its job.
The Problem: What’s Wrong?
So, when you update VMware to version 17.0.0, it doesn’t quite get along with your Linux system, causing a glitch. This glitch makes the vmnet module, which is like the bridge between your virtual machines and your computer, not work properly. As a result, you can’t use your virtual machines like you used to.
The Solution: Fixing the vmnet Module
To get your virtual machines back in action, follow these steps to fix the vmnet module:
Step 1: Go to the VMware modules place
First, open your computer’s command center (the terminal) and go to the place where VMware keeps its special files. This place is usually at /usr/lib/vmware/modules/source.
cd /usr/lib/vmware/modules/sourceStep 2: Unpack the vmnet module
Think of the vmnet module as a puzzle in a box. To use it, you need to unpack it.
tar -xvf vmnet.tarStep 3: Add the missing puzzle piece
The problem is like a missing puzzle piece in the vmnet-only/bridge.c file. We can fix it by adding that missing piece with a special command called sed. This command makes sure the vmnet module knows what to do by adding a line in the right spot.
sed -i '46 a#include <net/gso.h>' vmnet-only/bridge.cStep 4: Keep a backup of the original vmnet
Before we make changes, it’s always a good idea to have a backup, just like keeping a spare key.
mv vmnet.tar vmnet.tar.originalStep 5: Put the puzzle back together
Now that we’ve added the missing piece, it’s time to pack up the vmnet module again into its puzzle box.
tar -cf vmnet.tar vmnet-onlyWith this step, we’re putting everything back in its place, but this time, it’s fixed!
Testing Your Virtual Machines
Now that you’ve fixed the vmnet module puzzle, you should be able to start your virtual machines without seeing that “Can’t make vmnet work” message. This solution manually fixes the problem by making sure the vmnet module understands what to do.
Remember, updates to VMware or your Linux computer might need you to do this fix again in the future. Just keep an eye out for updates from VMware that might make this problem go away for good.
In the end, even though computer problems can be annoying, there are usually ways to solve them. This time, we fixed the “Can’t make vmnet work” problem by patching the vmnet module. Enjoy using your virtual machines again!
If you liked the post also check out : error-failed-to-commit-transaction-conflicting-files-solution