Stopping mandatory Updates to Full-17.5.2-23775571.x86_64.bundle

[TonyF]

using VMware-Workstation-Full-17.5.2-23775571.x86_64.bundle

I'm getting updates on workstation startup that render it inoperable

Its in Linux Mint

vmware-2325.log

vmware-apploader-2325.log

2024-09-28T23:44:18.821Z In(05) host-2325 Log for VMware Workstation pid=2325 version=17.5.2 build=build-23775571 option=Release
2024-09-28T23:44:18.821Z In(05) host-2325 The host is x86_64.
2024-09-28T23:44:18.821Z In(05) host-2325 Host codepage=UTF-8 encoding=UTF-8
2024-09-28T23:44:18.821Z In(05) host-2325 Host is Linux 6.8.0-45-generic Linux Mint 21.3 (Virginia) Linux Mint 21.3 21.3
2024-09-28T23:44:18.821Z In(05) host-2325 Host offset from UTC is +10:00.

anybody got any clues on stopping the mandatory updates before program starts.

 is this somehow calendar controlled and oblivious to need

it happened a month ago and i reinstalled it.  the error logs are petty well identical this time

[Tim Prater]

I am having the same issue on Zorin 17.2. Spent a couple of hours fixing the issue a few weeks ago. I go to start the VM this am and the same issue is back.  I am not a Linux, "power user,' which is why a am using Zorin. I don't have time to wade through the pits of Sudo **** trying to fix this every few weeks.

[goldeneye_007]

Never heard of Zorin. Sounds interesting. I use OpenSUSE and I have never seen 'mandatory updates',

not even sure what that looks like. Is this the host OS requesting these or VMware? VMware generally will

suggest updates, not force them. Maybe it is updating VMware tools? If it is open the base Workstation app and go to Edit>Preferences.

In the applet you will see on the left 'Updates'. Untick the Automatically update VMware tools, You can leave the two 'Check for Updates'.

[TonyF]

VMware startup msg  - no options offered

is there something we can edit that will stop this mandatory action: you either do it or exit to OS

if you let it run the update fails with error messages

You now have lost access to your VMware installation

unless there is a remaining config file we can edit in some way

[goldeneye_007]

Ah. These messages occur when your Linux kernel is updated. Those are specific to Linux. VMware must recompile itself, the dreaded vmmon vmnet errors may occur at that time and you may have to hack your way around them. For that reason I always tread lightly when I see kernel updates because sometimes vmmon/vmnet compile errors cannot be immediately worked around, requiring a rollback or booting of an earlier kernel. If this stuff sounds 'advanced' it kinda is. If you never want to see these messages, never install kernel updates. Be aware kernel updates often include security and bug fixes.

[TonyF]

Thanks for inputs GE_007  maybe your experience would help unravel crucial issues in these logs: see attached error logs: looks like it cannot load library modules. think it may be app-loader is wanting to load old style library modules. see all the undefined symbols

2024-10-02T03:29:47.438Z In(05) host-5254 Skipping BTF generation for /tmp/modconfig-NLHnPu/vmnet-only/vmnet.ko due to unavailability of vmlinux
2024-10-02T03:29:47.438Z In(05) host-5254 Unable to install all modules.  See log for details.
2024-10-02T03:29:47.438Z In(05) host-5254 

This stuff is very much the same as it was a month ago when i had the problem, needed to reinstall,but it looks like this is impossible now

[goldeneye_007]

The issue is in the compile script. It does version checking and when it cannot find the supported kernel version is pops 'unavailability of vmlinux. The only fix is to munge a couple of files. It is documented elsewhere. Do a google search on 'compiling vmmon vmnet for unsupported kernel'. ---- On Wed, 02 Oct 2024 20:07:29 -0400 TonyF via Broadcom<[e-mail]> wrote ----




Thanks for inputs GE_007 maybe your experience would help unravel crucial issues in these logs: see attached error logs: looks like it cannot... -posted to the "VMware Workstation" community
div.zm_7734330045272608086_parse_803881063425970970 a { color: rgb(66, 139, 202) }
div.zm_7734330045272608086_parse_803881063425970970 a:link { text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 a:visited { text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 a:hover { color: rgb(66, 139, 202); text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 a:focus { text-decoration: underline; border: 1px solid }
div.zm_7734330045272608086_parse_803881063425970970 a:active { text-decoration: none }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210buttons a:link { text-decoration: none }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210buttons a:visited { text-decoration: none }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210buttons a:hover { text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210buttons a:active { text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210msglink a { color: rgb(255, 255, 255) }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210remove-embedded-content { max-height: 0; font-size: 0 }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210uconBody a { color: blue }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210uconBody a:link { text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210uconBody a:visited { text-decoration: underline }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210bquote { background: rgb(250, 250, 250); border-left: 5px solid rgb(235, 235, 235); margin: 1.5em 10px 1.5em 20px; padding: 0.5em 10px }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210bquote :before { color: rgb(204, 204, 204); font-size: 4em; line-height: 0.1em; vertical-align: -0.4em; margin-right: 5px }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210bquote p { display: inline; font-weight: normal; font-size: 11.5px; font-weight: 300; line-height: 1.25 }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210bqFooter { text-align: right; font-size: 80%; margin-top: 5px }
div.zm_7734330045272608086_parse_803881063425970970 .x_578092210bqFooter :after { color: rgb(204, 204, 204); font-size: 5em; line-height: 0; vertical-align: -0.4em; margin-left: 5px }



















VMware Workstation





Post New Message







Re: Stopping mandatory Updates to Full-17.5.2-23775571.x86_64.bundle







Reply to Group


Reply to Sender
















Oct 2, 2024 8:05 PM  |    view attached



TonyF















Thanks for inputs GE_007  maybe your experience would help unravel crucial issues in these logs: see attached error logs: looks like it cannot load library modules. think it may be app-loader is wanting to load old style library modules. see all the undefined symbols
2024-10-02T03:29:47.438Z In(05) host-5254 Skipping BTF generation for /tmp/modconfig-NLHnPu/vmnet-only/vmnet.ko due to unavailability of vmlinux2024-10-02T03:29:47.438Z In(05) host-5254 Unable to install all modules.  See log for details.2024-10-02T03:29:47.438Z In(05) host-5254 
This stuff is very much the same as it was a month ago when i had the problem, needed to reinstall,but it looks like this is impossible now









 
Reply to Group Online
 
Reply to Group via Email
 
View Thread
 
Recommend
 
Forward
 
Flag as Inappropriate
 

[TonyF]

Seems the fix:the wrong timex is being used

https://unix.stackexchange.com/questions/773558/vmware-vmmon-vmnet-17-5-1-and-linux-kernel-6-8-0-wont-compile

this fix is at the end

run this script to fix vmware itself, not tried it yet,      before i dive in - any opinions Guys ?

#!/bin/sh

# switch to the vmmware modules source dir
cd /usr/lib/vmware/modules/source/

# create backup of the modules
cp vmmon.tar vmmon.tar.bak

# extract the module with code issue 
tar -xvf vmmon.tar 

# fix the line that caused the build to fail
sed  -i "s/asm\/timex/uapi\/linux\/timex/" vmmon-only/common/vmx86.c 

# package the module again
tar -cvf vmmon.tar vmmon-only

# remove the working dir 
rm -rf vmmon-only

# try to rebuild the module 
vmware-modconfig --console --install-all

[goldeneye_007]

Well that's a new one. Not surprised at all though. Each kernel update always risks it breaking in novel ways. VMware has never kept up with kernel updates, I don't think they care honestly since the community steps in and fixes it. ---- On Wed, 02 Oct 2024 21:17:42 -0400 TonyF via Broadcom<[e-mail]> wrote ----




Seems the fix:the wrong timex is being used unix.stackexchange.com/questions/773558/... this fix is at the end run this script to fix vmware... -posted to the "VMware Workstation" community
div.zm_7525689496189460096_parse_3660704949628330123 a { color: rgb(66, 139, 202) }
div.zm_7525689496189460096_parse_3660704949628330123 a:link { text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 a:visited { text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 a:hover { color: rgb(66, 139, 202); text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 a:focus { text-decoration: underline; border: 1px solid }
div.zm_7525689496189460096_parse_3660704949628330123 a:active { text-decoration: none }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670buttons a:link { text-decoration: none }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670buttons a:visited { text-decoration: none }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670buttons a:hover { text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670buttons a:active { text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670msglink a { color: rgb(255, 255, 255) }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670remove-embedded-content { max-height: 0; font-size: 0 }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670uconBody a { color: blue }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670uconBody a:link { text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670uconBody a:visited { text-decoration: underline }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670bquote { background: rgb(250, 250, 250); border-left: 5px solid rgb(235, 235, 235); margin: 1.5em 10px 1.5em 20px; padding: 0.5em 10px }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670bquote :before { color: rgb(204, 204, 204); font-size: 4em; line-height: 0.1em; vertical-align: -0.4em; margin-right: 5px }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670bquote p { display: inline; font-weight: normal; font-size: 11.5px; font-weight: 300; line-height: 1.25 }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670bqFooter { text-align: right; font-size: 80%; margin-top: 5px }
div.zm_7525689496189460096_parse_3660704949628330123 .x_375382670bqFooter :after { color: rgb(204, 204, 204); font-size: 5em; line-height: 0; vertical-align: -0.4em; margin-left: 5px }



















VMware Workstation





Post New Message







Re: Stopping mandatory Updates to Full-17.5.2-23775571.x86_64.bundle







Reply to Group


Reply to Sender
















Oct 2, 2024 9:16 PM



TonyF















Seems the fix:the wrong timex is being used
unix.stackexchange.com/questions/773558/...
this fix is at the end
run this script to fix vmware itself
#!/bin/sh

# switch to the vmmware modules source dir
cd /usr/lib/vmware/modules/source/

# create backup of the modules
cp vmmon.tar vmmon.tar.bak

# extract the module with code issue
tar -xvf vmmon.tar

# fix the line that caused the build to fail
sed -i "s/asm/timex/uapi/linux/timex/" vmmon-only/common/vmx86.c

# package the module again
tar -cvf vmmon.tar vmmon-only

# remove the working dir
rm -rf vmmon-only

# try to rebuild the module
vmware-modconfig --console --install-all










 
Reply to Group Online
 
Reply to Group via Email
 
View Thread
 
Recommend
 
Forward
 
Flag as Inappropriate