For some reason current ebuild are more picky about my kernel .config and are not happy with me having VMCI available as modules: >>> Emerging (5 of 5) app-emulation/vmware-modules-279.2 * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 3.10.12-default-pciehp * 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. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * Once you have satisfied these options, please try merging * this package again. * ERROR: app-emulation/vmware-modules-279.2::gentoo failed (setup phase): * Incorrect kernel configuration options * * Call stack: * ebuild.sh, line 93: Called pkg_setup * vmware-modules-279.2.ebuild, line 45: Called linux-info_pkg_setup * linux-info.eclass, line 914: Called check_extra_config * linux-info.eclass, line 808: Called die * The specific snippet of code: * die "Incorrect kernel configuration options" * * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.2::gentoo'`, # grep VMCI /usr/src/linux/.config CONFIG_VMWARE_VMCI_VSOCKETS=m CONFIG_VMWARE_VMCI=m # BTW, I do have vmware already installed, I jsut cannot upgrade: :( # emerge -pv app-emulation/vmware-modules ... Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-279.2 [279.1] USE="vmci%* vsock%* -pax_kernel" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB
Looks like those modules are now supplied by vmware-modules, you can't have them enabled at all in your kernel config (even as modules) because they will collide.
Hi, first of all, I don't agree that 279.1 uses official kernel modules while 279.2 silently uses it's own drivers. Of course I rather stay with official drivers. 279.1 runs fine with 3.10.12 kernel. Second, I disabled the two modules and tried to compile against linux-3.10.46, no luck. I understand it is an effort for you but I would be happy if emerge did a kernel version check for me and told me that 3.10.46 is not supported anyway. And did it somewhere soon like in src_prepare() before even trying to compile the thing and before complaining to me that I have enabled the VMWARE kernel modules. Finally to say, I do not know what are IUSE vmci and vsock useful for? Again, einfo() should have told me. Thanks, Martin So, I stay at 3.10.12, the last one that worked.
(In reply to Martin Mokrejš from comment #0) Martin, the selection between the linux kernel tree modules and ones provided by vmware-modules package is done with the vmsock and vmci USE flags. (Set "-vmci -vmsock" to use the in-kernel modules).
(In reply to Alexander Bezrukov from comment #3) > (In reply to Martin Mokrejš from comment #0) > > Martin, the selection between the linux kernel tree modules and ones > provided by vmware-modules package is done with the vmsock and vmci USE > flags. (Set "-vmci -vmsock" to use the in-kernel modules). This is the correct solution. Closing.
