On Sat, 2008-07-19 at 22:39 -0400, Kevin J. Cummings wrote: > Michael Eager wrote: > > Kevin J. Cummings wrote: > >> Mike Burger wrote: > >>>> Has anyone been able to get VMWare Server running on F9? > >>>> > >>>> I've installed VMWare Server from the rpm, run the config > >>>> script and everything seems to be installed correctly. > >>>> When I try to connect to the web management server, it > >>>> tells me that the server is not responding. <snip...> > > I had run the vmware-config program and started the server, but > > I decided to try restarting the server. It complained that I needed > > to run vmware-config again, so I did. It built all modules without > > error and started all of the VMware services. > > > > One thing which looks odd is that when the vmware-config script > > starts VMware Services, that the line "VMware Virtual Infrastructure > > Web Access" doesn't have either [OK] or [FAILED] after it. > > > >> After that (if it was successful), you should be able to connect to > >> the server. > > > > No such luck. Starting the browser and pointing to localhost: > > gives me a VI Web Access dialog (as before), but entering in > > the admin user/password results in a complaint that the server > > is not responding, and suggests that I check that the server is > > running and accepting connections. > > > > The following processes are running: > > vmnet-bridge > > vmware-authdlau > > vmware-watchdog > > vmware-hostd > Aha! There's a hint here (see below). > I don't see vmware-server in the above list. > This is what got built and started on my machine: > > > Starting VMware services: > > Virtual machine monitor [ OK ] > > Virtual ethernet [ OK ] > > Bridged networking on /dev/vmnet0 [ OK ] > > Host-only networking on /dev/vmnet1 (background) [ OK ] > > Bridged networking on /dev/vmnet2 [ OK ] > > Host-only networking on /dev/vmnet8 (background) [ OK ] > > NAT service on /dev/vmnet8 [ OK ] > > Starting VMware virtual machines... [ OK ] > > How does this compare with your build? ...And here's the other shoe dropping. You are each running different builds of VMware Server! > > > If I go to https://localhost:902, I get the following line: > > 220 Vmware Authentication Daemon Version 1.10; SSL Required, > > ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported > > Same as me, but it runs on a different port number on my machine. YMMV The difference you are seeing between the two is that one of you is running VMware Server version 1.0.6 while the other one is running the pre-release version of VMware Server 2.0 (currently at RC1 stage). VMware Server 1.0.6 works quite well under F9, but VMware Server 2.0 RC1 has many issues, including the ones the OP has noted. I'm not certain how to overcome these yet, but I know that there are several things that seem to conflict with regular F9 components. Apache is just for openers. Other things just plain don't work at all. I have yet to find a solution for getting 2.0RC1 going. Anyone given it a try and had success getting it to work yet? Cheers, Chris -- ================================================= "There is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things" --Niccolo Machiavelli -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
