Bug 523390 – app-emulation/vmware-modules-279.2 with hardened kernel 3.15.8 - /work/vsock-only/linux/notifyQState.c:785:4: error: invalid initializer

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Shawn C 2014-09-21 16:37:35 UTC]

Created attachment 385244 [details]
build.log

I've installed every patches from here:
https://bugs.gentoo.org/show_bug.cgi?id=507664

Steps to reproduce:
emerge -a vmware-modules

[Comment 1 Harris Landgarten 2014-09-21 18:09:11 UTC]

you need the getname patch. I also suggest for use the vmci and vsock from the kernel.

These are the only patches you need if you use vmci and vsock from the kernel.

I am uploading them to this bug

[Comment 2 Harris Landgarten 2014-09-21 18:10:29 UTC]

Created attachment 385260 [details, diff]
279-getname patch

[Comment 3 Harris Landgarten 2014-09-21 18:11:08 UTC]

Created attachment 385262 [details, diff]
279-kernel-315 patch

[Comment 4 Harris Landgarten 2014-09-21 18:12:15 UTC]

Created attachment 385264 [details, diff]
inode_patch

[Comment 5 Harris Landgarten 2014-09-21 18:15:40 UTC]

note: if you are using systemd you have to change vmware.service to load and unload vmw_vmci.ko instead to vmci.ko

otherwise the vmware.service will not find the vmci module from the kernel.

[Comment 6 Shawn C 2014-09-22 09:10:25 UTC]

(In reply to Harris Landgarten from comment #1)
> you need the getname patch. I also suggest for use the vmci and vsock from
> the kernel.
> 
> These are the only patches you need if you use vmci and vsock from the
> kernel.
> 
> I am uploading them to this bug

Harry, what do u mean use vmci & vsock from the kernel? I compiled them as modules but i got errors while trying to install vmware-modules:
------------------------------------------------------------------
>>> Emerging (1 of 1) app-emulation/vmware-modules-279.1-r1
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.15.8-hardened/build
 * Found sources for kernel version:
 *     3.15.8-hardened
 * Checking for suitable kernel configuration options...
 *   CONFIG_VMWARE_VMCI:	 should not be set. But it is.
 *   CONFIG_VMWARE_VMCI_VSOCKETS:	 should not be set. But it is.
-----------------------------------------------------------------

Then I removed these two modules from kernel config and mv all patches to /etc/portage/patches/app-emulation/vmware-modules, but still got same errors..any ideas?

[Comment 7 Harris Landgarten 2014-09-30 16:38:09 UTC]

set:

CONFIG_VMWARE_VMCI_VSOCKETS=m
CONFIG_VMWARE_VMCI=m
CONFIG_VMWARE_PVSCSI=m

in your kernel config.

set:

app-emulation/vmware-modules -vmci -vsock

in you USE file

put the 3 patches I posted in /etc/portage/patches/app-emulation/vmware-modules/

and you should be good to go.

[Comment 8 Shawn C 2014-10-01 10:07:13 UTC]

(In reply to Harris Landgarten from comment #7)
> set:
> 
> CONFIG_VMWARE_VMCI_VSOCKETS=m
> CONFIG_VMWARE_VMCI=m
> CONFIG_VMWARE_PVSCSI=m
> 
> in your kernel config.
> 
> set:
> 
> app-emulation/vmware-modules -vmci -vsock
> 
> in you USE file
> 
> put the 3 patches I posted in
> /etc/portage/patches/app-emulation/vmware-modules/
> 
> and you should be good to go.
>
Harris, it works! Thanks very much!