Confirming that I'm having the same issue...
I have been experiencing the same situation on Fedora11/i386 on ThinkPad X61s(Cere 2 Duo).
And I can't resolve the issue not yet.
A significant point is that as/cc1/gcc processes are locked up with "pipe_w" state while compiling some modules.
Same situation with the kernel version 184.108.40.206-217.2.8.fc11.x86_64. :_|
Should we change to Virtualbox which has better support?
Fedora 11, 32 bit, latests patches and kernel version available. Same problem, exactly as described. Was really hoping that this realese would address some of the issues I was seeing in 6.5.2 under fedora 11 (I do understand this is not an officially supported linux distro).
I also fail to understand why this is "unsupported" as a major user of Redhat 5 Enterprise I asked redhat what their Beta strategy is. They say that Fedora is their Beta strategy so we run Fedora to understand which products are going to crash an burn a Redhat 6 Enterprise. Looks like Vmware Workstation is on the list.
Same issue on Ubuntu Karmic And I am evaluating it ;(
The same thing like 6.5.2 installation process - very stressful. It seems there's a problem write or read on the vmware config database (/etc/vmware/database). Under the origin FC11 install, the vmware installation is successfully. I think, you have an updated FC11 System, you have that problem. During the installation process you show the /var/log/vmware-installer file. Before the message
Using UI type gtk
Opening database file /etc/vmware/database
and the install hang up, you move the /etc/vmware/database. Then the install finished and you bring back vmware database file.
That worked for me But why ? VMware fix it
I saw the same problem installing Player 6.5.3 on Fedora 11 but got around it by killing the terminal running the install after it hangs and then running the command 'vmware-modconfig --console --install-all' afterwards. On a more positive note the 6.5.3 release compiles ok with the 2.6.29 kernel in Fedora 11 albeit with a slew of warnings.
Westlaus - thanks much! The workaround was successful. I agree very stressful. Now we'll see if this release is more compatible with Fedora 11.
I couldn't quite follow this. What are the steps to get 6.5.3 to install on an updated Fedora 11 Kernel?
I tried the instuctions to quit the terminal window and run vmware-modconfig--console --install-all, but I only got the vmplayer, and am missing vmware. If I press CTRL-C, the installer removes all of the files after it hangs. I don't understand at what point to type gtk. With the rpm install, that doesn't seem to be an option, or I just don't get it. (Don't get what is meant by opening database? How? With what?
OK I have now got this working.
I downloaded the bundle and ran this:-
./VMware-Workstation-6.5.3-185404.x86_64.bundle --console --required
When it hung I killed -9 the process:-
This is important as it ensures the bundle install continues and installs Workstation.
The bundle will then report that it is installed.
vmware-modconfig --console --install-all
Thanks for all your help guys
westlaus, im trying this procedure and I get an error when it tries to compile the kernel modules. The prompt comes up as "The component vmware-player does not exist".
The "/tmp/vmware-root/setup-21298.log" shows:
Aug 25 21:27:48.219: app| Failed to install the module /tmp/vmware-root/modules/vmmon.o to /lib/modules/220.127.116.11-217.2.3.fc11.x86_64/misc/vmmon.o.
Aug 25 21:29:08.036: app| Extracting the sources of the vmmon module.
Aug 25 21:29:08.047: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2
.6.29.6-217.2.3.fc11.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.1
Aug 25 21:29:08.927: app| The vmmon module loads perfectly in the running kernel.
Aug 25 21:29:08.927: app|
Aug 25 21:29:08.937: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/18.104.22.168-217.2.3.fc11
I get a little farther than that but I still get stuck
Aug 25 14:41:25.156: app| The vmmon module loads perfectly in the running kernel.
Aug 25 14:41:25.156: app|
Aug 25 14:41:25.165: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/22.214.171.124-217.2.8.fc11.x86_64/misc/vmmon.o
Aug 25 14:41:25.314: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/126.96.36.199-217.2.8.fc11.x86_64/misc/vmmon.ko
Aug 25 14:41:34.859: app| Extracting the sources of the vmnet module.
Aug 25 14:41:34.867: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmnet-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/188.8.131.52-217.2.8.fc11.x86_64/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.4.