1 2 Previous Next 19 Replies Latest reply on Jun 8, 2019 12:18 AM by paolol

    fedora 30 kernel 5.1 vmmon fail to biuld

    paolol Novice

      Hi,

      I just find out that with the new kernel 5.1.5-300.fc30.x86_64 th vmmon is not building

      If I run

      sudo vmware-modconfig --console --install-all

      I get a lot of errors, but all works fine if I start with the old 5.0.xx kernel.

      I also try downloading and reinstalling from fresh, same issue.

      let me know if you need the logs to fix this issue.

      Thanks,

      paolo

        • 1. Re: fedora 30 kernel 5.1 vmmon fail to biuld
          CitizenVM Lurker

          I have the same exact issue with Fedora 30.

           

          It seems every time a new kernel is released...Workstation breaks.

           

          VMware should incorporate a new system to ensure this doesn't happen almost every time a kernel is released....

          • 2. Re: fedora 30 kernel 5.1 vmmon fail to biuld
            mkubecek Enthusiast

            You need patched version of the host modules (only two latest patches are strictly necessary but I would recommend building from branch head anyway).

            • 3. Re: fedora 30 kernel 5.1 vmmon fail to biuld
              paolol Novice

              @

              • 4. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                paolol Novice

                Installed but still no vmmon when I run the VM, think you need to update your code.

                Let me know if you I can help.

                • 5. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                  mkubecek Enthusiast

                  The patched module builds against anything up to current mainline (as of this morning). If it does not build for you, please show the error(s).

                  • 6. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                    paolol Novice

                    Hi, no no errors on building the modules all seem OK but when I start the VM I still get the error on vmmon not loaded.

                    thanks

                    • 7. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                      mkubecek Enthusiast

                      Did you run "/etc/init.d/vmware restart" after rebuilding the module and installing it to the right place? You can also use "lsmod" to check if the module is loaded and if it is, compare srcversion from /sys/module/vmmon/srcversion with one shown by "modinfo vmmon" or modinfo applied to vmmon.ko you just built.

                      • 8. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                        paolol Novice

                        Thanks mkubecek, for you help.

                        I did a new rebuild and now it works fine, think is my fault but no idea how happen.

                        Paolo

                        • 9. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                          JackShaftoe Lurker
                          I had a somewhat related (oddball) FC30 issue recently that was due to my kernel-devel package being one minor release higher than my other kernel-* packages. I'm guessing that they were out of sync in the repo for a bit, since it resolved itself after checking for new updates (which included the matching kernel-* packages). This is probably not a likely scenario, but it may be worth checking to see if your kernel-* packages are behaving properly.
                          • 10. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                            JackShaftoe Lurker

                            VMware should incorporate a new system to ensure this doesn't happen almost every time a kernel is released....

                            this. times eleventybillion.

                            • 11. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                              VijayNehaOm Novice

                              Sorry to bother you but I am very new to Linux and am still having difficulty getting Workstation to run.  I am getting  a Version mismatch with vmmom module: expecting 361.0, got 360.0  You have an incorrect version of the vmmon kernel module.  try reinstalling.  I am running Fedora 30 5.1.6-300.fc30.x86_64 with Workstation 15.1.0

                              Do you have an idiots guide to make this work?  Please?

                              Vijay

                              • 12. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                                mkubecek Enthusiast

                                it may be worth checking to see if your kernel-* packages are behaving properly

                                That would certainly be useful but it's not clear (to me) how to do it. Maybe by trying to build a trivial "hello, world" module which would be so simple that it would be rarely (if ever) affected by changes in kernel API. I'll think about it.

                                • 13. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                                  mkubecek Enthusiast
                                  I am getting  a Version mismatch with vmmom module: expecting 361.0, got 360.0

                                  This means that you are trying to run newer VMware binary while vmmon module intended for an older version is loaded. Two most likely reasons are:

                                  • you used wrong branch for build (in this case, version 360 means 15.0.0 through 15.0.4)
                                  • you either forgot to install the new module or did not reload it (/etc/init.d/vmware restart)
                                  • 14. Re: fedora 30 kernel 5.1 vmmon fail to biuld
                                    mkubecek Enthusiast

                                    VMware should incorporate a new system to ensure this doesn't happen almost every time a kernel is released....

                                    First of all, as long as the host modules are developed as out-of-tree, this is going to happen. Linux kernel does not maintain stable API for modules; in-tree modules are naturally updated when such API change happens but out-of-tree ones are on their own. So the best solution would be upstreaming the remaining two host modules like the three which have been in mainline since quite some time (3.9 or so, IIRC). But that would require some work and maybe also some changes (some design decision in vmnet might be questioned and even in vmmon which is not my area of expertise I've seen things that would raise some eyebrows). That would be the ideal long term solution.

                                     

                                    In less ideal - but still much better - world, VMware would be providing updated module sources, at least as source tarballs (if not a git repository). But first someone would have to decide it's worth the effort for them. Aparently noone did, I suspect that big part of it is that VMware, as a big company, thinks in the scheme of "supported host systems", not kernel versions. Therefore they feel no need to support a new mainline kernel version until there is a major distribution release with it so that they can add a new entry to the list of "supported host systems". "Rolling" distributions or even people running latest mainline kernel, that's still a foreign concept for them and they simply don't care enough.

                                     

                                    As for having a Workstation/Player release updated to work with new kernel release as soon as it is out, I'm afraid it's unrealistic to expect. This time, they did not support even the new Window 10 update at the time it was released. The 15.1.0 release timing was apparently determined by disclosure of latest batch of Intel CPU vulnerabilities and everything else was secondary. What is sad is that even if 15.1.0 was released after kernel 5.1, they didn't include build fixes for it even if they were trivial and problems had been known for almost two months - I doubt their QA process takes that long. But that's the same problem as in previous paragraph, thinking in the terms of "supported host systems" rather than kernel versions.

                                    1 2 Previous Next