Trying to emerge app-emulation/open-vm-tools-kmod-2013.04.16.1098359 against sys-kernel/gentoo-sources-3.10.9 results in build errors. Full build log attached. Reproducible: Always
Created attachment 356944 [details] Build log
Yeah, I spent some time trying to make it work with 3.10.9 yesterday. Everything except the vmxnet driver fails for me for one reason or another. If you have a patch, I'll check it out, but I was really just going to wait for upstream to do another release at this point.
I'll give patching a shot. In the meanwhile, perhaps it might be prudent to add a blocker for kernel version >=3.10.9 ? Actually I'm not even sure if this is the first kernel version to exhibit this issue, on my VM I upgraded straight from 3.9.x to 3.10.9. I can do some testing to figure out where the breakage started.
*** Bug 482586 has been marked as a duplicate of this bug. ***
I can confirm that 3.10.0 is affected too.
Same Problem here with hardened-sources which are now 3.10.1-r1 stable for AMD64. I spent some time with google and found on this page a complete patchset to get open-vm-tools-kmod working with 3.10 kernel. I extracted the relevant parts and created two patches for my own ebuild to test if it works - yes it does. Attached find the 2 patches for adding this to the current ebuild. You also have to include the patches in the ebuild file: Here is the complete epatch part from the ebuild: epatch "${FILESDIR}/frozen.patch" epatch "${FILESDIR}/putname.patch" epatch "${FILESDIR}/1098359-vmblock-3.10.0.patch" epatch "${FILESDIR}/1098359-vmhgfs-3.10.0.patch" epatch "${FILESDIR}/1098359-vmsync-3.10.0.patch" epatch_user
Created attachment 358364 [details, diff] patch for vmhgfs
Created attachment 358366 [details, diff] patch for vmsync
(In reply to Andreas Fragner from comment #6) Where did these patches come from?
It would also be great to follow the upstream packages and disable VMCI and VMSOCK for kernels >= 3.9 see http://sourceforge.net/p/open-vm-tools/mailman/open-vm-tools-announce/?viewmonth=201304
With the patches provided by Andreas, I could compile open-vm-tools-kmod on 3.10.10-hardened. However, loading vmhgfs.ko emits: vmhgfs: Unknown symbol VMCIDatagram_Send (err 0) vmhgfs: Unknown symbol VMCIDatagram_DestroyHnd (err 0) vmhgfs: Unknown symbol VMCIDatagram_CreateHnd (err 0) vmblock and vmsync seems to modprobe ok. As noted by Daniel, vmci and vsock should be removed from the list, because it's already in the kernel.
Just wanted to add some things here I wanted to get this building on 3.11 here is a working ebuild and the needed 3.11 vmblock patch
Created attachment 359200 [details] open-vm-tools-kmod-2013.04.16.1098359.ebuild
Created attachment 359202 [details, diff] vmblock.3.11 patch
hgfs simply doesn't work on 3.11 so it is simply disabled in the ebuild
Upstream has released a new snapshot version 2013.09.16, but it doesn't seem to have fixed these compile issues, so the patches are still needed. I've gone ahead and created an ebuild for the new version that incorporates these patches as well as disables building vmhgfs on 3.10+ and vmci/vsock for 3.9+. According to upstream's mailing list, they want to deprecate vmblock as of Linux-3.0 in favor of their vmblock-fuse implementation, which is included with open-vm-tools[fuse]. Can we go ahead and remove vmblock (and required patches) from this package in favor of that?
Created attachment 361258 [details] New ebuild
Created attachment 361260 [details] open-vm-tools-kmod-2013.09.16.1328054.ebuild Correct filename this time... user error :(
The ebuild has a note regarding vmhgfs: # vmhgfs does not build with Linux 3.10+ Which kernel have you tried with? You can remove vmxnet in versions >=2.6.32 and vmblock & vmsync in versions >=3.0.
I want to test this out in my local overlay, but I'm a little confused. Where does the freeze patch come from?
(In reply to Tomas Mozes from comment #19) > The ebuild has a note regarding vmhgfs: > # vmhgfs does not build with Linux 3.10+ > > Which kernel have you tried with? > > You can remove vmxnet in versions >=2.6.32 and vmblock & vmsync in versions > >=3.0. According to https://bugs.gentoo.org/show_bug.cgi?id=487484#c9, what I've written regarding vmxnet isn't true, sorry.
The original issue reported should be fixed by the latest version bump. Please file new bugs for any issues with 2013.09.16.1328054.