VMware Workstation 17.5.2 Pro has been released #250
Comments
|
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 |
|
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
<#250 (comment)>,
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 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)
<#239 (comment)>
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
<#250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASRTBWCOCMSGJ7YRUQ4LW4DZDTZNXAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGYZTEOJTG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
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
<#250 (comment)>,
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
<#250 (comment)>,
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
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
<#250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASRTBWDJIPPBQGN2OZ62SG3ZEQYRLAVCNFSM6AAAAABHWLRZBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGU2TANRZGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Tried this The vmmon e vmnet services fail to start even here. Waiting for the 17.5.2 patch and see if this works. |
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. |
|
I want to confirm that it is not compiling on Kernel 6.9. |
|
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': |
|
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. |
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.
I used approach (2b) from the INSTALL instructions to replace the original module source tarballs with the patched ones:
Copied the patched tarballs over the original tarballs (which I renamed with
|
|
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: First install dwarves and copy the file to avoid the warning BTF: Then make the modules with the appropriate command: Now it is time to sign the modules: reboot system and import in UEFI BIOS once rebooted need to sign the binaries sudo kmodsign sha256 ./MOK.priv ./MOK.der $(modinfo -n vmnet) on reboot new signed binaries used |
|
I run an Ubuntu 24.04 system (kernel 6.8.0-35-generic) and I just installed VMware Workstation 17.5.2 Pro. /shared/src/vmware-host-modules-w17.5.1/vmmon-only/common/crosspage.o: warning: objtool: CrossPage_CodePage+0x207: 'naked' return found in RETHUNK build |
|
@Gabbelebab Have you tried giving the kernel parameter (I suspect you did reading your output). I had no Error 255 |
|
@PaoloPelloni Yes tried that option as well. from within the vmmon-omly folder I will investigate further. |
|
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: #if defined(CONFIG_RETHUNK) && !defined(__DISABLE_EXPORTS) && !defined(BUILD_VDSO) and "extern unsigned long random_get_entropy_fallback(void);" to timex.h |
you just added it to the end of the file? |
I confirm - it works on my 6.9.4 kernel under Fedora 40 - of course vmware-netcfg does not work, but in my simple tests of various systems it does not matter - I am using the free version VMware-Pro-17.5.2-build-23775571, in currently from Broadcom. |
|
Hello, friends, it is my first time to install workstation, I see 17.5.2 patch is not yet to come. Can I have a quick setup, so that I can get my hand dirty quickly, playing with virtual machines while waiting for the patch to come? I have read through readme and I am confused about relationships between kernel versions and patch versions. Right now 17.5.1 patch is available, if I download 17.5.1 version of workstation, and use this patch, which version of kernel should I use? I have use 17.5.1 with kernel 6.8.0 on ubuntu 24.04. I have installed kali in the virtual machine. Thanks for making this possible, mkubecek. |
I can confirm that this worked for me also (only currently running VMware Workstation 17.5.1 not 17.5.2) Linux oryx-pro 6.9.3-76060903-generic #202405300957 └─(13:36:57)──> cat /etc/os-release ──(Wed,Jun19)─┘ I never actually noticed that vmware-netcfg didn't work. I had previously created another NAT network that I do need but I have not had to create any new networks since then (thankfully). Has that always been the case with the mkubecek/vmware-host-modules? Thanks @mkubecek |
I also confirm following the above worked. VMware Workstation Pro 17 |
No, this has never been the case with mkubecek/vmware-host-modules before - note, however, that the method described here and the modified driver source files themselves do not come from @mkubecek but from @nan0desu. To sum up - as you wrote - you must first have all possible network scenarios created using vmware-netcfg, and only at the very end introduce this modification to the installation of these drivers, because after this vmware-netcfg is not currently available and using the code as it is now works. |
I was pretty sure that, as you stated, everything has worked previously with the @mkubecek host modules. Hoping that @mkubecek updates his modules so that we can revert to updating the VMware Workstation modules as we all have done previously. Everything was still working for me (module updating) until the most recent updating that I did yesterday where the kernel was updated to 6.9.3-76060903-generic. |
Yep. Same here, exact same version. |
|
Had to modify the source to make it work with 6.9. Tested on debian testing. |
|
Issues: Application/VM freezes on starting it. Built and Tested for Kernal 6.9.3-76060903-generic (k6.9) for vmware-workstation and player - 17.5.2.23775571 (17.5.2) branched from tmp/workstation-17.5.0-k6.8 Error caused after make: dev_base_lock’ undeclared (first use in this function); did you mean ‘device_lock’? The issue is that 'dev_base_lock' is no longer used in newer kernel versions. Instead, we need to use a different mechanism for protecting the network device list. In modern kernels, this is typically done using RCU (Read-Copy-Update) mechanisms. changes done in these files
After compiling:
verify: incase of error:
|
|
@nan0desu what about the above patch? |
At least it compiles for 6.6.36-1-longterm and 6.9.7-1-default, don't have much time now to test how it works. |
works for me |
I meant workstation opens ups and all, but when you boot up a VM it doesn't freeze? Maybe I should try again? |
|
All, this comment is just to inform that @nan0desu and @Sharishth patches can be stacked and reported to compile: https://github.com/nan0desu/vmware-host-modules/commits/tmp/workstation-17.5.2-k6.9-sharishth/ |
Hi, Installed Ubuntu 24.04 yesterday and can confirm that this approach worked for me. Thanks for sharing very useful ! user@hostname:pts/0-> /home » user (1)
> sudo /etc/init.d/vmware status
[sudo] password for user:
Module vmmon loaded
Module vmnet loaded
user@hostname:pts/0-> /home » user (0)
> sudo /etc/init.d/vmware start
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Virtual ethernet done
VMware Authentication Daemon done
Shared Memory Available done
|
|
When trying to compile any of the recent branches listed here (both branches of nan0desu's and bytium's 17.5.2) with Arch's 6.9.10 kernel and headers I get |
|
I am thinking of a rollback both kernel and workstation probably to 6.5 and 17.5.0. before that I will try @nan0desu 's patch above in which he has implemented both of our contribution. And probably avoid generic ones. I would recommend all linux users to avoid updates that include kernel updates. That is why I am not going for 6.10 before the 6.9 generic one is resolved. I learned this from recent experience now. |
|
I upgraded my local installation from VMWare 17.5.1 to 17.5.2, and nothing but PROBLEMS. VMs which have worked fine for months won't boot up. This includes VMs with Windows, QNX, and Linux. VMs which have been running stably are hanging with Windoze showing high CPU utilization. Only way to resolve is to have VMWare terminate the VM. This also includes VMs with Windows, QNX, and Linux. I tried creating brand new VMs for Ubuntu 23.10 and 24.04, and both hung during creation at various locations. Tried this MANY times using variations of VM configurations -- memory: 4G, 8G, 12G; Processors: 1, 2, 4, 12; Side Channel mitigation both enabled and disabled; Nothing works. And then when one of my Ubuntu 23.10 sessions was stable-ish, apt update pulled new kernel files, and the next time I started it, V17.5.2 does the typical "I need to recompile modules vmmon and vmnet". But the compile for vmmon fails. Oh Joy. And Broadcom? Talk about USELESS! Hours online with support chats. Days waiting for responses when asking support questions via email. I have been a loyal VMWare paying customer with Workstation Pro and Fusion licenses going back almost 15 years. And all seems to be wasted by Broadcom's inane decisions regarding VMWare and licensing. I am going to TRY downgrading back to VMWare V17.5.1, but for now V17.5.2 is persona non grata. I would recommend garlic, crosses, and holy water before I would recommend V17.5.2 to anyone. |
|
I am running 17.5.2 form some time. Like a few days after it was released. Now, workstation officially does NOT support other configs besides what it has defined at launch of 17.5.2. Having said that, we have @mkubecek luckily who fixes the small issues comiling the modules. (Else you wouldn't be here, right? Now. I do run tumbleweed, fedora, ubuntu, rhel, sles, you name it as testsystems both virtual and on hardware. Even ky "kick ass" kernel versions just go well here. I start with the point where vmware "fails" with the known "recompile modukes" fails. Linux zeetak.invalid 6.9.9-1-default #1 SMP PREEMPT_DYNAMIC Thu Jul 11 11:31:54 UTC 2024 (8c0f797) x86_64 x86_64 x86_64 GNU/Linux roeland@zeetak:~/src> cd vmware-host-modules/ roeland@zeetak:~/src/vmware-host-modules> make && sudo make install && sudo systemctl restart vmware make -C vmmon-only and now it pops up. Having said that , sometimes (!) older vm's that are in a suspended state cannot be re-spun up and will throw errors. So, maybe you first take a breath, be sure your hardware and OS are ok (tbh: ubuntu or any derived from debian is not my favourite here and we don't use it for any serious workload we run here.) In any case, the build and make vmware work took the laptop 5 seconds. And it's an older laptop. So why not try to maually comile and share your issues instead of barking againts the wrong trees (vmware as well as here). |
|
Hello @nan0desu and @Sharishth , is there any change untill today? Are your stacked patches still working? |
I have tested after building, application runs but when I turn on the VM, it does not boot, just black window, I have to force kill the process. If there aren't any builds that work I think it's better to rollback to the previous compatible kernel and workstation version as I mentioned earlier. |
|
@Sharishth I run 6.10.3-1 (tw) and all works fine. The only time(s) I have issues starting up a vm is that when it is resuming from suspended state. And that does not happen often... just only whenever you have suspended it months ago etc. I use the default stuff from here not any other version that's been forked (as I don't have any reason to do so) . I didn't look back what issues you have faced but tell me what you did to start with. |
The only one that works well for me is https://github.com/nan0desu/vmware-host-modules/tree/tmp/workstation-17.5.2-k6.9.1 . This has worked on any 6.9.x and also working fine on 6.10.5 on my Slackware -current. Any other branch/patch has had problems for me. |
Which Distro are you using? |
|
pop_OS! 22.04, Kernel 6.9.3-76060903-generic |
I can confirm in work on kernel 6.10.9-200.fc40.x86_64 Fedora 40 |
and others
https://docs.vmware.com/en/VMware-Workstation-Pro/17.5.2/rn/vmware-workstation-1752-pro-release-notes/index.html
The text was updated successfully, but these errors were encountered: