Ask Your Question
0

Fedora 23 VMware, error starting vmware.service via systemctl

asked 2016-03-13 10:24:17 -0500

Woodnerd gravatar image

updated 2016-03-13 12:11:57 -0500

hhlp gravatar image

I has formatted my laptop, and put fedora 23.
]$: dnf update, and update distro with last pakage, update has installed new kernel:4.4.4-301.fc23.x86_64

I has just installed installed gcc make && CO kernel header of my kernel version

launch truth terminal vmplayer that give me some error, not start. Google heps me with this: this guide

  1. Compile vmware modules
  2. Copy new libs
  3. Install modules

from point 2 vmware player start his windows, but launching virtual machine return error ERROR: Could not open /dev/vmmon: File o directory not exist. Please make sure that the kernel module `vmmon' is loaded.

Last point return error in systemctl start vmware.service

log of all this: /tmp/vmware/vmware-12712.log

2016-03-13T16:08:57.615+01:00| modconfig| I125: Log for VMware Workstation pid=12712 version=12.1.0 build=build-3272444 option=Release
2016-03-13T16:08:57.615+01:00| modconfig| I125: The process is 64-bit.
2016-03-13T16:08:57.615+01:00| modconfig| I125: Host codepage=UTF-8 encoding=UTF-8
2016-03-13T16:08:57.615+01:00| modconfig| I125: Host is Linux 4.4.4-301.fc23.x86_64 Fedora release 23 (Twenty Three)
2016-03-13T16:08:57.615+01:00| modconfig| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2016-03-13T16:08:57.615+01:00| modconfig| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2016-03-13T16:08:57.615+01:00| modconfig| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.
2016-03-13T16:08:57.615+01:00| modconfig| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2016-03-13T16:08:57.617+01:00| modconfig| I125: Initialized!  Lets do this thing...
2016-03-13T16:08:57.617+01:00| modconfig| I125: Obtaining info using the running kernel.
2016-03-13T16:08:57.617+01:00| modconfig| I125: Created new pathsHash.
2016-03-13T16:08:57.617+01:00| modconfig| I125: Setting header path for 4.4.4-301.fc23.x86_64 to "/lib/modules/4.4.4-301.fc23.x86_64/build/include".
2016-03-13T16:08:57.617+01:00| modconfig| I125: Validating path "/lib/modules/4.4.4-301.fc23.x86_64/build/include" for kernel release "4.4.4-301.fc23.x86_64".
2016-03-13T16:08:57.617+01:00| modconfig| I125: Failed to find /lib/modules/4.4.4-301.fc23.x86_64/build/include/linux/version.h
2016-03-13T16:08:57.617+01:00| modconfig| I125: /lib/modules/4.4.4-301.fc23.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-03-13T16:08:57.617+01:00| modconfig| I125: using /usr/bin/gcc for preprocess check
2016-03-13T16:08:57.623+01:00| modconfig| I125: Preprocessed UTS_RELEASE, got value "4.4.4-301.fc23.x86_64".
2016-03-13T16:08:57.623+01:00| modconfig| I125: The header path "/lib/modules/4.4.4-301.fc23.x86_64/build/include" for the kernel "4.4.4-301.fc23.x86_64" is valid.  Whoohoo!
2016-03-13T16:08:57.745+01:00| modconfig| I125: found symbol version file /lib/modules/4.4.4-301.fc23.x86_64/build/Module ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-03-14 07:46:28 -0500

Woodnerd gravatar image

I found a solution

systemctl start vmware.service continue return me error but it start virtual machine a look like working correct.
Solution was disable sercure boot flag into BIOS setting. It not permit to put into kernel, modules that are not signed. Then if you disable this flag recompile it work and can run virtual machine.

use lsmod for check if modules is loaded into kernel

edit flag offensive delete link more

Question Tools

Stats

Asked: 2016-03-13 10:24:17 -0500

Seen: 1,697 times

Last updated: Mar 13 '16