Bug 506584 – app-emulation/vmware-modules-271.1 with kernel 3.14 - .../work/vmblock-only/linux/inode.c:138:32: error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’

• Status: RESOLVED DUPLICATE of bug 462666
• Product: Gentoo Linux

[Description Harris Landgarten 2014-04-02 17:06:53 UTC]

Getting vmware-workstation working with 3.14 kernel requires some changes:

1. vsock.ko and vmci modules are now in the kernel tree and have to be removed from the ebuild and from patches that reference vsock_only or vmci_only.

2. vmci.ko is now vmw_vmci.ko and need to be fixed in systemd services as well as udev rules in the ebuild

3. vmnet and vmmon both build and install with kernel based vsock and vmci but I have not been able to build vmblock.

I am currently running without vmblock which is not effecting me.

[Comment 1 Jeroen Roovers (RETIRED) 2014-04-03 15:31:11 UTC]

1) Please post your `emerge --info' output in a comment.
2) Please attach the entire build log to this bug report.

[Comment 2 Harris Landgarten 2014-04-03 16:26:33 UTC]

Created attachment 374168 [details]
build log

show failure of vmblock to build

[Comment 3 Harris Landgarten 2014-04-03 16:28:27 UTC]

Created attachment 374170 [details]
modified ebuild

ebuild modified for vmci and vsock from kernel and vmci renamed to vmw_vmci

[Comment 4 Harris Landgarten 2014-04-03 16:29:10 UTC]

I also commented out all the vmci_only and vsock_only parts of 279 patches

[Comment 5 Harris Landgarten 2014-04-03 16:30:31 UTC]

also still using all the user patches I posted to get kernel-3.13 to work

[Comment 6 Sven 2014-04-04 12:11:03 UTC]

Do you mean 279.1 instead of 271.1?

[Comment 7 Jeroen Roovers (RETIRED) 2014-04-04 15:58:42 UTC]

Comment on attachment 374170 [details]
modified ebuild

--- vmware-modules-279.1.ebuild 2013-11-24 17:40:13.625689177 +0100
+++ -   2014-04-04 17:58:30.536451777 +0200
@@ -38,7 +38,7 @@
 
        VMWARE_GROUP=${VMWARE_GROUP:-vmware}
 
-       VMWARE_MODULE_LIST="vmblock vmci vmmon vmnet vsock"
+       VMWARE_MODULE_LIST="vmblock vmmon vmnet"
        VMWARE_MOD_DIR="${PN}-${PVR}"
 
        BUILD_TARGETS="auto-build KERNEL_DIR=${KERNEL_DIR} KBUILD_OUTPUT=${KV_OUT_DIR}"
@@ -75,7 +75,7 @@
        linux-mod_src_install
        local udevrules="${T}/60-vmware.rules"
        cat > "${udevrules}" <<-EOF
-               KERNEL=="vmci",  GROUP="vmware", MODE=660
+               KERNEL=="vmw_vmci",  GROUP="vmware", MODE=660
                KERNEL=="vmmon", GROUP="vmware", MODE=660
                KERNEL=="vsock", GROUP="vmware", MODE=660
        EOF

[Comment 8 Sven 2014-04-13 15:39:50 UTC]

This seems to be fixed by the new 279.1-r1 ebuild. Simply disable vmci and vsock use flags.

[Comment 9 Harris Landgarten 2014-04-13 16:45:23 UTC]

the new version is still dying on vblock_only with the same error I posted. Must still need a patch.

Also the requirement for VMCI_VSOCKETS = y or m in .config is unnecessary for using gentoo as a host. It is only needed for linux as a guest.

[Comment 10 Harris Landgarten 2014-04-13 18:33:50 UTC]

From my research, it is very possible the vmblock_only error is being caused by gcc-4.8 considering as an error what was a warning in gcc-4.7

Unfortunately we cannot compile a module with 4.7 and use with a kernel compiled by 4.8

[Comment 11 Sven 2014-04-13 21:04:19 UTC]

I'm using gcc 4.7 and I did not have problems in building vmblock.

[Comment 12 Harris Landgarten 2014-04-13 23:00:26 UTC]

should we continue this bug as gcc-4.8 only or start a new bug?

[Comment 13 Harris Landgarten 2014-04-19 18:08:55 UTC]

Created attachment 375322 [details, diff]
patch in inode.c

I cannot get vmblock to build without this patch. It will still not modprobe with getname error but at least vmware-modules builds and installs. I don't think vmblock is used anymore anyway.

[Comment 14 Jeroen Roovers (RETIRED) 2014-04-26 16:14:29 UTC]

*** This bug has been marked as a duplicate of bug 462666 ***