Unable to build the vmmon module uisng a 4.3.0 core - 1 - virtual machine monitor [failed]

Similar Questions

• Core 3.2.1 and WS 8.0.1 (impossible to build the vmmon module)

  Hello

  I try to compile WS 8.0.1 on my Debian 6, but I can't do it!

  # vmware-modconfig - console - install-all

  Stopping VMware services:
  Demon of authentication makes VMware
  VM communication interface socket family is
  Virtual machine communication interface is
  Virtual machine monitor makes
  File system is blocking
  Using 2.6.x kernel build system.
  do: entering no diretorio ' / tmp/vmware-root/modules/vmmon-only '.
  do /lib/modules/3.2.1-yamane/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. \
  MODULEBUILDDIR = modules
  make [1]: entering no diretorio ' / home/yamane/kernel/linux-3.2.1'
  CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
  CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
  /tmp/vmware-root/modules/vmmon-only/Linux/IOMMU.c: in function 'IOMMU_AdjustMappings ':
  /tmp/vmware-root/modules/vmmon-only/Linux/IOMMU.c:180: error: implicit declaration of function 'iommu_found '.
  /tmp/vmware-root/modules/vmmon-only/Linux/IOMMU.c: in function 'IOMMU_RegisterDevice ':
  /tmp/vmware-root/modules/vmmon-only/Linux/IOMMU.c:415: error: too few arguments to function 'iommu_domain_alloc '.
  make [2]: * [/ tmp/vmware-root/modules/vmmon-only/linux/iommu.o] error 1
  make [2]: * waiting for the completion of all processes.
  make [1]: * [_module_/tmp/vmware-root/modules/vmmon-only] error 2
  make [1]: leaving directory ' / home/yamane/kernel/linux-3.2.1'
  make: * [vmmon.ko] error 2
  make: leaving directory ' / tmp/vmware-root/modules/vmmon-only '.
  Cannot install vmmon

  # cat modconfig - 5447.log

  
  2012 01-22 T 21: 24:07.716 - 03:00 | modconfig | I120: Log for VMware Workstation nest = 5447 version 8.0.1 = build = build-528992 option = output
  2012 01-22 T 21: 24:07.716 - 03:00 | modconfig | I120: The process is 32-bit.
  2012 01-22 T 21: 24:07.716 - 03:00 | modconfig | I120: Host codepage = UTF-8 encoding = UTF-8
  2012 01-22 T 21: 24:07.716 - 03:00 | modconfig | I120: Host is Linux 3.2.1 - yamane Debian GNU/Linux 6.0.3 (squeeze)
  2012 01-22 T 21: 24:07.661 - 03:00 | modconfig | I120: Msg_Reset:
  2012 01-22 T 21: 24:07.661 - 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.
  2012 01-22 T 21: 24:07.661 - 03:00 | modconfig | I120: ----------------------------------------
  2012 01-22 T 21: 24:07.661 - 03:00 | modconfig | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.
  2012 01-22 T 21: 24:07.661 - 03:00 | modconfig | I120: Msg_Reset:
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/config ': no such file or directory.
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: ----------------------------------------
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: Optional preferences PREFS not found in root/.vmware/config file. Using the default values.
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: Msg_Reset:
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/preferences ': no such file or directory.
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: ----------------------------------------
  2012 01-22 T 21: 24:07.662 - 03:00 | modconfig | I120: PREF cannot load the user's preferences.
  2012 01-22 T 21: 24:07.716 - 03:00 | modconfig | I120: modconf initialized request interface
  2012 01-22 T 21: 24:07.717 - 03:00 | modconfig | I120: modconf library initialized
  2012 01-22 T 21: 24:07.719 - 03:00 | modconfig | I120: Trying to find a suitable for the core 3.2.1 - PBM yamane.
  2012 01-22 T 21: 24:07.720 - 03:00 | modconfig | I120: Your GCC version: 4.4
  2012 01-22 T 21: 24:07.720 - 03:00 | modconfig | I120: Validation/lib/modules/preferred/build/include path for the core version 3.2.1 - yamane
  2012 01-22 T 21: 24:07.720 - 03:00 | modconfig | I120: Could not find /lib/modules/preferred/build/include/linux/version.h
  2012 01-22 T 21: 24:07.720 - 03:00 | modconfig | I120: Failure of test version: /lib/modules/preferred/build/include/linux/version.h not found.
  2012 01-22 T 21: 24:07.720 - 03:00 | modconfig | I120: Validation of path /lib/modules/3.2.1-yamane/build/include for 3.2.1 - kernel version yamane
  2012 01-22 T 21: 24:07.721 - 03:00 | modconfig | I120: Your GCC version: 4.4
  2012 01-22 T 21: 24:07.726 - 03:00 | modconfig | I120: Your GCC version: 4.4
  2012 01-22 T 21: 24:07.750 - 03:00 | modconfig | I120: Header path /lib/modules/3.2.1-yamane/build/include for 3.2.1 - yamane of kernel version is valid.
  2012 01-22 T 21: 24:07.838 - 03:00 | modconfig | I120: Trying to find a suitable for the core 3.2.1 - PBM yamane.
  2012 01-22 T 21: 24:07.838 - 03:00 | modconfig | I120: Validation of path /lib/modules/3.2.1-yamane/build/include for 3.2.1 - kernel version yamane
  2012 01-22 T 21: 24:07.839 - 03:00 | modconfig | I120: Your GCC version: 4.4
  2012 01-22 T 21: 24:07.845 - 03:00 | modconfig | I120: Your GCC version: 4.4
  2012 01-22 T 21: 24:07.865 - 03:00 | modconfig | I120: Header path /lib/modules/3.2.1-yamane/build/include for 3.2.1 - yamane of kernel version is valid.
  2012 01-22 T 21: 24:07.865 - 03:00 | modconfig | I120: Building module vmmon.
  2012 01-22 T 21: 24:07.865 - 03:00 | modconfig | I120: Extract the sources of the vmmon module.
  2012 01-22 T 21: 24:07.871 - 03:00 | modconfig | I120: Module construction with the command: / usr/bin/make-j - C/tmp/vmware-root/modules/vmmon-only self-build SUPPORT_SMP = 1 HEADER_DIR=/lib/modules/3.2.1-yamane/build/include CC = / usr/bin/gcc = GREP / usr/bin/make IS_GCC_3 = no VMCCVER = 4.4.5
  2012 01-22 T 21: 24:10.155 - 03:00 | modconfig | I120: Unable to build the vmmon module.

  Completely uninstall WS.  Run the againî installation program and immediately apply the update 3.2 day form heliohost.   The links are everywhere in this list that the insataller will say that WS has been properly installed-it's not unless you apply the patch to the kernel of 3.2.  Change the version of the script for patch 8.0.1 or 4.0.1

• the virtual machine monitor driver required by the virtual machine is missing

  Hello
  After you install virtual pc xp2 and when I run this program I got this messege (the virtual machine monitor driver required by the virtual machine is missing)
  What is the answer

  Hi jameelaswad,

  The question you have posted is better suited in the forums of Virtual PC. Please see the following link for more information.

  Windows Virtual PC / Windows XP Mode Forum

• Unable to build the dimension.

  Hello
  I use currently version 6.1.4 in Essbase to add a few members of the contour using a dimension create the rule.
  But, whenever I try to build the dimension using my dimension build rule it give the error.
  
  Network (10054) error: Cannor receive data.
  
  When I press Ok at the prompt, it appears another error.
  
  Network (10054) error: cannot send data.
  
  And when I press Ok again, the line disappears.
  
  Now, when I try to disconnect from the server, it displays a message saying that "the application is not responding.
  
  Well want to, help me to solve this problem.
  
  TIA,
  Gerard.

  There are a lot of reasons, you may receive this message. This means something bad happened and the application stops instead of is wrong. IT really does not give you the root cause of the problem.

  You mention that you're building dimensions. May is the dense dimension? If so, it is possible, you are adding enough members that blow you to the top of the block size and using all of the available memory. I saw the question before (especially if dense and fragmented are not set correctly)

  If it is a BSO cube, you could try opening you outline and selection the MEMU contour hierarchical update. It is based the dimension without saving it in order to see what the impact of the Sun building. If it works there, I bet that when you try to save it is when you have questions. If so, try to check the pattern to see if it shows you the problem

• Unable to start the virtual machine after failing to remove the snapshot

  Recently, I tried to delete a snapshot on a Windows XP virtual machine in VMware server 2.0. After a few minutes, the operation has failed, then the GUI crashed. I was not able to manage one of my virtual machines until I rebooted the server. My other virtual machines still work fine. I can't just run the virtual machine on which I tried to remove the snapshot. This virtual machine is very important to me and I would try to get it back. Does anyone have advice? Also, I upgraded this version of VMware server 1.x to 2.x, so please let me know if this may have something to do with this problem. Thanks in advance.

  An additional note. If the virtual machine starts, I suggest that you run chkdsk, just to make sure that there are no problems with the file system of the client.

  André

• Confused over the upgrades and full versions for Windows 8 on a virtual machine

  Hello

  I am wanting to legally install Windows 8 or 8.1 on a virtual computer. When I look at the Microsoft pages only, they seem to offer Windows 8 one update and I can't find a way to the purchase of a previous version either. Is anyone able to point me to an explanation in plain English what I should buy.

  Thanks for your help.

  If you need to install Windows 8 in a virtual machine, you must purchase the full version of license OEM System Builder. If you need to install Windows 8.1 in a virtual machine, you can buy the license of retail sales (which is a full version) or OEM System Builder License.

• Can I use the Windows Vista I had with my Toshiba laptop on virtual machine?

  Hey all

  I have changed Microsoft for Macintosh, but installed on a virtual machine (oracle vm virtual machine) my Windows Vista I got with my Toshiba Satellite A350D Notebook previous. I installed Vista with the recovery disk. Now he asks me the Windows Vista product key. The sticker on the back of my laptop is more readable. I run the Belarc Advisor to get the product key in this way. But right now, he said: "it's the product key installed at the factory by the manufacturer rather than yours. You can change this to your product key here for Windows http://go.microsoft.com/fwlink/?LinkId=45668"

  My question: am I not allowed to use windows vista legally, I had with my computer toshiba laptop on other devices? I won't use the Thoshiba laptop. Do I have to delete the record from the Thoshiba laptop? Where can I get a new product key?

  Maybe someone can help me here. Thank you in advance for taking your time to read this.

  Betty

  Recovery disk or recovery image is designed for some cell phone only and is not a kind of universal image that can be used on other devices. It comes with the laptop.

  You can use the Microsoft Windows disk with valid license on each device. Recovery image is not only BONES. This is the package that contains the drivers and tools specific to Toshiba and utilities.
  As you also know recovery image when you install it on your laptop must be turned on not so the license code downstairs just proves you have purchased a valid license with your laptop.
  > Should I remove the record of the Toshiba laptop?
  Not why do this?
  > Where can I get a new product key?
  You cannot get it because you need when you use the recovery image on your Satellite A300D. I think even you will hear of Toshiba.

• I forgot the password of Windows 8, try to re - format the PC and no access to Windows XP on a virtual machine.

  Original title: need to reformat windows 8 and windows xp

  Hello

  2 questions here:

  1. my problem is that I have a PC under Windows 8, but I forgot the password, I can not connect using the admin account too. So, reformat my PC is the only solution?

  2. If I need to reformat the PC, the virtual machine (Windows XP) my colleague who installed in this PC will be too lost and product key has been purchased via online and now I don't know where to find the product key now. :( . How can I do to get the product key because I can not even access the pc host (Windows 8)?

  Hello

  1. you are using a third-party virtual machine?

  2. are you referring to Windows 8 or XP product key? Where did you get the product key from?

  3. you use a Local account or a Microsoft account to access Windows 8?

  4. you remember changes to the computer before the show?

  You can check the article to recover the password and check if it helps.

  What to do if you forget your Windows password

  Hope the helps of information. Let us know if you need help with Windows related issues. We will be happy to help you.

• The State of Transition (VM_STATE_ON-> VM_STATE_CREATE_SNAPSHOT) not allowed for this virtual machine

  Can't figure this one out and search Google is not come with much.

  I have 13 virtual machines in my environment.  They all use the same data store.  11 of them have no problems, but 2 of them fail with this error when you try to make a snapshot.

  I tried to reboot the hypervisor and vmware vsphere services.  I tried to remove and add the virtual machines of the inventory.  None of the VMs directories have snapshot of the files already.

  This usually means that you have material non-quiescable, as a tape device connected, or you have a persistence of defined virtual disk.  I recomment you latter by default and try again, because this is the typical cause.  Otherwise, other suspects are raw disk mappings (a fibre channel LUN) sent directly to your virtual machine, which cannot be suspended or IO DirectPath devices (USB or PCI cards series you will cross TSE of the VM).  If this is the case, you're probably SOL.

  I strongly suspect that you're a mode not supported on the persistence on a virtual disk to your virtual machine.

• The host CPU is not able to run 64-bit virtual machines

  I am running VMWare Server Console on a Windows 2003 64 bit OS 1.0.3 and prepare to create a 64-bit VM server to test a new application on.  This forum server works on is a SuperMicro SuperServer 6025 B - TR +.  I entered the bios and activated the virtual bios in the CPU settings.  However, when I start my VM, I get the following error:

  «You have configured the virtual machine as an operationg system 64-bit client.»  However, this host processor is not able to run 64-bit virtual machines or this virtual machine has 64-bit support disabled.

  I looked online and saw some references to allow an EM64T which was to be activated but I do not see this option in my BIOS.  Someone at - it any other suggestions as to what I have to do to get the virtual machine to use the 64-bit compatibility.

  Unfortunately, the 1.x server logs are a little sparse in this regard.  However, it seems that you have mixed steppings of physical processors.  In this range of models, Intel changed the VMCS review between the Bx steppings and Gx steppings ID, making it incompatible for the execution of VT - x.  Realizing their mistake, Intel has provided to OEMS for a microcode patch that makes the revision ID the Gx stepping VMCS matches that of the Bx stepping.  OEMs distribute this patch of microcode as a BIOS update.

  In short, an update of the BIOS of your system provider should solve the problem.

• VMWar merger 5: With the vmmon module Version mismatch: expected 271.0, obtained 267.0.

  You have a bad version of the module kernel "vmmon.
  Try reinstalling VMware Fusion.
  I completely deleted Version 4 according to the instructions and reinstalled Fusion 5 two times and I still get this error. Help!

  Hi baellis,

  We had reports that sometimes the core of Fusion extensions 'stuck' in a way that can only be cured by restarting the computer host computer.

  If you haven't already done so, can you try to restart after the installation of Fusion 5, then see if it works?

  A restart should not be necessary in the majority of cases, but some users have found that it is necessary after the upgrade/update of Fusion.

  See you soon,.

  --

  Darius

• How the Network Server 2003 Active Directory, DNS, DHCP with other virtual machines

  Hi ~

  I am trying to create a network within the workstation test environment. I did research on everyday and can't find a direct answer. I want to do is use the Server 2003 functions and create my own private network with the 2 other VMS XP Active Directory domain controller. I want both of these XP machines to be able to log into the domain of the 2003 server. I have never used or learned 2003 server, that's why I do this.

  What do I need to create a custom network? can I use bridged, host-only, nat? Stop the service DHCP from Vmware workstation?

  What is your host operating system and how to get its IP address? What is the result of: ipconfig/all in Windows or Linux ifconfig-a?

  Disable the firewall during installation.

  I don't think that the network connection is all that matters (if you care on the internet or a local area network LAN) for guests, while they are the same. I always use filled but the only thing that really counts, IMHO, is that the host, guests of the XP and W2003 prompt are all on the same subnet and the server has a static IP address.

  I almost always use open for all guests. I put all the guests for static IP addresses on the same subnet as the host. I put the DNS server for XP clients to the IP address of the host to W2003. I have install the DNS role on W2003 server and then install the role of domain controller (AD), with the help of a domain name like lousdomain.local. Then you should be able to join XP guests to this area.

  It's all exactly the same as if it was real machines.

  My default installation is filled with the IP host is defined on 10.0.3.5, a gateway of 10.0.3.1 (my ADSL router), my server W2003 (or W2008) the 10.0.3.4 value and guests XP, the value to something like 10.0.3.6, 10.0.3.7 etc. Again, once again, is not the same as little care as long as they are on the same subnet.

  What are the errors you get when you try to set up?

  What you get from ipconfig/all on each of the guests?

  Lou

• How to solve the problem of VMWare Workstation 8 - unable to open/dev/vmmon

  Initially, I had this problem in March 2011 after installing VMWare Workstation 7 on a lab machine 5.7 RHEL and attempt to boot an image I know was good and should work. .  Someone else fixed the problem for me - I think they had to install a new/different libraries (vmmon.o and vmnet.o for vmware).  However, I find no information detailing what has been done to solve the problem.

  I see the same error on the same machine after upgrading to VMWare Workstation 7.0 for VMWare Workstation 8.0.

  1 here are the mistakes I see:

  a. "Could not open/dev/vmmon.

  b. "failed to initialize the surveillance apparatus.
  c. "cannot change the power state of VM: cannot find a valid peers to connect to.

  Also, when I run the stop etc/init.d/vmware, then run /etc/init.d/vmware start, I see that the State of "Virtual Machine Monitor" is DOWN.

  
  2 here is the information on VMWare Workstation:

  VMWare Workstation 8.0.1 build 528992

  3 here is the RHEL uname - information for the host:

  2.6.18 - 274.7.1.el5xen Linux #1 SMP xxx.xxx.xxx kills Oct 17 12:06:22 EDT 2011 x86_64 x86_64 GNU/Linux
  Release of RedHat Enterprise Linux Server 5.7 (Tikanga)

  The problem could be that the version of vmmon.o and vmnet.o that comes by default with vmware does not work with linux kernel version I have on my system.  I think I need to build a new vmmon.o and vmnet.o on my particular 5.7 RHEL.

  I found that to build a new version of vmmon.o you Executive vmware - config.pl.  I have not just on my machine, and I was not able to find on the internet.

  Here is the version of vmmon.o (for RHEL 5) that I have installed on my machine:
  /usr/lib/VMware/modules/binary/BLD-2.6.18-8.EL5-x86_64smp-RHEL5/objects/vmmon.o

  Here is the version of rhel5 I use:
  2.6.18 - 274.12.1.el5xen
  It is possible that the vmmon.o using bld - 2.6.18 - 8.el5 - x86_64smp-RHEL5 is not compatible with the kernel 2.6.18 - I 274.12.1.el5xen.

  Please help me find vmware - config.pl so I can build my own vmmon.o and vmnet.o

  do not use a kernel XEN enabled when you install Workstation

• VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host

  Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.

  After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:

  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit.
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final)
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values.
  2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash.
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon".
  2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
  2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
  2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock".
  2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci".
  2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock".
  2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7".
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
  2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7".
  2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
  2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
  2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko".
  2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
  2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source.
  2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
  2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.
  
  
  

  Hi, I faced the same problem, and now I have corrected this issue.

  He was vmnet.ko, at least for me.

  Here's how to solve,

  You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko

  Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.

  And then run vmware, if you fail at the first, please run again.

  If so, you can run vmwre!

  I hope this will help you.

  Good day.

• Vmmon module kernel does not not on Fedora 21 w / 11 workstation

  Don't know if anyone else has questions nightmare on Fedora with VMware and other...

  After getting through the questions with the headers of the kernel, GCC, etc... for the installation is successful, I set up a machine and try to start it but get:

  Error: Unable to open/dev/vmmon: no such file or directory. Please ensure that the "vmmon" kernel module is loaded.

  I did a lot of research and VMwares Ko, communities, as seems to be a coherent question. I have also crossed a lot of 3rd party sites too, but nothing of the resolution.

  I used the following corrections but no luck:

  • "Could not open/dev/vmmon: no such file or directory." Please make sure that the "vmmon" kernel module is loaded. " -which States:

    • MV/usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

      ... See the section below for the reconstitution of the modules

  • vmware-modconfig - console - install-all - to (re) construction of the modules for later
  • Checking service in /etc/init.d/ and attempted to launch and get:

  Starting VMware services: Virtual machine monitor [FAILURE] Virtual machine communication interface [OK] VM communication interface socket family [OK] Block the system files [OK] Virtual Ethernet [FAILURE] [OK] VMware authentication daemon

  • Tried to add vmmon kernel usage: modprobe vmmon, but get the error: modprobe: ERROR: could not insert 'vmmon': the button is not available

  
  

  I don't know there is something simple that I'm missing, right?  It seems that before the service can run just, I must get vmmon working properly?

  
  

  Journalctl newspapers attached as well.

  
  

  Thanks for your help!
  

  
  

  
  

  I encountered exactly the same problem and finally solved by disabling "Secure Boot" from the BIOS.

  When "Secure Boot" is enabled, the unsigned kernel extensions will be not allowed to load. vmmon. Ko and vmnet.ko are of course not signed with cert of Fedora, so they will not work.