installing VMwareTools-8.6.0-515842.tar.gz on gentoo

Majed17 · 05-10-2012, 05:08 AM

well what can i say

? thank you very much

it finally worked.. it required a lot of patience but it worked

the

Code:

<*>       Intel PATA old PIIX support

was blank so i included it but i don't think it mattered..
however pcnet32 was modular and was not included in the modules file, so i just put a star (*) instead of the (M) infront of it and followed the manual configuration of the kernel and the system booted flawlessly it just said that it failed to do something and fell to automatic detection of something but otherwise the system works fine.

after that i tried installing vmware tools..and voila it also got installed

first i did:

Code:

ln -s /usr/src/linux/include/generated/utsrelease.h /usr/src/linux/include/linux/utsrelease.h
ln -s /usr/src/linux/include/generated/autoconf.h /usr/src/linux/include/linux/autoconf.h

and both links got created except i was unabled to see where they were created..
then it detected by itself where gcc was and the kernel image headers..and everything else, however finally it finished with the following message:

Code:

srvmon-esx vmware-tools-distrib # /etc/init.d/vmware-tools start
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Paravirtual SCSI module:                                           failed
   Guest memory manager:                                              failed
   VM communication interface:                                        failed
   VM communication interface socket family:                          failed
   File system sync driver:                                            done
   Guest operating system daemon:                                      done

4 of the operations failed.
next i added vmware to runlevel default

Code:

rc-update add vmware-tools default

after reboot, however, vmware did not start automatically for some reason and when i started it manually
i got:

Code:

srvmon-esx ~ # /etc/init.d/vmware-tools start
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Paravirtual SCSI module:                                           failed
   Guest memory manager:                                              failed
   VM communication interface:                                        failed
   VM communication interface socket family:                          failed
   File system sync driver:                                            done
   Guest operating system daemon:                                      done

but i didn't understand what has failed and why didn't it start by itself after boot, any ideas? and thank you again for your help

i92guboj · 05-10-2012, 07:26 AM

These failures might have something to do with kernel modules that, either, do not exist, or failed to load. Maybe "dmesg" in the VM can help you determine that.

I have no idea about vmware at all, but you can always look around in the kernel, and see if there's some related option (I doubt it), or, you can try installing app-emulation/vmware-modules if you haven't yet. Maybe these modules are there. Google might help you better with this than I.

In any case, I am happy that we were able to solve this, at least in part

Majed17 · 05-14-2012, 03:40 AM

well

Code:

dmesg

turned up an error that existed before upgrading the kernel. it started when i installed VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz and try to run a perl script which uses this sdk and i used to get "segmentation fault"
so i was surprised to see the same fault shown in the output of dmesg:
http://www.fileupyours.com/files/324524/dmesg
can you make anything of it that might help me solve this old segfault problem? or should i make a new thread about that because googling about it didn't help much. hope you are doing fine in the tough economic times and the demonstrations where you are at

i92guboj · 05-15-2012, 04:18 AM

Quote:

Originally Posted by Majed17

well

Code:

dmesg

turned up an error that existed before upgrading the kernel. it started when i installed VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz and try to run a perl script which uses this sdk and i used to get "segmentation fault"
so i was surprised to see the same fault shown in the output of dmesg:
http://www.fileupyours.com/files/324524/dmesg
can you make anything of it that might help me solve this old segfault problem? or should i make a new thread about that because googling about it didn't help much. hope you are doing fine in the tough economic times and the demonstrations where you are at

I can't hep with that segfault. It could be some incompatibility with the concrete kernel version you are using, or some other more obscure issue (or just a bug). I suggest you checking whatever mailing list is relevant for that driver. I can't direct you to any place because I have no experience with it, or with vmware at all.