mkubecek
VMware Workstation 17.5.2 Pro has been released
https://docs.vmware.com/en/VMware-Workstation-Pro/17.5.2/rn/vmware-workstation-1752-pro-release-notes/index.html
The 'Player' version has been discontinued, and Workstation Pro is now 'free for personal use'.. Download link goes to 'VMware Store Down for Maintenance' and it seems it will be available via CloudVista Store?? 17.5.2 is just another dot-release with some more 'security fixes', with no new features listed... I'm hoping they fix the UI with Wayland......
Thanks to info found on a certain forum, there is a direct download from the old vmware servers:
https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/core/
@rgadsdon do you know if vmware 17.5.2 modules are compiling on kernel 6.9?
I haven't updated the version since I need it for work :: I cannot risk it
And, surprise, surprise... the module source in 17.5.2 is exactly the same as in 17.5.1 and 17.5.0. On one hand, it makes the transition to new version quite simple, on the other I can't help feeling that it's kind of sad.
@Hyphaed I have 17.5.2, plus the 17.5.1 vmmon/vmnet patches, plus the 6.9 vmnet patch copied from another thread, working, but I would recommend waiting until the 'correct' 6.9 patch is available here..
@rgadsdon I will wait, yes
I do not know if vmware is paying to mkubecek or not
I think they must
I cannot understand why I need to head here to have working vmware modules on my system?
nowadays I've read with 17.5.2 is free for personal use, I got a license for the workstation pro :: and is not about the price....
is about being a Software used by thousands of companies around the world, and is quite common find VMWare virtual machines on servers
hence I cannot just understand why there is that poor support from vmware side
I can understand you need to patch it in order to run MacOS operating system, because of apple non sense copyright that does not let run their OS if the metal on it hasn't an apple stamped
anyway
many thanks for your great work @mkubecek
I guess someday I will move to other virtualization solutions, companies/clients using VMWare was what made me move to VMWare Workstation Pro
For Ubuntu 24.04, Workstation Pro 17.5.2 has no problem with the 6.5 kernel. Issues do surface with the 6.8 kernel. For the present, a work-around is to just run the 6.5 kernel.
@rpressw I'm on ubuntu 24.04 base and no problem running 17.5.2 with kernel 6.9.1
+###### ..
#-+#############. +.
.##+#################-. Uptime: 4 hours, 12 mins
.#######+#+---..-+######
###+#+---+-++--....+####. Ubuntu Customized OS
-##+-----.--.. .. ..++## f2fs, custom kernel, nvidia open kernel
####---++---.-+++-. -#. configured targeting local hardware & work needs
##+-----....---- ##
##+------...-..-. .. -+ Kernel: 6.9.1-tkg-custom
.##.+#####+++--+++++++ + Packages: 3462 (dpkg), 45 (flatpak)
#+---+##++++. ++##-+-. +
.#+-+++-+++++ +++ - + Shell: bash 5.2.21
+-++--+----- ..-.. DE: GNOME 46.1
++--------++ ++ - WM: Mutter
++-+------#---+ .- Terminal: gnome-terminal
+++-----#######++- ..
+-+-##--+++++++++..- CPU: 11th Gen Intel i7-11700 (16) @ 4.800GHz
+++--+----- + .. GPU: NVIDIA GeForce RTX 3070
-++-----####+. --.. RAM: 8306MiB / 64039MiB
++-++-----..-.-..
-++++++-+#-++..-.
.+-+###+-+##++-.
.+-----+++-- ..
.+--------. .
.+++------... ..
-+-+++--------..--. .-
I see that your kernel description is '6.9.1-tkg-custom'. Did the Workstation installation run smoothly through the kernel module updater, or did you need to make modifications to the associated files? Or was Workstation first installed on an earlier kernel, and things just fell into place when there was a switch to your 6.9.1?
On Wed, May 22, 2024 at 1:25 PM Hyphaed @.***> wrote:
@rpressw https://github.com/rpressw I'm on ubuntu base and no problem running 17.5.2 with kernel 6.9.1
+###### .. #-+#############. +. .##+#################-. Uptime: 4 hours, 12 mins .#######+#+---..-+###### ###+#+---+-++--....+####. Ubuntu Customized OS -##+-----.--.. .. ..++## f2fs, custom kernel, nvidia open kernel ####---++---.-+++-. -#. configured targeting local hardware & work needs ##+-----....---- ## ##+------...-..-. .. -+ Kernel: 6.9.1-tkg-custom .##.+#####+++--+++++++ + Packages: 3462 (dpkg), 45 (flatpak) #+---+##++++. ++##-+-. + .#+-+++-+++++ +++ - + Shell: bash 5.2.21 +-++--+----- ..-.. DE: GNOME 46.1 ++--------++ ++ - WM: Mutter ++-+------#---+ .- Terminal: gnome-terminal +++-----#######++- .. +-+-##--+++++++++..- CPU: 11th Gen Intel i7-11700 (16) @ 4.800GHz +++--+----- + .. GPU: NVIDIA GeForce RTX 3070 -++-----####+. --.. RAM: 8306MiB / 64039MiB ++-++-----..-.-.. -++++++-+#-++..-. .+-+###+-+##++-. .+-----+++-- .. .+--------. . .+++------... .. -+-+++--------..--. .-— Reply to this email directly, view it on GitHub https://github.com/mkubecek/vmware-host-modules/issues/250#issuecomment-2125378658, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASRTBWAKYLTVYX2J4QYWVFTZDTIKFAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGM3TQNRVHA . You are receiving this because you were mentioned.Message ID: @.***>
@rpressw you need to compile the modules
check this other post, many of us had been testing even on 6.9rc
https://github.com/mkubecek/vmware-host-modules/issues/239#issuecomment-2124243195
I do not know which issues are you having with 6.8
I like 6.9.1 tkg :: it comes with Clear Linux patches and other interesting features, apart I like to compile it targeting the hardware I'm on and modprobed database modules (only the kernel modules I use). It offers many options to choose when compiling and/or to configure trough "customization.cfg"
https://github.com/Frogging-Family/linux-tkg
ubuntu came to exist as a tunned Debian version :: let's not stop tunning the system, there is no need to use everything as it comes out of the box/binaries
that's the beauty of the OS we all around like
I do use VMWare daily on my workflow, it is working with 0 issues here
It's obvious to me that if I want to use Workstation on 6.8, I would need to track down the changes necessary for the modules. After having to do this for several previous iterations of Workstation, I am fully tired of this. Since it doesn't burp on 6.5, I don't think that I have any problem. I wouldn't even mind if I had to run on a kernel in the 5 series. Accomplishing the work is my goal.
And I wasn't asking you to solve any issues for me. My curiosity was about how smooth the Workstation install was on your kernel, or whether you migrated to 6.9.1 after installation on an earlier kernel. This is a very minor question, and if you don't wish to answer, no big deal.
When I was younger, I tailored, compiled, and installed new kernels within a couple of weeks after their release. I admit that it was a lot of fun. Now I really don't have the time to dedicate to this. So I take the path of least resistance.
On Wed, May 22, 2024 at 3:51 PM Hyphaed @.***> wrote:
@rpressw https://github.com/rpressw you need to compile the modules
check this other post, many of us had been testing even on 6.9rc
#239 (comment) https://github.com/mkubecek/vmware-host-modules/issues/239#issuecomment-2124243195
I do not know which issues are you having with 6.8
I like 6.9.1 tkg :: it comes with Clear Linux patches and other interesting features, apart I like to compile it targeting the hardware of the workstation I'm nowdays, and modprobed database modules (only the kernel modules I use), it offers many options to choose when compiling and/or to configure trough "customization.cfg"
https://github.com/Frogging-Family/linux-tkg
ubuntu came to exist as a tunned Debian version :: let's not stop tunning the system, there is no need to use everything as it comes out of the box/binaries
that's the beauty of the OS we all around like
I do use VMWare daily on my workflow, it is working with 0 issues here
— Reply to this email directly, view it on GitHub https://github.com/mkubecek/vmware-host-modules/issues/250#issuecomment-2125632937, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASRTBWCOCMSGJ7YRUQ4LW4DZDTZNXAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGYZTEOJTG4 . You are receiving this because you were mentioned.Message ID: @.***>
@rpressw
if you got offended is your problem buddy, do not understand your rection
"And I wasn't asking you to solve any issues for me." haven't wrote at any time I was not interested into help you
just pointed you to the post where you will find more information. Since many people are there posting hat they found and what they did to solve the issues
I understand is just your bad mood
just be more specific and less aggressive next time, will help to make friends
I've installed it on 6.8.10 also :: yes
0 issue apart from 1 jut detected right now about not being able to "launch virtual network editor"
yet note I had been all day working with VMWare with 0 problems, using different guest machines
"Now I really don't have the time to dedicate to this. So I take the path of least resistance."
well, then why are you here? no offense
if you expect all out of the box then just do not lose your time, as for you is just losing time :: checking on github and/or other community places
you do that also when you go hungry to a restaurant? you just tell them you are not really there for the food? is because you are too proud of yourself and cannot merit the nice stuff they are cooking? or what's the problem exactly?
any way....
you are welcome
that's it
just giving an answer tailored to you
I sometimes forget how conversation on the internet is so different from face-to-face. I neglected to keep this in mind. If you could have heard my tone of voice and seen my face, you'd have had a good chance to know that there was no venom there.
My apologies for the words which did not convey the intent.
On Wed, May 22, 2024 at 6:37 PM Hyphaed @.***> wrote:
@rpressw https://github.com/rpressw
if you got offended is your problem buddy, do not understand your rection
"And I wasn't asking you to solve any issues for me." haven't wrote at any time I was not interested into help you
just pointed you to the post where you will find more information. Since many people are there posting hat they found and what they did to solve the issues
I understand is just your bad mood
just be more specific and less agressive next time, will help to make friends
I've installed it on 6.8.10 also :: yes
0 issue apart from 1 jut detected right now about not being able to "launch virtual network editor"
yet note I had been all day working with VMWare with 0 problems, using different guest machines
"Now I really don't have the time to dedicate to this. So I take the path of least resistance."
well, then why are you here? no offense
if you expect all out of the box then just do not lose your time, as for you is just losing time :: checking on github and/or other community placese
you do that also when you go hungry to a restaurant? you just tell them you are not really there for the food? is because you are too proud of yourself and cannot merit the nice stuff they are cooking? or what's the problem exactly?
any way....
you are welcome
that's it
just giving an answer tailored to you
— Reply to this email directly, view it on GitHub https://github.com/mkubecek/vmware-host-modules/issues/250#issuecomment-2125887317, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASRTBWHTFHDE4KHUIQH5VZLZDUM2DAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVHA4DOMZRG4 . You are receiving this because you were mentioned.Message ID: @.***>
Hello, sorry I'm consfused. Are we getting new modules or can we use the current ones? If using the current ones, what's the procedure to get it to work with 17.5.2?
I used this cookbook yesterday. It worked to enable 17.5.2 on kernel 6.8.0. Good luck! https://unix.stackexchange.com/questions/773558/vmware-vmmon-vmnet-17-5-1-and-linux-kernel-6-8-0-wont-compile
On Mon, May 27, 2024 at 11:09 AM Darius Davis @.***> wrote:
Hello, sorry I'm consfused. Are we getting new modules or can we use the current ones? If using the current ones, what's the procedure to get it to work with 17.5.2?
— Reply to this email directly, view it on GitHub https://github.com/mkubecek/vmware-host-modules/issues/250#issuecomment-2133669168, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASRTBWAKH7JEHOF2IPVPKW3ZENECTAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZTGY3DSMJWHA . You are receiving this because you were mentioned.Message ID: @.***>
I tried the @rpressw suggestion but with no luck I downloaded the 17.5.1 version just to be sure.... installed the mkubecek files, amended them editing timex.h but when I compile I get:
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
There are no errors, just a warning that the compiler is different from the one used to build the kernel and the following line:
Skipping BTF generation for /tmp/modconfig-7RfXAe/vmmon-only/vmmon.ko due to unavailability of vmlinux
which I am not sure is an error per se.
Anyone with a similar issue?
Thanks
As a shot in the dark, I didn't edit timex.h; just viewed it as an option should the main stuff fail. Also, I had 17.5.2 already in place after running it with an earlier 5.xx kernel.
Both gcc and the 6.8.0 kernel reported 13.2.0-23ubuntu4, and I still saw that error about a mismatch, so I don't understand the basis of that.
Again, good luck!
On Tue, May 28, 2024 at 3:43 AM PaoloPelloni @.***> wrote:
I tried the @rpressw https://github.com/rpressw suggestion but with no luck I downloaded the 17.5.1 version just to be sure.... installed the mkubecek files, amended them editing timex.h but when I compile I get:
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
There are no errors, just a warning that the compiler is different from the one used to build the kernel and the following line:
Skipping BTF generation for /tmp/modconfig-7RfXAe/vmmon-only/vmmon.ko due to unavailability of vmlinux
which I am not sure is an error per se.
Anyone with a similar issue?
Thanks
— Reply to this email directly, view it on GitHub https://github.com/mkubecek/vmware-host-modules/issues/250#issuecomment-2134550691, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASRTBWDJIPPBQGN2OZ62SG3ZEQYRLAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGU2TANRZGE . You are receiving this because you were mentioned.Message ID: @.***>
Tried this https://github.com/jvillavi/vmware17-ubuntu23.10 but also failed.
The vmmon e vmnet services fail to start even here.
Waiting for the 17.5.2 patch and see if this works.
I do not know if vmware is paying to mkubecek or not
Me either, but mkubecek has made my life much easier for YEARS.
If he wants to put a "Buy me a coffee" link or a PayPal I would be happy to send him some money.
really lovely work!
on tumbleweed as of today: kernel-default-devel-6.9.1-1.1.x86_64
/home/roeland/src/vmware-host-modules/vmnet-only/bridge.c: In function 'VNetBridgeReceiveFromVNet': /home/roeland/src/vmware-host-modules/vmnet-only/vmnetInt.h:44:39: error: 'dev_base_lock' undeclared (first use in this function); did you mean 'device_lock'? 44 | #define dev_lock_list() read_lock(&dev_base_lock) | ^~~~~~~~~~~~~ /usr/src/linux-6.9.1-1/include/linux/rwlock.h:56:48: note: in definition of macro 'read_lock' 56 | #define read_lock(lock) _raw_read_lock(lock) | ^~~~ /home/roeland/src/vmware-host-modules/vmnet-only/bridge.c:587:4: note: in expansion of macro 'dev_lock_list' 587 | dev_lock_list(); | ^~~~~~~~~~~~~ /home/roeland/src/vmware-host-modules/vmnet-only/vmnetInt.h:44:39: note: each undeclared identifier is reported only once for each function it appears in 44 | #define dev_lock_list() read_lock(&dev_base_lock) | ^~~~~~~~~~~~~ /usr/src/linux-6.9.1-1/include/linux/rwlock.h:56:48: note: in definition of macro 'read_lock' 56 | #define read_lock(lock) _raw_read_lock(lock) | ^~~~ /home/roeland/src/vmware-host-modules/vmnet-only/bridge.c:587:4: note: in expansion of macro 'dev_lock_list' 587 | dev_lock_list(); | ^~~~~~~~~~~~~ /home/roeland/src/vmware-host-modules/vmnet-only/bridge.c: In function 'VNetBridgeUp': /home/roeland/src/vmware-host-modules/vmnet-only/vmnetInt.h:44:39: error: 'dev_base_lock' undeclared (first use in this function); did you mean 'device_lock'? 44 | #define dev_lock_list() read_lock(&dev_base_lock) | ^~~~~~~~~~~~~ /usr/src/linux-6.9.1-1/include/linux/rwlock.h:56:48: note: in definition of macro 'read_lock' 56 | #define read_lock(lock) _raw_read_lock(lock) | ^~~~ /home/roeland/src/vmware-host-modules/vmnet-only/bridge.c:902:4: note: in expansion of macro 'dev_lock_list' 902 | dev_lock_list(); | ^~~~~~~~~~~~~
This repository contains a patched vmnet version of the module that claims to compile with kernel 6.9: https://github.com/nan0desu/vmware-host-modules/tree/tmp/workstation-17.5.2-k6.9.1
The repository is forked from this one here.
This repository contains a patched vmnet version of the module that claims to compile with kernel 6.9: https://github.com/nan0desu/vmware-host-modules/tree/tmp/workstation-17.5.2-k6.9.1
I used this successfully a few days ago w/vmw 17.5.2 and kernel 6.9.3 on a Slackware system. Appears to work fine.
$ git clone -b tmp/workstation-17.5.2-k6.9.1 https://github.com/nan0desu/vmware-host-modules.git
I used approach (2b) from the INSTALL instructions to replace the original module source tarballs with the patched ones: https://raw.githubusercontent.com/nan0desu/vmware-host-modules/tmp/workstation-17.5.2-k6.9.1/INSTALL
$ make tarballs
Copied the patched tarballs over the original tarballs (which I renamed with .orig) in the vmware install directory and then the normal process to build and install the modules,
$ vmware-modconfig --console --install-all
I am afraid that doesn't work for 6.8.0-31-generic neither using approach 2a and compiling against that kernel. Or at least not on my system.... but then I found the solution (which I copy here for convenience of the readers, but credit goes to: https://askubuntu.com/questions/1348250/skipping-btf-generation-xxx-due-to-unavailability-of-vmlinux-on-ubuntu-21-04
First install dwarves and copy the file to avoid the warning BTF:
apt install dwarves
cp /sys/kernel/btf/vmlinux /usr/lib/modules/uname -r/build/
Then make the modules with the appropriate command: make VM_UNAME='6.8.0-31-generic' sudo make install
Now it is time to sign the modules: openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=VMware/" import to UEFI database sudo mokutil --import MOK.der (generate a password need next step)
reboot system and import in UEFI BIOS (use same password) sudo shutdown -r now
once rebooted need to sign the binaries sudo kmodsign sha256 ./MOK.priv ./MOK.der $(modinfo -n vmmon)
sudo kmodsign sha256 ./MOK.priv ./MOK.der $(modinfo -n vmnet)
on reboot new signed binaries used sudo shutdown -r now
I run an Ubuntu 24.04 system (kernel 6.8.0-35-generic) and I just installed VMware Workstation 17.5.2 Pro. In my case vmnet does compile, vmmon does not. It throws the error also seen elsewhere, added add the bottom. Up and until know none of the possible solutions mentioned solved the issue. So many different setups even so many solutions to issues that seem alike but are not.
/shared/src/vmware-host-modules-w17.5.1/vmmon-only/common/crosspage.o: warning: objtool: CrossPage_CodePage+0x207: 'naked' return found in RETHUNK build make[3]: *** [scripts/Makefile.build:243: /shared/src/vmware-host-modules-w17.5.1/vmmon-only/common/crosspage.o] Error 255 make[3]: *** Deleting file '/shared/src/vmware-host-modules-w17.5.1/vmmon-only/common/crosspage.o' make[2]: *** [/usr/src/linux-headers-6.8.0-35-generic/Makefile:1926: /shared/src/vmware-host-modules-w17.5.1/vmmon-only] Error 2 make[1]: *** [Makefile:240: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.8.0-35-generic' make: *** [Makefile:117: vmmon.ko] Error 2
@Gabbelebab It did compile for me on same Ubuntu version, slightly different kernel, now I am on -35 and it is still fine.
Have you tried giving the kernel parameter (I suspect you did reading your output). make VM_UNAME='6.8.0-35-generic'
I had no Error 255
@PaoloPelloni Yes tried that option as well. from within the vmmon-omly folder I will investigate further. Update: and now also from the source root.
I've yet to test what I broke by doing this, but I got it to compile and install by adding this to crosspage.c: (borrowed from: https://stackoverflow.com/questions/75556275/how-to-address-textxxx-naked-return-found-in-rethunk-build-in-assembly-pa)
#if defined(CONFIG_RETHUNK) && !defined(__DISABLE_EXPORTS) && !defined(BUILD_VDSO) #define RET "jmp __x86_return_thunk\n" #else /* CONFIG_RETPOLINE / #ifdef CONFIG_SLS #define RET ret; int3 #else #define RET ret #endif #endif / CONFIG_RETPOLINE */
and "extern unsigned long random_get_entropy_fallback(void);" to timex.h
I've yet to test what I broke by doing this, but I got it to compile and install by adding this to crosspage.c: (borrowed from: https://stackoverflow.com/questions/75556275/how-to-address-textxxx-naked-return-found-in-rethunk-build-in-assembly-pa)
#if defined(CONFIG_RETHUNK) && !defined(__DISABLE_EXPORTS) && !defined(BUILD_VDSO) #define RET "jmp __x86_return_thunk\n" #else /* CONFIG_RETPOLINE / #ifdef CONFIG_SLS #define RET ret; int3 #else #define RET ret #endif #endif / CONFIG_RETPOLINE */
and "extern unsigned long random_get_entropy_fallback(void);" to timex.h
you just added it to the end of the file?
you just added it to the end of the file? No, the RET macro was added almost at the top of crosspage.c, right after the #ifdef linux section. The original line 646 of crospage.c reads "ret\n", that's what cause the warning. Changing it to "jmp __x86_return_thunk\n" directly instead of defining a macro makes it compile as well.
The line that was added to "/usr/src/linux-headers-6.8.0-35/arch/x86/include/asm/timex.h" is placed directly after the last include that was already there, so: #include <asm/processor.h> #include <asm/tsc.h> extern unsigned long random_get_entropy_fallback(void);
I don't know what side effects this might have created. Edit: not really up for signing them myself, will call it quits for a few days. Other stuff to do :-)