I'm using systemd and I'm trying to emerge vmware-modules but I cannot emerge, plus I cannot see nor start vmware service. kernel 3.14.14, stable branch up to date portage (2014-09-01) ben ~# uname -a Linux 3.14.14-gentoo #1 SMP Tue Aug 26 15:44:00 2014 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux I'm just using standard portage with stable packages but with systemd on it (shame on me) Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge vmware-modules NOTE: I don't have (yet) vmware service loaded because there's no trace of it in systemd services. My system has emerged app-emulation/vmware-player (6.0.2.1744117) but I didn't started it yet even if I've executed: - env-update && source /etc/profile - emerge --config vmware-player as suggested Actual Results: I cannot emerge vmware-modules even if I'm up to date and I have synced with portage tree Expected Results: I'd like to have vmware-modules emerged I cannot even start vmware service manually. I have created a vmware service for systemd with these information: ben ~# cat /usr/lib/systemd/system/vmware.service [Unit] Description=VMware network [Service] ExecStart=/opt/vmware/bin/vmware-networks --start ExecStop=/opt/vmware/bin/vmware-networks --stop PIDFile=/var/lock/subsys/vmware TimeoutSec=0 RemainAfterExit=yes [Install] WantedBy=multi-user.target (Hint: there's no vmware.service in portage, it could be nice to have it like this one) but after trying a start I get: ben ~# systemctl enable vmware ben ~# systemctl start vmware ben ~# systemctl status vmware vmware.service - VMware network Loaded: loaded (/usr/lib64/systemd/system/vmware.service; enabled) Active: active (exited) (Result: exit-code) since Mon 2014-09-01 09:39:43 CEST; 32min ago Main PID: 10536 (code=exited, status=1/FAILURE) Sep 01 09:39:44 ben vmnet-dhcpd[10601]: Sep 01 09:39:44 ben vmnet-dhcpd[10601]: Configured subnet: 192.168.113.0 Sep 01 09:39:44 ben vmnet-dhcpd[10601]: Setting vmnet-dhcp IP address: 192.168.113.254 Sep 01 09:39:44 ben vmnet-dhcpd[10601]: Cannot open /dev/vmnet8: No such device or address Sep 01 09:39:44 ben vmnet-dhcpd[10601]: exiting. Sep 01 09:39:44 ben vmware-networks[10536]: Failed to start DHCP service on vmnet8 Sep 01 09:39:44 ben vmware-networks[10536]: Failed to start some/all services Sep 01 09:39:44 ben vmware-networks[10536]: Started Bridge networking on vmnet0 Sep 01 09:39:44 ben systemd[1]: vmware.service: main process exited, code=exited, status=1/FAILURE Sep 01 10:12:14 ben systemd[1]: Started VMware network. Please see my portage and system information as attachment Thanks Ben
Created attachment 384042 [details] emerge --info '=app-emulation/vmware-modules-279.2::gentoo' emerge info app-emulation/vmware-modules
Created attachment 384044 [details] emerge -pqv '=app-emulation/vmware-modules-279.2::gentoo'
Created attachment 384046 [details] emerge vmware-modules (build output)
I have a fresh installation with kernel 3.14.14 no vmware stuff was there before this emerge. I have seen bug #521408 that seems to be pretty similar. Let me know if you need more information
Created attachment 384096 [details] vmware-modules-279.2.ebuild proposed ebuild for vmware-modules
Created attachment 384100 [details, diff] 279-linux-3.14.patch Proposed patch
Created attachment 384102 [details, diff] 279-vmblock-3.11.patch proposed patch
Created attachment 384104 [details, diff] 279-vmblock-3.12.patch proposed patch
I have figured out the problem and after some searches I have found these attached files : 279-linux-3.14.patch 279-vmblock-3.11.patch 279-vmblock-3.12.patch vmware-modules-279.2.ebuild Original credit goes to http://k53sv.blogspot.it/2014/04/app-emulationvmware-modules-2792gentoo.html where I have found these. Same kernel (stable and official on gentoo source tree right now) and same problems during compilation, after copying these patches and the ebuild I can confirm to emerge vmware-modules without troubles. Please take a look at these edits to see if it could be a nice idea to merge them in the stable branch tree. Let me know if there're further news Ben
*** This bug has been marked as a duplicate of bug 462666 ***
