VMware Communities
DGBrennan
Contributor
Contributor
‎08-22-2009 10:59 AM
Jump to solution

Fedora 11 and Workstation 6.5.2 now working but new 6.5.3 install fails

Having got Workstation 6.5.2 working on Fedora 11 by using the "patch". I expected that the new download of 6.5.3 would install without problems.

It didn't!

It hangs in "Configuring" Player

Installing VMware Installer 1.0

Copying files...

Configuring...

Installing VMware Player 2.5.3

Copying files...

Configuring...

Installing VMware VIX API 1.6.3

Copying files...

Configuring...

Installing VMware Player 2.5.3

Copying files...

Configuring...

Installing VMware Player 2.5.3

Copying files...

Configuring...

Typing in ^C just rolls back the install.

Has anybody got past this yet?

Reply
0 Kudos
50 Replies
lagriffe
Contributor
Contributor
‎08-29-2009 08:47 AM
Jump to solution

BTW, I'm running Archlinux, so this will work on other distros, as long as you know where the VMware init scripts are located (/etc/rc.d/vmware.d in the case of Archlinux).

Reply
0 Kudos
VMwareRoot
Contributor
Contributor
‎08-30-2009 11:25 AM
Jump to solution

-

INSTALLING VMWARE 6.5.3 on FC 11(Fedora 11) -

To install you don't need to kill !!!

Just wait it freezes on 62%, go to another bash terminal window and move the file /etc/wmare/database to database_old for example:

mv /etc/vmware/database /etc/vmware/database_old

and then the installation will unlock, continue and when it finishes you bring back the file

mv /etc/vmware/database_old /etc/vmware/database

-

DONE -

Reply
0 Kudos
radikaled
Contributor
Contributor
‎08-31-2009 02:32 AM
Jump to solution

After reading the previous posts and seeing VMware Root's post. I have to say it seems like it all comes down to timing.

I have tried all the previous methods mentioned but it always seemed like something was missing. Apparently once the installer freezes on 62% you have to immediately move /etc/vmware/database. Key word being immediately. I had another terminal window open with a mv command ready to go right when the installer hit 62%. :smileylaugh:

Reply
0 Kudos
krazyz28
Contributor
Contributor
‎08-31-2009 06:24 PM
Jump to solution

The above post worked for me. I had to time the move from another console window before it would finish the installation.

mv /etc/vmware/database /etc/vmware/database_old

Move it back after the installation finishes

mv /etc/vmware/database_old /etc/vmware/database

Then run

vmware-modconfig --console --install-all

Everything works. :smileycool: :smileycool: :smileycool:

Reply
whitneyp
Contributor
Contributor
‎09-01-2009 11:21 AM
Jump to solution

Indeed this worked for me. Just to be safe, I ran the modconfig install all command listed in this thread. But I still wonder about the stability and completeness of the install.

Paul M. Whitney

Paul M. Whitney
Reply
0 Kudos
DGBrennan
Contributor
Contributor
‎09-01-2009 12:20 PM
Jump to solution

This has become a useful thread and it looks like there are a number of ways to slice and dice this install. I assume the many Fedora users will have to try every option outlined above to get 6.5.3 to install. When you do you will not have to worry about it until 6.5.4.

The problem we all face is VMWARE's "we don't support Fedora" is going to leave us all in the dark as to why the install really fails.

This thread has become a great advert for VirtualBox which I trully didn't know existed until I started it, as VirtualBox does support Fedora and if I was not an owner of a VMWARE Workstation license I would not waste so much time trying to get VMWORKSTATION working.

But here is my review:-

  • The installer is designed to impart lots of eye candy to the user and hide lots of warnings as the product is compiled. When it breaks it hangs. That is not what an installer should do.

  • When I developed products the idea that when you compiled a module you generated a 100 odd compiler warnings would have had me sent back to my desk.

  • Clearly Fedora and pulseaudio has still is not support in 6.5.3 so sound is a thing of the past.

  • The hanging of your VM on shutdown with "Unexpected signal 11" is something we all have to live with.

I can only assume that in the Ivory tower that is VMWARE development they don't know how to spell Fedora and if they do they are not allowed to tell us how to fix it.

Reply
0 Kudos
radikaled
Contributor
Contributor
‎09-01-2009 01:28 PM
Jump to solution

Here here! I've been using VirtualBox since v1.6 and I have to say for a free product it is very refined (getting better all the time) and in terms of features rivals that of VMware Workstation. Unless you are doing some fancy virtual networking you won't even miss VMware Workstation (or even VMware Fusion for that matter). So I encourage everyone getting the shaft to try out VirtualBox. On another note please make a Virtual Infrastructure Client for Linux already!

Reply
0 Kudos
natan770
Contributor
Contributor
‎09-02-2009 02:42 AM
Jump to solution

Hi there,

I'm awfully sorry, have followed these indications, which brought no result. Still freezing. It's not too good, sorry.

Reply
0 Kudos
whitneyp
Contributor
Contributor
‎09-02-2009 05:15 AM
Jump to solution

In all due fairness to VMware, we are lucky they even provide anything at all for the Fedora/Ubuntu line of products. Fedora after all is just a cooking pot for Red Hat. If you want "true" supportability, perhaps switching to an official Red Hat distribution, or CentOS, or some other commercial Linux distribution will alleviate the frustration.



I only say this because I just upgraded to Fedora 11, and already Fedora 12 is released in alpha stage. I am just getting comfortable with Fedora 11 and 12 is already around the corner? I think it is unreasonable to expect a commercial company to support these moving targets/hobbyist/cooking pot distributions. Do you see any of the competition doing it? No. For the most part they are sticking to "official" releases only.

VMware in my opinion does not consider Fedora a priority. When they can, they will get to it. But they have bigger fish to fry. I struggle with the ad-hoc workarounds to get the product working, but at least we can still use it without having to pay for a subscription to "officially released" distributions.






Paul M. Whitney

p.s. I second the motion for Virtual Infrastructure Client for Linux.

Paul M. Whitney
Reply
0 Kudos
natan770
Contributor
Contributor
‎09-02-2009 05:44 AM
Jump to solution

I dont want to hear about fedora, ubuntu, redhat or whatever. We are LINUX USERS, and need a LINUX version of vmware.

Anyway, I've just switched to VBox. At least, the job is done.

Reply
0 Kudos
mjs
Contributor
Contributor
‎09-02-2009 08:17 AM
Jump to solution

I don't think the timing is all that critical, at least on the early side. I installed the RPM. When the RPM installation ends, the VMware installer starts. When you are prompted to accept the EULA, /etc/vmware/database already exists. You can move it at that point, then accept the EULA, and everything proceeds normally. When the VMware installer completes, move the database file back. Everything seems to work after that.

Reply
0 Kudos
VMwareRoot
Contributor
Contributor
‎09-02-2009 10:19 AM
Jump to solution

Yes it's gonna work there too...

I am guessing that you didn't wait so much AFTER changed the file name as i said...

You must wait some seconds AFTER you changed the file name and it will unlock. For me it was about 20 seconds.

I don't know what you are running there so wait 5 min LOL, it will unlock.

Keep in mind that the problem relies on that file. After you change the name, it WILL unlock.

See u!

Reply
0 Kudos
Mulchman
Contributor
Contributor
‎09-02-2009 10:23 AM
Jump to solution

As VMwareRoot mentions, I ended up waiting about 3 minutes after it hit 62% - and I moved the database file to database_old in another terminal - until it completed "successfully".

Reply
0 Kudos
mjs
Contributor
Contributor
‎09-02-2009 10:58 AM
Jump to solution

Yes, it did take a little while to complete after the move, but it did complete and is working fine. (This is Fedora 11.)

I just wanted to point out that there's a convenient pause where the move can be made without worrying about missing the "magic moment" and having to reboot, clean up, and try again (as some reported they needed to do).

Reply
0 Kudos
DGBrennan
Contributor
Contributor
‎09-02-2009 04:11 PM
Jump to solution

VMWARE is stable on Redhat 5 our production systems.

Working with Redhat on new capabilities its clear that they use Fedora very much as there Beta program.

I also know that most devlopment staff who run RHEL5 are also using Fedora as a development platform.

In my view VMWARE ignore Fedora at their peril.

While I can live with 6.5.2 needing a patch to run, I am shocked that nobody in VMWARE tried to install 6.5.3 on Fedora 11.

Clearly if developers suddenly can't run VMWARE on their Fedora development systems it will not be long before they turn to something like Virtualbox, and the end result will be that it will find its way into our RHEL 5 production systems.

Maybe VMWARE consider they do have bigger fish to fry, but ask Redhat the question "how to ensure that we can track the future of your operating system" and they will answer "Fedora".

Reply
0 Kudos
Mulchman
Contributor
Contributor
‎09-02-2009 04:19 PM
Jump to solution

Now that most of us are getting 6.5.3 to install on Fedora 11, does anyone have advice for 'fixing' the "VMware Workstation hangs when shutting down a WinXP guest" issue? Some searches indicate this was a problem with 6.5.2 and Fedora 11 and one user posts that disabling USB in Workstation fixed the hang for him (it doesn't for me).

Reply
0 Kudos
Rastlinux
Contributor
Contributor
‎09-02-2009 04:37 PM
Jump to solution

Actually, mine still hangs as well and I do not use the usb either. I'd really like my sound back. This is how I watch NetFlix on Linux is through VMware... So they are messing with my leisure time as well as my work time Smiley Wink

I tried Virtual Box and sound works great and is starts and shuts down great. I just could not figure out the network part. I uninstalled VirtualBox as part of my attempt to get 6.5.2 to 6.5.3 upgrade to work.

Reply
0 Kudos
psyk
Contributor
Contributor
‎09-03-2009 04:45 AM
Jump to solution

For those having issues with shutdown of Virtual Machine guests try disabling or turning off the 'pcscd' service.

# service pcscd stop
# chkconfig --level 345 pcscd off
# chkconfig --list

If you need smart-cards etc. in your VM then this won't work for you... Smiley Sad

This worked for me, so your mileage might vary...

Reply
0 Kudos
Mulchman
Contributor
Contributor
‎09-03-2009 08:42 AM
Jump to solution 

For those having issues with shutdown of Virtual Machine guests try disabling or turning off the 'pcscd' service.
bq. 	# service pcscd stop 
		 # chkconfig --level 345 pcscd off 
		 # chkconfig --list
If you need smart-cards etc. in your VM then this won't work for you...  Smiley Sad
This worked for me, so your mileage might vary...
 
Weird; this worked for me as well. I stopped the pcscd service through (in Gnome) "System > Administration > Services" then attempted to shutdown my WinXP guest and everything went fine with no hang.

					
				
			
			
				
			
			
			
			
			
			
			
		

		
		
	

	
	


	
				
		
			
		
			
		
			
					
			
		
				
		
			
					
		
	
				
		
			
					
		
	
				
		
			
					
		
	
				
		
			
					
		
	
				
		
			
					
		
	
				
		
	
	


		

	

		

			

	
		
			
					
				
		
			
		
			
					
		
		Reply
	
				
		
			
					
				
		
			
					

	
			

				
		
			
		
			
				

					
						
	
			0
		

	Kudos

					
				

			
			
		

	
		
    	
		

			
				
					
				
				
			
		

	
    
			

		

	

	

	

    

	

	


				
		
	
	


		

	

		

			
		

			

	
		
			
					
				
		
	
	


		

	

		

			

	
		
			
					
				
		
			
					
				
		
	
	


		

			

	
		
			
					
		
	
				
		
			
					
		
	
				
		
	
	


		

	



		

	

	

	




			
		
    
            

                

            

        

	
		

		
	

	

	



	
                

                
				
            
                
                    
        

	
	

		
	

	


		
	
		

			

	 
	 
	
	

	

	

	
		

			

			
	

	

		


	

	
		

			
			

	

		

			

	
		
			
					

	
			
					hydetech
					
				
		


				
		
	
	

	
		

			
		
			
	

	
			
				
		Enthusiast
		
			
		
		
		
		
		
		
		
		
	
			
		

		
			
					
		

			Enthusiast
		

	
				
		
	
		

	
	

	
		
			
					
		

			
    

	
		
		
		‎09-03-2009
	
		
		08:51 AM
	
	

	
	
	
	
	
	
	
	
	
	
	
	

		

	
				
		
			
			
				
			Jump to solution
		
			
		
		
	
	


		

			

	
		
			
		
	
	


		

	

		

			
		

	

		

			

	
		

			
		
			

		


	

	
			

	
	
	 
	
	
	
				
		

			
				
					
					
				
			
		

	
			
	
	
	
	
	


		

	

	

	

	

	

	

	
			
					
				
		

	


	

		
	
		

	
	


		

	

		

			

	
		
			
					
		
	
				
		
			
					
		

	
		

			
				
					
					
						
Yeah, it works even USB controller enabled. Thanks. :smileygrin:

					
				
			
			
				
			
			
			
			
			
			
			
		

		
		
	

	
	


	
				
		
			
		
			
		
			
					
			
		
				
		
			
					
		
	
				
		
			
					
		
	
				
		
			
					
		
	
				
		
			
					
		
	
				
		
			
					
		
	
				
		
	
	


		

	

		

			

	
		
			
					
				
		
			
		
			
					
		
		Reply
	
				
		
			
					
				
		
			
					

	
			

				
		
			
		
			
				

					
						
	
			0
		

	Kudos