On Sat, 19 Jul 2008 21:11:42 -0400
"Kevin J. Cummings" <cummings@kjchome.homeip.net> 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.
> >
> > Noting that I've not worked, yet, with VMWare, at all, I still
> > think the question needs to be asked:
> >
> > Did you start the VMWare server processes?
>
> An easier question (based on how VMWare is packaged) is did you run
> the vmware-config.pl script that comes with the RPM? It will
> shutdown any running services, and compile the necessary kernel
> modules for your running kernel (if you haven't made them already,
> and, no, just installing the RPM does not do this), and then start
> them up again.
>
> After that (if it was successful), you should be able to connect to
> the server.
>
> Good Luck!
>

Additionally - see this URL:

http://www.howtoforge.com/the-perfect-desktop-fedora9-gnome-p7

I'm not sure if the "patching" the Op does is need however - it's still
a nice guide to use.

--
Best regards,

Chris

() ascii ribbon campaign - against html e-mail
/ www.asciiribbon.org - against proprietary attachments

"There's no place like 127.0.0.1"

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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.


Noting that I've not worked, yet, with VMWare, at all, I still think the
question needs to be asked:

Did you start the VMWare server processes?


An easier question (based on how VMWare is packaged) is did you run the
vmware-config.pl script that comes with the RPM? It will shutdown any
running services, and compile the necessary kernel modules for your
running kernel (if you haven't made them already, and, no, just
installing the RPM does not do this), and then start them up again.


Thanks, all.

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

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

I'll try following Chris' pointer to HowToForge, but if any
of this looks hinky, please let me know.


--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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.


Noting that I've not worked, yet, with VMWare, at all, I still think the
question needs to be asked:

Did you start the VMWare server processes?


An easier question (based on how VMWare is packaged) is did you run
the vmware-config.pl script that comes with the RPM? It will shutdown
any running services, and compile the necessary kernel modules for
your running kernel (if you haven't made them already, and, no, just
installing the RPM does not do this), and then start them up again.


Thanks, all.

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


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?


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


I'll try following Chris' pointer to HowToForge, but if any
of this looks hinky, please let me know.


Not sure. Have you looked closely at the results of your config run?
Were there *any* errors at all? Warnings?


--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Christopher A. Williams wrote:

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?


Yes, I'm running 2.0. It seems I'm not alone.
Jeez, I hate the bleeding edge. :-)

I'll look into what happens when the startup script
tries to run Web Access, and why it doesn't say [OK]
or [FAILED]. Maybe there is a clue.


--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

David Timms wrote:

Michael Eager wrote:

Yes, I'm running 2.0. It seems I'm not alone.
Jeez, I hate the bleeding edge. :-)


As an aside, I've been succesfully running vmware-server-1.0.6 on F9
since release. I do this by installing and default booting the latest
2.6.24 kernel from F8. I haven't needed to manually patch files {just
use the vmware-any-any-update115 patch before vmware-config.pl


I find that strange. I had to find the update117 in order to get it
working on my F9 laptop (mostly, vmware-cmd still won't build). I guess
MMDV. B^)



DaveT.




--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

I did it with open vmware tools. It is much better than the any any.

On Sun, Jul 20, 2008 at 11:59 AM, Kevin J. Cummings <cummings@kjchome.homeip.net> wrote:

David Timms wrote:


Michael Eager wrote:


Yes, I'm running 2.0. * It seems I'm not alone.

Jeez, I hate the bleeding edge. *:-)




As an aside, I've been succesfully running vmware-server-1.0.6 on F9 since release. I do this by installing and default booting the latest 2.6.24 kernel from F8. I haven't needed to manually patch files {just use the vmware-any-any-update115 patch before vmware-config.pl





I find that strange. *I had to find the update117 in order to get it working on my F9 laptop (mostly, vmware-cmd still won't build). *I guess MMDV. *B^)




DaveT.








--

Kevin J. Cummings

kjchome@rcn.com

cummings@kjchome.homeip.net

cummings@kjc386.framingham.ma.us

Registered Linux User #1232 (http://counter.li.org)



--

fedora-list mailing list

fedora-list@redhat.com

To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Sat, 2008-07-19 at 23:49 -0700, Michael Eager wrote:
> Christopher A. Williams wrote:
> > 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?
>
> Yes, I'm running 2.0. It seems I'm not alone.
> Jeez, I hate the bleeding edge. :-)
>
> I'll look into what happens when the startup script
> tries to run Web Access, and why it doesn't say [OK]
> or [FAILED]. Maybe there is a clue.
>
>
> --
> Michael Eager eager@eagercon.com
> 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
>

I would check for a selinux violation in /var/log/audit/audit.log
and/or /var/log/messages. You can temporarily try
"setenforce 0" to test and then update the selinux policy afterwards.
I've seen this problem under CentOS 5.2 with Vmware server 2. I've also
seen other problems where the hostd and/or the webaccess process would
not run for other reasons.

Nataraj

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Sun July 20 2008, Alex Katebi wrote:
> I did it with open vmware tools. It is much better than the any any.
could you explain? if I simply run vmserver 1.06 which I just installed, it
returns the message telling me to run the installation file 'runme.pl' - if I
run that, it returns errors. If I run the any-any patch 117, which I just did,
it goes ahead with a complete build of the correct module for my running
kernel and returns a 'completed successfully' message. how are you doing this
with vmwaretools?

--
Claude Jones
Brunswick, MD, USA

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Michael Eager wrote:

Yes, I'm running 2.0. It seems I'm not alone.
Jeez, I hate the bleeding edge. :-)


As an aside, I've been succesfully running vmware-server-1.0.6 on F9
since release. I do this by installing and default booting the latest
2.6.24 kernel from F8. I haven't needed to manually patch files {just
use the vmware-any-any-update115 patch before vmware-config.pl


DaveT.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list