Problem is described at http://www.vmware.com/community/thread.jspa?threadID=9613&messageID=85419. The fix described there: ----------------------------------------------------------------------- unpack /opt/vmware/lib/modules/source/vmmon.tar, and in vmmon-only/include/pgtbl.h you want to replace pgd_offset(mm, addr) with pml4_pgd_offset(pml4_offset(mm, addr), addr) and then recreate vmmon.tar and try again. -------------------------------------------- Fixes that problem, but only when the advice is similarly applied to the vmnet.tar file as well. The next issue is a series of dmesg errors, as follows: vmnet: Unknown symbol class_simple_device_add vmnet: Unknown symbol class_simple_destroy vmnet: Unknown symbol class_simple_device_remove vmnet: Unknown symbol class_simple_create vmnet: Unknown symbol class_simple_device_add vmnet: Unknown symbol class_simple_destroy vmnet: Unknown symbol class_simple_device_remove vmnet: Unknown symbol class_simple_create This is related to some licensing issues that are articulated in kernel message traffic, nicely presented at: http://www.gossamer-threads.com/lists/linux/kernel/486286 Now, I was able to hack around the issue by implementing a global s/EXPORT_SYMBOL_GPL/EXPORT_SYMBOL in the kernel file: drivers/base/class_simple.c , then a recompile of the kernel. This is, at least according to the kernel traffic above, supposed to be fixed in some upcoming version of mm-sources, so it may be self fixing. Reproducible: Always Steps to Reproduce:
Dang. Forgot to mention: mm-sources-2.6.10-rc2-mm2 app-emulation/vmware-workstation-4.5.2.8848-r2 The hacks described above seem to have resolved the issues, at least for now.
Both of these issues appear to be absent in the new vmware-5 beta. I would assign this as an upstream bug, apparently in the process of being fixed.
If you're on mm-sources, you're a glutten for punishment anyway, so feel free to use 5.0 beta. Just unmask it using /etc/portage/package.unmask.
I agree with aja and jhuebel. We really can't support mm-sources for vmware simply because mm-sources is the kernel team playground where they intentionally break stuff all the time to test out new ideas.
VMware 5 is in portage now
