Problem running vmPlayer on Fedora 21












1














After install the program and execute vmPlayer request the kernel headers to recompile it (I guess), after that vmP install the virtual network device, at this point show an error.



this one



and the vmware-15092.log file is:



  2015-03-27T22:51:28.154-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
2015-03-27T22:51:28.154-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
2015-03-27T22:51:28.158-06:00| vthread-4| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-03-27T22:51:28.158-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
2015-03-27T22:51:28.158-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
2015-03-27T22:51:28.158-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-03-27T22:51:28.158-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
2015-03-27T22:51:28.164-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
2015-03-27T22:51:28.164-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
2015-03-27T22:51:28.164-06:00| vthread-4| I120: Using temp dir "/tmp".
2015-03-27T22:51:28.165-06:00| vthread-4| I120: Obtaining info using the running kernel.
2015-03-27T22:51:28.165-06:00| vthread-4| I120: Setting header path for 3.19.1-201.fc21.x86_64 to "/lib/modules/3.19.1-201.fc21.x86_64/build/include".
2015-03-27T22:51:28.165-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
2015-03-27T22:51:28.165-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
2015-03-27T22:51:28.165-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-03-27T22:51:28.165-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
2015-03-27T22:51:28.171-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
2015-03-27T22:51:28.171-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
2015-03-27T22:51:28.288-06:00| vthread-4| I120: found symbol version file /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers
2015-03-27T22:51:28.288-06:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers.
2015-03-27T22:51:28.302-06:00| vthread-4| I120: Read 15286 symbol versions
2015-03-27T22:51:28.302-06:00| vthread-4| I120: Invoking modinfo on "vmnet".
2015-03-27T22:51:28.304-06:00| vthread-4| I120: "/sbin/modinfo" exited with status 256.
2015-03-27T22:51:28.381-06:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.19.1-201.fc21.x86_64/misc/vmnet.ko".
2015-03-27T22:51:28.381-06:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".


2015-03-27T22:51:28.385-06:00| vthread-4| I120: Successfully extracted the vmnet source.
2015-03-27T22:51:28.385-06:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3fL25O/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.1-201.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2015-03-27T22:51:29.709-06:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command.


Now I don't know what to do, any idea?










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    1














    After install the program and execute vmPlayer request the kernel headers to recompile it (I guess), after that vmP install the virtual network device, at this point show an error.



    this one



    and the vmware-15092.log file is:



      2015-03-27T22:51:28.154-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
    2015-03-27T22:51:28.154-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
    2015-03-27T22:51:28.158-06:00| vthread-4| I120: The GCC version matches the kernel GCC minor version like a glove.
    2015-03-27T22:51:28.158-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
    2015-03-27T22:51:28.158-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
    2015-03-27T22:51:28.158-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
    2015-03-27T22:51:28.158-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
    2015-03-27T22:51:28.164-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
    2015-03-27T22:51:28.164-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
    2015-03-27T22:51:28.164-06:00| vthread-4| I120: Using temp dir "/tmp".
    2015-03-27T22:51:28.165-06:00| vthread-4| I120: Obtaining info using the running kernel.
    2015-03-27T22:51:28.165-06:00| vthread-4| I120: Setting header path for 3.19.1-201.fc21.x86_64 to "/lib/modules/3.19.1-201.fc21.x86_64/build/include".
    2015-03-27T22:51:28.165-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
    2015-03-27T22:51:28.165-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
    2015-03-27T22:51:28.165-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
    2015-03-27T22:51:28.165-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
    2015-03-27T22:51:28.171-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
    2015-03-27T22:51:28.171-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
    2015-03-27T22:51:28.288-06:00| vthread-4| I120: found symbol version file /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers
    2015-03-27T22:51:28.288-06:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers.
    2015-03-27T22:51:28.302-06:00| vthread-4| I120: Read 15286 symbol versions
    2015-03-27T22:51:28.302-06:00| vthread-4| I120: Invoking modinfo on "vmnet".
    2015-03-27T22:51:28.304-06:00| vthread-4| I120: "/sbin/modinfo" exited with status 256.
    2015-03-27T22:51:28.381-06:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.19.1-201.fc21.x86_64/misc/vmnet.ko".
    2015-03-27T22:51:28.381-06:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".


    2015-03-27T22:51:28.385-06:00| vthread-4| I120: Successfully extracted the vmnet source.
    2015-03-27T22:51:28.385-06:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3fL25O/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.1-201.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
    2015-03-27T22:51:29.709-06:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command.


    Now I don't know what to do, any idea?










    share|improve this question
















    bumped to the homepage by Community 1 hour ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      1












      1








      1







      After install the program and execute vmPlayer request the kernel headers to recompile it (I guess), after that vmP install the virtual network device, at this point show an error.



      this one



      and the vmware-15092.log file is:



        2015-03-27T22:51:28.154-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.154-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: The GCC version matches the kernel GCC minor version like a glove.
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
      2015-03-27T22:51:28.164-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.164-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
      2015-03-27T22:51:28.164-06:00| vthread-4| I120: Using temp dir "/tmp".
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Obtaining info using the running kernel.
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Setting header path for 3.19.1-201.fc21.x86_64 to "/lib/modules/3.19.1-201.fc21.x86_64/build/include".
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
      2015-03-27T22:51:28.171-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.171-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
      2015-03-27T22:51:28.288-06:00| vthread-4| I120: found symbol version file /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers
      2015-03-27T22:51:28.288-06:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers.
      2015-03-27T22:51:28.302-06:00| vthread-4| I120: Read 15286 symbol versions
      2015-03-27T22:51:28.302-06:00| vthread-4| I120: Invoking modinfo on "vmnet".
      2015-03-27T22:51:28.304-06:00| vthread-4| I120: "/sbin/modinfo" exited with status 256.
      2015-03-27T22:51:28.381-06:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.19.1-201.fc21.x86_64/misc/vmnet.ko".
      2015-03-27T22:51:28.381-06:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".


      2015-03-27T22:51:28.385-06:00| vthread-4| I120: Successfully extracted the vmnet source.
      2015-03-27T22:51:28.385-06:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3fL25O/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.1-201.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
      2015-03-27T22:51:29.709-06:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command.


      Now I don't know what to do, any idea?










      share|improve this question















      After install the program and execute vmPlayer request the kernel headers to recompile it (I guess), after that vmP install the virtual network device, at this point show an error.



      this one



      and the vmware-15092.log file is:



        2015-03-27T22:51:28.154-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.154-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: The GCC version matches the kernel GCC minor version like a glove.
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
      2015-03-27T22:51:28.158-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
      2015-03-27T22:51:28.164-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.164-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
      2015-03-27T22:51:28.164-06:00| vthread-4| I120: Using temp dir "/tmp".
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Obtaining info using the running kernel.
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Setting header path for 3.19.1-201.fc21.x86_64 to "/lib/modules/3.19.1-201.fc21.x86_64/build/include".
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
      2015-03-27T22:51:28.165-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check
      2015-03-27T22:51:28.171-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64".
      2015-03-27T22:51:28.171-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo!
      2015-03-27T22:51:28.288-06:00| vthread-4| I120: found symbol version file /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers
      2015-03-27T22:51:28.288-06:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers.
      2015-03-27T22:51:28.302-06:00| vthread-4| I120: Read 15286 symbol versions
      2015-03-27T22:51:28.302-06:00| vthread-4| I120: Invoking modinfo on "vmnet".
      2015-03-27T22:51:28.304-06:00| vthread-4| I120: "/sbin/modinfo" exited with status 256.
      2015-03-27T22:51:28.381-06:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.19.1-201.fc21.x86_64/misc/vmnet.ko".
      2015-03-27T22:51:28.381-06:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".


      2015-03-27T22:51:28.385-06:00| vthread-4| I120: Successfully extracted the vmnet source.
      2015-03-27T22:51:28.385-06:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3fL25O/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.1-201.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
      2015-03-27T22:51:29.709-06:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command.


      Now I don't know what to do, any idea?







      fedora virtual-machine vmware






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 24 '17 at 6:23









      Kusalananda

      122k16230375




      122k16230375










      asked Mar 28 '15 at 5:09









      Gagaganlf

      62




      62





      bumped to the homepage by Community 1 hour ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 1 hour ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          try this, it works on VM Player too.



          VMware Workstation 11 fails to build vmnet on Fedora 21



          Greetings!






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f193049%2fproblem-running-vmplayer-on-fedora-21%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            try this, it works on VM Player too.



            VMware Workstation 11 fails to build vmnet on Fedora 21



            Greetings!






            share|improve this answer




























              0














              try this, it works on VM Player too.



              VMware Workstation 11 fails to build vmnet on Fedora 21



              Greetings!






              share|improve this answer


























                0












                0








                0






                try this, it works on VM Player too.



                VMware Workstation 11 fails to build vmnet on Fedora 21



                Greetings!






                share|improve this answer














                try this, it works on VM Player too.



                VMware Workstation 11 fails to build vmnet on Fedora 21



                Greetings!







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 30 '15 at 22:25









                PersianGulf

                6,89543461




                6,89543461










                answered Mar 30 '15 at 22:08









                Emmanuel Ayala Cortés

                1




                1






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f193049%2fproblem-running-vmplayer-on-fedora-21%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    濃尾地震