-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vmware modversion is wrong #2
Comments
|
I have uninstalled completely vmware and reinstalled it from scratch .... same issue The virtual machine is unable to reserve memory. If selecting Retry does not work, try closing programs on the host machine to free memory first. the version error comes up when I apply your patches |
as you can see I even tried to remove the tars before reinstalling so ... cd source/ |
the patch installs an old version I guess |
if you want I can give you the whole zipped tarball of the source dir |
For 14.0.0, you need the module source from branch workstation-14.0.0, not workstation-12.5.7. |
Those sources reappeared right after I removed them and reinstalled vmware workstation from scratch |
the error is now The virtual machine is unable to reserve memory. If selecting Retry does not work, try closing programs on the host machine to free memory first. |
if I install the ones from your git the version error appears |
please help |
Flooding me with more and more comments doesn't help anything. Please read what I already wrote to you and use the source from the branch matching your VMware version. |
Try downloading the 14.0.0 sources as a zipfile instead, using this link: https://github.com/mkubecek/vmware-host-modules/archive/workstation-14.0.0.zip .. Or have a look at the one-step installer script in the pull-request section, set VMWARE_PRODUCT="workstation-14.0.0" to make it match your product, and run that. |
Hi @rubyjedi
Version mismatch with vmmon module: expecting 329.0, got 308.0. Failed to initialize monitor device. Only I am using VMware WS 14.1 which was recently released. My host is Debian Sid but with kernel 4.12. I'm wondering if you have made a zipfile of the sources for this release or can provide me a link to the one step installer you mentioned. TIA Marty Felker |
Branches for Workstation and Player 14.1.0 are available now (tested against 4.9, 4.12, 4.13, 4.14 and 4.15-rc5). |
Hi, I am using Workstation 12.5.9 on Ubuntu Xenial with Kernel 4.13.0-26-generic. I tried to apply the patches from the 12.5.8 branch, as there is no 12.5.9 yet, but end up with the same
error message as the original poster. This is after cloning and checking out the branch, and running
The error only appears when trying to start a VM. If I try to build the modules manually, make throws these warnings for vmmon, but builds seemingly just fine.
when, after building manually, I
Searching for
gives me
when trying to start a VM. Any chance of getting this resolved in the near future, maybe in a 12.5.9 branch? Or do I need to fall back to 12.5.8 (or shell out the $$$ for WS Pro 14, which seems to work out of the box)? Kind Regards, |
err, of course that's "insmod ./vmmon.ko" in the last code block, not "./vmmon.ko". |
I'll prepare a branch for 12.5.9 this weekend but I can't test it (except for build) as don't have 12.5.9 installed anywhere. |
12.5.9 is a free upgrade to previous 12.5 releases; but if you don't have any 12.5 around, I'm willing and able to test. :) |
Branches workstation-12.5.9 and player-12.5.9 are ready now. It seems VMware is not going to fix build against recent kernels in 12.5.x as the only differences between 12.5.8 seem to be related to Meltdown/Spectre (and cleanup of unused files). In other words, unpatched 12.5.9 modules are broken with >= 4.13 (in less severe form since 4.9) and do not build with >= 4.14. Note: 12.5.9 branches are only build tested (I'm using only 14.x on my machines) but as the changes between 12.5.8 and 12.5.9 are unrelated, I'm quite confident there should be no problems (or at least no new problems). |
Hi I have the same problem with 12.5.9 and 4.13.0-26-generic (4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) "Version mismatch with vmmon module: expecting 309.0, got 308.0. So I followed the steps:
https://github.com/mkubecek/vmware-host-modules/blob/workstation-12.5.9/vmmon-only/linux/hostif.c
4 Tarred it up and reran:
Update: I've downgraded to 12.5.7 and applied your hostif.c patch for 12.5.7. vmware workstation starts up now. will report back if this solves my out of memory issue |
Picking one file from patched sources is rarely a good idea, I don't understand why some people give this kind of advice on various webs. Eiter pick a particular commit fixing your issue and apply it to the original sources from VMware or use complete patched sources from here. I added (into all active branches) a top level makefile and file Anyway... if anyone sees this message, it means he/she built their modules from wrong sources (based on module for a different version of Workstation / Player). It's possible, in theory, that I used wrong source tarball as a base for some branch but then everyone using that branch would encounter this kind of problem, not only some users. |
This issue is happening again. I think b/c the linux modules update soooo fast |
This is not an actual issue, this error message means the user used wrong module version meant for different Workstation/Player version. In other words, pure user mistake, not something to report here as an issue. |
ohhhhh your make file does not download the correct version of vmmon and vmnet, they have to be downloaded separately. |
No, you just need to checkout the right branch depending on your Workstation/Player version. Please read the README and INSTALL files, it's all explained there. |
Well, I have VMware-Player-Full-17.0.2-21581411.x86_64.bundle and I switched to branch tmp/workstation-17.0.2-k6.5 but I still get an error. I guess I need to switch to a newer version of VMWare :) |
There seems to be a disconnect here. Try the one-step bash installer script I submitted a while ago Set the vmware_product to "workstation-17.0.2" (this sets your branch) and run the script as root. |
@rubyjedi Thank you, that worked. Strange thing is, I had previously checked out branch workstation-17.0.2 before I tried tmp/workstation-17.0.2-k6.5. I do not really know why workstation-17.0.2 worked this time, but not before. But, thank you. |
I wish VMWare would release a flatpak version. Since I have Fedora, every single update breaks VMWare :( |
Help me save my job please :)
I am using 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 GNU/Linux and bumped into the memory bug:
The virtual machine is unable to reserve memory. If selecting Retry does not work, try closing programs on the host machine to free memory first.
For more information about this error, see "http://vmware.com/info?id=19".
applying your patches I get
Version mismatch with vmmon module: expecting 329.0, got 308.0.
You have an incorrect version of the 'vmmon' kernel module.
Try reinstalling VMware Workstation.
Failed to initialize monitor device.
The text was updated successfully, but these errors were encountered: