Build guest vmware kernel modules: Difference between revisions
Jump to navigation
Jump to search
m (→The solution) |
|||
Line 47: | Line 47: | ||
====Troubleshooting==== | ====Troubleshooting==== | ||
===== available kernel modules ===== | |||
After the manual compile, you can run the lsmod command to see what modules it was able to load: | After the manual compile, you can run the lsmod command to see what modules it was able to load: | ||
$ lsmod | grep -i vm | $ lsmod | grep -i vm | ||
Line 72: | Line 74: | ||
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well. | * /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well. | ||
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon | * vmware-tools-thinprint - printing integration with the host using a virtual printing daemon | ||
===== unable to start services for VMware Tools ===== | |||
Creating a new initrd boot image for the kernel. | |||
NOTE: both /etc/vmware-tools/GuestProxyData/server/key.pem and | |||
/etc/vmware-tools/GuestProxyData/server/cert.pem already exist. | |||
They are not generated again. To regenerate them by force, | |||
use the "vmware-guestproxycerttool -g -f" command. | |||
initctl: Job failed to start | |||
Unable to start services for VMware Tools | |||
Execution aborted. | |||
If you get the above error then you can probably do as is sugggested above. I simply nuked the folder /etc/vmware-tools/GuestProxyData (rm -rf ) and completely reran the installer, after that it worked. | |||
===== vgauth what? ===== | |||
Nowadays VMware Tools asks if you want to enable the CAF agent (Common Agent Framework agent). | |||
If you are like me then you are probably wondering what this is. | |||
At the forums there's an answer ( https://communities.vmware.com/message/2604183#2604183 by VMware employee ykzang) | |||
I'm quoting that here for ease of reading. | |||
''Multiple VMware management solutions (e.g. vCM, Hyperic, Log Insight) require installation of in-guest agents.The Common Agent Framework attempts to provide a common framework to unify and simplify the management of various types of agents, and these agents would be referred to as Common Agent. | |||
Those VMware solutions are working on distinct administrative domains from the guest. VGAuth provides a way to authorize those solutions users' behaviors(install agent for example) within guest.'' | |||
====Alternative solution==== | ====Alternative solution==== |