VMware Communities
xphinx
Enthusiast
Enthusiast
Jump to solution

Help with a new error of this kind: modinfo: ERROR: Module vmmon not found.

Hi, every time I update the Linux kernel I have to run the steps showed here: https://kb.vmware.com/s/article/2146460

and its been working fine. I also encountered errors before and was fixed with this: https://communities.vmware.com/t5/VMware-Workstation-Pro/The-fix-I-used-to-do-isn-t-working-anymore-...

but this is not the case any more. I only have like 3 other keys.

The ERROR I encountered this time is:

After step 1:

sudo openssl req -new -x509 -newkey rsa:2048 -keyout MOK-0004.priv -outform DER -out MOK-0004.der -nodes -days 36500 -subj "/CN=VMware/"

At step 2:

sudo /usr/src/linux-headers-`uname -r`/scripts/sign-file sha256 ./MOK-0004.priv ./MOK-0004.der $(modinfo -n vmmon)

I get this error:

modinfo: ERROR: Module vmmon not found.

Usage: scripts/sign-file [-dp] <hash algo> <key> <x509> <module> [<dest>]

scripts/sign-file -s <raw sig> <hash algo> <x509> <module> [<dest>]

Can someone help me to fix this issue. Thanks.

0 Kudos
3 Solutions

Accepted Solutions
bluefirestorm
Champion
Champion
Jump to solution

The error shows "Module vmmon not found." Chances are the build of vmmon failed with the new kernel (6.15.0-14 vs the previous kernel). A visit to mkubecek github repository should help get you to a successful vmmon build with the new kernel. Signing should succeed when the vmmon module is successfully built.

https://github.com/mkubecek/vmware-host-modules/blob/master/INSTALL

 

View solution in original post

DhairyaT
VMware Employee
VMware Employee
Jump to solution

0 Kudos
bluefirestorm
Champion
Champion
Jump to solution

From the looks of it, the vmmon build was successful as the built kernel object file was copied over.

make[1]: Leaving directory '/tmp/modconfig-Wm9BKD/vmmon-only'
cp -f vmmon.ko ./../vmmon.o

But now the error is on vmnet,

make[3]: *** [scripts/Makefile.build:251: /tmp/modconfig-Wm9BKD/vmnet-only/bridge.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.5.0-15-generic/Makefile:2037: /tmp/modconfig-Wm9BKD/vmnet-only] Error 2

You could try the patch to bridge.c as indicated in this post
https://communities.vmware.com/t5/Workstation-2023-Tech-Preview/Linux-Kernel-6-5-rc-vmmon-compile-fa...

It is strange that you have to do these manual patches. I just built again for 6.5.0.18 update without having to do anything extra with method 2.

 

View solution in original post

0 Kudos
19 Replies
bluefirestorm
Champion
Champion
Jump to solution

The error shows "Module vmmon not found." Chances are the build of vmmon failed with the new kernel (6.15.0-14 vs the previous kernel). A visit to mkubecek github repository should help get you to a successful vmmon build with the new kernel. Signing should succeed when the vmmon module is successfully built.

https://github.com/mkubecek/vmware-host-modules/blob/master/INSTALL

 

xphinx
Enthusiast
Enthusiast
Jump to solution

Hi, thanks a lot for your help again.

I tried doing the first two methods on: 0. Quick guide for impatient: https://github.com/mkubecek/vmware-host-modules/blob/master/INSTALL

but I'm getting these errors:

First method (build and install):

ERROR: modpost: "__pte_offset_map" [/home/wwx/vmware-host-modules-workstation-17.0.0/vmmon-only/vmmon.ko] undefined!
make[4]: *** [scripts/Makefile.modpost:144: /home/wwx/vmware-host-modules-workstation-17.0.0/vmmon-only/Module.symvers] Error 1
make[3]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:1989: modpost] Error 2
make[2]: *** [Makefile:234: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'
make[1]: *** [Makefile:117: vmmon.ko] Error 2
make[1]: Leaving directory '/home/wwx/vmware-host-modules-workstation-17.0.0/vmmon-only'
make: *** [Makefile:21: vmmon-only] Error 2

0 Kudos
bluefirestorm
Champion
Champion
Jump to solution

Was the "make install" executed with sudo?

Personally, I use the second method as the original tarballs would also fail in subsequent updates to the Linux kernel (for example 6.15.0-15 if ever there will be one). As the tarballs were already replaced with the 2nd method; a build from the VMware UI or manual vmware-modconfig followed by the secure boot key signing is all that is needed for any subsequent Linux kernel update; unless of course the kernel update breaks vmmon/vmnet build(s) again and another visit to github/mkubecek is again required.

 

xphinx
Enthusiast
Enthusiast
Jump to solution

Hi, yes I did it on root.

And I just tried the second method: "Second method (replace original tarballs):"

and while on root at the last step: vmware-modconfig --console --install-all

I'm getting this error:

Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
[AppLoader] GLib does not have GSettings support.
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done
make: Entering directory '/tmp/modconfig-gpMlzT/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.5.0-14-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-14-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/crosspage.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/moduleloop.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/sharedAreaVmmon.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/statVarsVmmon.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/task.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/bootstrap/bootstrap.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/bootstrap/monLoader.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/bootstrap/monLoaderVmmon.o
CC [M] /tmp/modconfig-gpMlzT/vmmon-only/bootstrap/vmmblob.o
LD [M] /tmp/modconfig-gpMlzT/vmmon-only/vmmon.o
MODPOST /tmp/modconfig-gpMlzT/vmmon-only/Module.symvers
ERROR: modpost: "__pte_offset_map" [/tmp/modconfig-gpMlzT/vmmon-only/vmmon.ko] undefined!
make[3]: *** [scripts/Makefile.modpost:144: /tmp/modconfig-gpMlzT/vmmon-only/Module.symvers] Error 1
make[2]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:1989: modpost] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'
make: *** [Makefile:117: vmmon.ko] Error 2
make: Leaving directory '/tmp/modconfig-gpMlzT/vmmon-only'
make: Entering directory '/tmp/modconfig-gpMlzT/vmnet-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.5.0-14-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-14-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/driver.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/hub.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/userif.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/netif.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/bridge.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/procfs.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/smac.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-gpMlzT/vmnet-only/vnetUserListener.o
/tmp/modconfig-gpMlzT/vmnet-only/bridge.c: In function ‘VNetBridgeSendLargePacket’:
/tmp/modconfig-gpMlzT/vmnet-only/bridge.c:1416:11: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘tcp_gso_segment’? [-Werror=implicit-function-declaration]
1416 | segs = skb_gso_segment(skb, 0);
| ^~~~~~~~~~~~~~~
| tcp_gso_segment
/tmp/modconfig-gpMlzT/vmnet-only/bridge.c:1416:9: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
1416 | segs = skb_gso_segment(skb, 0);
| ^
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:251: /tmp/modconfig-gpMlzT/vmnet-only/bridge.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:2037: /tmp/modconfig-gpMlzT/vmnet-only] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'
make: *** [Makefile:117: vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-gpMlzT/vmnet-only'
Unable to install all modules. See log for details.

 

bluefirestorm
Champion
Champion
Jump to solution

The error for method 2 for the build of vmmon is the same as build of method 1. I was able to build vmmon/vmnet with kernel 6.5.0-14 with method 2 just this recent weekend although I have Workstation Pro 16.2.5.

Are you matching the version number? For example, if you are using 17.5.0 or 17.0.2, replace that accordingly whichever method you use. From the error text of method 1, it looks like you specified 17.0.0. Otherwise, I don't know what else to suggest.

ERROR: modpost: "__pte_offset_map" [/home/wwx/vmware-host-modules-workstation-17.0.0/vmmon-only/vmmon.ko] undefined!
make[4]: *** [scripts/Makefile.modpost:144: /home/wwx/vmware-host-modules-workstation-17.0.0/vmmon-only/Module.symvers] Error 1
make[3]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:1989: modpost] Error 2
make[2]: *** [Makefile:234: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'
make[1]: *** [Makefile:117: vmmon.ko] Error 2
make[1]: Leaving directory '/home/wwx/vmware-host-modules-workstation-17.0.0/vmmon-only'
make: *** [Makefile:21: vmmon-only] Error 2

xphinx
Enthusiast
Enthusiast
Jump to solution

Hi, thanks for replying. This is my vmware version: VMware Workstation 17.0.0 build-20800274

I just tried again with the second method:

wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.0.0.tar.gz
tar -xzf workstation-17.0.0.tar.gz
cd vmware-host-modules-workstation-17.0.0
tar -cf vmmon.tar vmmon-only
tar -cf vmnet.tar vmnet-only
cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/
vmware-modconfig --console --install-all

And I'm still getting the same error as above. Is any way to get a Vmware tech-customer service in this thread? Thanks.

Technogeezer
Immortal
Immortal
Jump to solution


@xphinx wrote:

Hi, thanks for replying. This is my vmware version: VMware Workstation 17.0.0 build-20800274

Is any way to get a Vmware tech-customer service in this thread? Thanks.


Only if they decide to do so on their own time. Unfortunately this is a user-to-user forum and not an official VMware support forum. VMware tech support doesn't monitor this forum as part of their official duties. 

You'd have better luck having @mkubecek  weigh in on what might be going wrong. 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
xphinx
Enthusiast
Enthusiast
Jump to solution

Thanks for the reply. I sent a message to @mkubecek I hope he answers.

0 Kudos
xphinx
Enthusiast
Enthusiast
Jump to solution

I just checked the permissions and I found all these:

.rw-rw-r-- wwx wwx 471 KB Sun Dec 4 13:51:03 2022  workstation-17.0.0.tar.gz
.rw-rw-r-- wwx wwx 471 KB Sun Dec 4 21:48:08 2022  workstation-17.0.0.tar.gz.1
.rw-rw-r-- wwx wwx 471 KB Mon Jan 15 20:09:34 2024  workstation-17.0.0.tar.gz.2
.rw-rw-r-- wwx wwx 471 KB Mon Jan 15 20:35:18 2024  workstation-17.0.0.tar.gz.3
.rw-rw-r-- wwx wwx 471 KB Tue Jan 16 11:08:15 2024  workstation-17.0.0.tar.gz.4
.rw-rw-r-- wwx wwx 471 KB Wed Jan 24 18:03:11 2024  workstation-17.0.0.tar.gz.5

I wonder why there's so many.

0 Kudos
DhairyaT
VMware Employee
VMware Employee
Jump to solution

@xphinx Ticket has been raised internally. Relevant team will look into the same.

0 Kudos
xphinx
Enthusiast
Enthusiast
Jump to solution

Great!, thank you. Will be on alert for their reply or message.

0 Kudos
DhairyaT
VMware Employee
VMware Employee
Jump to solution

@xphinx Please follow the solution mentioned on below thread and let us know the update here-

https://communities.vmware.com/t5/Workstation-2023-Tech-Preview/Linux-Kernel-6-5-rc-vmmon-compile-fa...

0 Kudos
xphinx
Enthusiast
Enthusiast
Jump to solution

Hi, thanks a lot for replying.

After what I've done from above and the results, I did what you told me:

 

Open vmmon-only/include/pgtbl.h and replace pte_offset_map to pte_offset_kernel

after this, I did what someone in the thread mentioned:

# Cd to the dir where the vmware modules are.
cd /usr/lib/vmware/modules/source
# Unpack vmmon.
tar -xvf vmmon.tar
# Fix by replacing replace pte_offset_map with pte_offset_kernel	
sed -i 's/pte_offset_map/pte_offset_kernel/g' vmmon-only/include/pgtbl.h
# Backup original vmmon.tar
mv vmmon.tar vmmon.tar.original
# Pack the patched vmmon.
tar -cf vmmon.tar vmmon-only
vmware-modconfig --console --install-all

and got similar errors:

Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
[AppLoader] GLib does not have GSettings support.
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done
make: Entering directory '/tmp/modconfig-Wm9BKD/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.5.0-15-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-15-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/crosspage.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/moduleloop.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/sharedAreaVmmon.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/statVarsVmmon.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/task.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/bootstrap/bootstrap.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/bootstrap/monLoader.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/bootstrap/monLoaderVmmon.o
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/bootstrap/vmmblob.o
LD [M] /tmp/modconfig-Wm9BKD/vmmon-only/vmmon.o
MODPOST /tmp/modconfig-Wm9BKD/vmmon-only/Module.symvers
CC [M] /tmp/modconfig-Wm9BKD/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-Wm9BKD/vmmon-only/vmmon.ko
BTF [M] /tmp/modconfig-Wm9BKD/vmmon-only/vmmon.ko
Skipping BTF generation for /tmp/modconfig-Wm9BKD/vmmon-only/vmmon.ko due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-15-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-Wm9BKD/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-Wm9BKD/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory '/tmp/modconfig-Wm9BKD/vmmon-only'
make: Entering directory '/tmp/modconfig-Wm9BKD/vmnet-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.5.0-15-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-15-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/driver.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/hub.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/userif.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/netif.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/bridge.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/procfs.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/smac.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-Wm9BKD/vmnet-only/vnetUserListener.o
/tmp/modconfig-Wm9BKD/vmnet-only/bridge.c: In function ‘VNetBridgeSendLargePacket’:
/tmp/modconfig-Wm9BKD/vmnet-only/bridge.c:1416:11: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘tcp_gso_segment’? [-Werror=implicit-function-declaration]
1416 | segs = skb_gso_segment(skb, 0);
| ^~~~~~~~~~~~~~~
| tcp_gso_segment
/tmp/modconfig-Wm9BKD/vmnet-only/bridge.c:1416:9: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
1416 | segs = skb_gso_segment(skb, 0);
| ^
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:251: /tmp/modconfig-Wm9BKD/vmnet-only/bridge.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.5.0-15-generic/Makefile:2037: /tmp/modconfig-Wm9BKD/vmnet-only] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-15-generic'
make: *** [Makefile:117: vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-Wm9BKD/vmnet-only'
Unable to install all modules. See log for details.

0 Kudos
bluefirestorm
Champion
Champion
Jump to solution

From the looks of it, the vmmon build was successful as the built kernel object file was copied over.

make[1]: Leaving directory '/tmp/modconfig-Wm9BKD/vmmon-only'
cp -f vmmon.ko ./../vmmon.o

But now the error is on vmnet,

make[3]: *** [scripts/Makefile.build:251: /tmp/modconfig-Wm9BKD/vmnet-only/bridge.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.5.0-15-generic/Makefile:2037: /tmp/modconfig-Wm9BKD/vmnet-only] Error 2

You could try the patch to bridge.c as indicated in this post
https://communities.vmware.com/t5/Workstation-2023-Tech-Preview/Linux-Kernel-6-5-rc-vmmon-compile-fa...

It is strange that you have to do these manual patches. I just built again for 6.5.0.18 update without having to do anything extra with method 2.

 

0 Kudos
xphinx
Enthusiast
Enthusiast
Jump to solution

This finally helped me to fix the issue. Thank you so much for all your help.

0 Kudos
mallap
VMware Employee
VMware Employee
Jump to solution

Please note that this issue is already resolved in VMware WS 17.5. Please check and confirm.

0 Kudos
xphinx
Enthusiast
Enthusiast
Jump to solution

Hey, I'm back at these issues again after upgrading to 17.5.

I did the whole process again and after running:

vmware-modconfig --console --install-all

I got these errors:

Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
[AppLoader] GLib does not have GSettings support.
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done
make: Entering directory '/tmp/modconfig-5ORcsf/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.5.0-21-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-21-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/crosspage.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/moduleloop.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/sharedAreaVmmon.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/statVarsVmmon.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/task.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/bootstrap/bootstrap.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/bootstrap/monLoader.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/bootstrap/monLoaderVmmon.o
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/bootstrap/vmmblob.o
LD [M] /tmp/modconfig-5ORcsf/vmmon-only/vmmon.o
MODPOST /tmp/modconfig-5ORcsf/vmmon-only/Module.symvers
CC [M] /tmp/modconfig-5ORcsf/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-5ORcsf/vmmon-only/vmmon.ko
BTF [M] /tmp/modconfig-5ORcsf/vmmon-only/vmmon.ko
Skipping BTF generation for /tmp/modconfig-5ORcsf/vmmon-only/vmmon.ko due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-21-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-5ORcsf/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-5ORcsf/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory '/tmp/modconfig-5ORcsf/vmmon-only'
make: Entering directory '/tmp/modconfig-5ORcsf/vmnet-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.5.0-21-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-21-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/driver.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/hub.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/userif.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/netif.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/bridge.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/procfs.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/smac.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-5ORcsf/vmnet-only/vmnet.o
MODPOST /tmp/modconfig-5ORcsf/vmnet-only/Module.symvers
CC [M] /tmp/modconfig-5ORcsf/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-5ORcsf/vmnet-only/vmnet.ko
BTF [M] /tmp/modconfig-5ORcsf/vmnet-only/vmnet.ko
Skipping BTF generation for /tmp/modconfig-5ORcsf/vmnet-only/vmnet.ko due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-21-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-5ORcsf/vmnet-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-5ORcsf/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory '/tmp/modconfig-5ORcsf/vmnet-only'
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface done
VM communication interface socket family done
Virtual ethernet failed
VMware Authentication Daemon done
Unable to start services

 

0 Kudos
bluefirestorm
Champion
Champion
Jump to solution

With the upgrade to version 17.5.0, ythe build was successful for both vmmon and vmnnet kernel modules (it got to the point of copy).
cp -f vmmon.ko ./../vmmon.o
cp -f vmnet.ko ./../vmnet.o

It would not go this far (Starting VMware services) if the build of either kernel module failed.
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface done
VM communication interface socket family done
Virtual ethernet failed
VMware Authentication Daemon done
Unable to start services

The "Virtual machine monitor failed" (vmmon) and "Virtual ethernet failed" (vmnet) messages is because the vmmon and vmnet now needs to be signed since secure boot is enabled on the Ubuntu host.

0 Kudos
xphinx
Enthusiast
Enthusiast
Jump to solution

Hi, thanks again, this solved the issue.

0 Kudos