http://open-vm-tools.sourceforge.net/

Install the vmware tools first. Then go to the above web site and download & install the open-vm-tools. Let me know if you have any peoblems. I have installed two Fedora 9 vmware tools this way. Forget the any any stuff you don't need that.



On Sun, Jul 20, 2008 at 3:00 PM, Claude Jones <cjones@levitjames.com> wrote:

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



--
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:
> http://open-vm-tools.sourceforge.net/
>
> Install the vmware tools first. Then go to the above web site and download
> & install the open-vm-tools. Let me know if you have any peoblems. I have
> installed two Fedora 9 vmware tools this way. Forget the any any stuff you
> don't need that.

I found that website, but, it wasn't so self-evident. How does one 'install
the vmware tools first' as you state? I normally open a vm after I've got
vmware server running, and it boots up and gives me a message about needing to
install or update vmware tools, and that's when I install vmware tools. How
are you doing that first - or better, I should ask, what do you mean by first?
First before what? Before installing the vmware package?

Are you simply installing the open-vm-tools from the tarball?

What advantage are you gaining by doing things that way? My vm's run just fine
the way I'm doing it now - what improvement should I expect by learning the
method you suggest?

--
Claude Jones
Brunswick, MD, USA

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

On Mon, Jul 21, 2008 at 12:36 AM, Claude Jones <cjones@levitjames.com> wrote:

On Sun July 20 2008, Alex Katebi wrote:

> http://open-vm-tools.sourceforge.net/

>

> Install the vmware tools first. Then go to the above web site and download

> & install the open-vm-tools. Let me know if you have any peoblems. I have

> installed two Fedora 9 vmware tools this way. Forget the any any stuff you

> don't need that.



I found that website, but, it wasn't so self-evident. How does one 'install

the vmware tools first' as you state? I normally open a vm after I've got

vmware server running, and it boots up and gives me a message about needing to

install or update vmware tools, and that's when I install vmware tools. How

are you doing that first - or better, I should ask, what do you mean by first?

First before what? Before installing the vmware package?


Before booting your guest Fedora make sure that your vmware cd drive is not pointing to an iso image. After booting install the vmeare tools as you said. Then untar & unzip the vmeare tools.*

*

Are you simply installing the open-vm-tools from the tarball?yes





What advantage are you gaining by doing things that way? My vm's run just fine

the way I'm doing it now - what improvement should I expect by learning the

method you suggest?


I thought that you were encountering errors by running the vmware tools alone.
I was trying to help you to install vmware tools without errors.
*


--

Claude Jones

Brunswick, MD, USA



--

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 Mon, 2008-07-21 at 00:36 -0400, Claude Jones wrote:
> On Sun July 20 2008, Alex Katebi wrote:
> > http://open-vm-tools.sourceforge.net/
> >
> > Install the vmware tools first. Then go to the above web site and download
> > & install the open-vm-tools. Let me know if you have any peoblems. I have
> > installed two Fedora 9 vmware tools this way. Forget the any any stuff you
> > don't need that.
>
> I found that website, but, it wasn't so self-evident. How does one 'install
> the vmware tools first' as you state? I normally open a vm after I've got
> vmware server running, and it boots up and gives me a message about needing to
> install or update vmware tools, and that's when I install vmware tools. How
> are you doing that first - or better, I should ask, what do you mean by first?
> First before what? Before installing the vmware package?
>
> Are you simply installing the open-vm-tools from the tarball?
>
> What advantage are you gaining by doing things that way? My vm's run just fine
> the way I'm doing it now - what improvement should I expect by learning the
> method you suggest?

In reality, you will learn very little.

I don't understand why this is, but a lot of folks seem to confuse
running a F9 Virtual Machine in an existing VMware Server setup with
installing and running VMware Server itself on F9 so that you can then
run *other* VMs.

There's nothing that the OpenSource VMware tools is going to do for you
if you're trying to do the second as opposed to the first.

VMware Server 1.0.6 with the latest vmware-any-any patch is known to
work on F9. VMware Server 2.0 RC1 has major issues on F9 - as yet, I
have only heard of one person on the VMware community forums claiming to
having it running, and that person has so far refused to share how he
did it. That leads me to think he's more likely a troll than someone
who's actually made it happen.

Again, if there is anyone who has figured out the appropriate "magic
incantation" for getting VMware Server 2.0 RC1 up and running on F9,
lots of us here would like to know about it. Do share - I'm certain
people will reply with their thanks.

Cheers,

Chris


--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.

--Socrates

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

On Mon July 21 2008, Alex Katebi wrote:
> What advantage are you gaining by doing things that way? My vm's run just
> fine the way I'm doing it now - what improvement should I expect by
> learning the method you suggest?
>
>
> I thought that you were encountering errors by running the vmware tools
> alone. I was trying to help you to install vmware tools without errors.
> *

no, I am seeking information - you made some rather cryptic statements and I
was trying to learn something - I'm afraid I'm still not understanding you - I
am not the original poster, and I'm having no problems running vmware-server
on top of Fedora 9, which is what I believe the original poster was asking
about

*to be clear, I'm running vmware-server, the latest version, installed from
the rpm on the vmware site, on my F9 box
*after running the new version as an update to my working vmware installation
yesterday, I then ran the any-any 117 patch, which built a new module for my
vmware version and running kernel
*I then started up a WinXP vm and it produced a message telling me my vmware
tools were out of date
*I then installed the vmware tools without incident, and my WinXP vm is now
running perfectly on top of Fedora9

I still don't understand exactly what it is you're doing. For example, you
stated: "Before booting your guest Fedora make sure that your vmware cd drive
is not pointing to an iso image. After booting install the vmeare tools as you
said. Then untar & unzip the vmeare tools."

First, I'm not booting a guest Fedora - I'm running mostly Windows VM's on top
of Fedora 9. Secondly, after installing vmware tools as I've said, my virtual
machine runs perfectly; but, you then state that I should untar & unzip the
vmware tools! OK - let's assume that's a typo, and you meant to say, I should
untar & unzip the open-vm-tools...If that is correct, what exactly shall I
gain from all this?
--
Claude Jones
Brunswick, MD, USA

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

Christopher A. Williams wrote:
> Again, if there is anyone who has figured out the appropriate "magic
> incantation" for getting VMware Server 2.0 RC1 up and running on F9,
> lots of us here would like to know about it. Do share - I'm certain
> people will reply with their thanks.

I have VMware Server 2.0 RC1 running on my Fedora 9 system (x86_64) with
a single Windows XP client. So what's the problem? I can check my
configuration to try to help out.

I had VMware Server 1.0.whatever, but needed USB 2.0 support, so I
upgraded to 2.0 beta, and later to RC1.

(I will be away for the second half of this week, so if I seem
unresponsive, that might be the reason.)

--
Sjoerd Mullender

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

On Mon, 2008-07-21 at 16:50 +0200, Sjoerd Mullender wrote:
> Christopher A. Williams wrote:
> > Again, if there is anyone who has figured out the appropriate "magic
> > incantation" for getting VMware Server 2.0 RC1 up and running on F9,
> > lots of us here would like to know about it. Do share - I'm certain
> > people will reply with their thanks.
>
> I have VMware Server 2.0 RC1 running on my Fedora 9 system (x86_64) with
> a single Windows XP client. So what's the problem? I can check my
> configuration to try to help out.
>
> I had VMware Server 1.0.whatever, but needed USB 2.0 support, so I
> upgraded to 2.0 beta, and later to RC1.
>
> (I will be away for the second half of this week, so if I seem
> unresponsive, that might be the reason.)

Excellent!

I'm not sure what the problem is. Everything seems to install and
compile/configure (vmware-config.pl) without issues. But then I can't
login to the Web interface at all. Closer inspection shows that several
services come up as dead. After rebooting, the startup messages show
that the system is not properly configured and about half of the
services show that they failed to start (others do start though).
Re-running vmware-config.pl shows everything re-configuring just fine
and services starting, but in reality they still show up as being dead.

I'm running the 32-bit version of F9 with this system. It's an older
due-processor Intel Xeon server that doesn't have 64-bit support.

I'm traveling this week too, so I won't be able to do anything with this
system for a few days as well...

If I could just get an idea of what needs to be there and what doesn't,
I'm sure that would help a lot...

Cheers,

Chris

--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.

--Socrates

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

Christopher A. Williams wrote:
> On Mon, 2008-07-21 at 16:50 +0200, Sjoerd Mullender wrote:
>> Christopher A. Williams wrote:
>>> Again, if there is anyone who has figured out the appropriate "magic
>>> incantation" for getting VMware Server 2.0 RC1 up and running on F9,
>>> lots of us here would like to know about it. Do share - I'm certain
>>> people will reply with their thanks.
>> I have VMware Server 2.0 RC1 running on my Fedora 9 system (x86_64) with
>> a single Windows XP client. So what's the problem? I can check my
>> configuration to try to help out.
>>
>> I had VMware Server 1.0.whatever, but needed USB 2.0 support, so I
>> upgraded to 2.0 beta, and later to RC1.
>>
>> (I will be away for the second half of this week, so if I seem
>> unresponsive, that might be the reason.)
>
> Excellent!
>
> I'm not sure what the problem is. Everything seems to install and
> compile/configure (vmware-config.pl) without issues. But then I can't
> login to the Web interface at all. Closer inspection shows that several
> services come up as dead. After rebooting, the startup messages show
> that the system is not properly configured and about half of the
> services show that they failed to start (others do start though).
> Re-running vmware-config.pl shows everything re-configuring just fine
> and services starting, but in reality they still show up as being dead.
>
> I'm running the 32-bit version of F9 with this system. It's an older
> due-processor Intel Xeon server that doesn't have 64-bit support.
>
> I'm traveling this week too, so I won't be able to do anything with this
> system for a few days as well...
>
> If I could just get an idea of what needs to be there and what doesn't,
> I'm sure that would help a lot...

One thing that I have to do every time is to do
# service vmware restart
(as root) after booting (and after I login). If I don't do that, I get
no UI. The service is started when the system boots, but I really need
to restart it for it to work.

--
Sjoerd Mullender

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

On Mon, 2008-07-21 at 18:02 +0200, Sjoerd Mullender wrote:
> Christopher A. Williams wrote:
> > On Mon, 2008-07-21 at 16:50 +0200, Sjoerd Mullender wrote:
> >> Christopher A. Williams wrote:
> >>> Again, if there is anyone who has figured out the appropriate "magic
> >>> incantation" for getting VMware Server 2.0 RC1 up and running on F9,
> >>> lots of us here would like to know about it. Do share - I'm certain
> >>> people will reply with their thanks.
> >> I have VMware Server 2.0 RC1 running on my Fedora 9 system (x86_64) with
> >> a single Windows XP client. So what's the problem? I can check my
> >> configuration to try to help out.
> >>
> >> I had VMware Server 1.0.whatever, but needed USB 2.0 support, so I
> >> upgraded to 2.0 beta, and later to RC1.
> >>
> >> (I will be away for the second half of this week, so if I seem
> >> unresponsive, that might be the reason.)
> >
> > Excellent!
> >
> > I'm not sure what the problem is. Everything seems to install and
> > compile/configure (vmware-config.pl) without issues. But then I can't
> > login to the Web interface at all. Closer inspection shows that several
> > services come up as dead. After rebooting, the startup messages show
> > that the system is not properly configured and about half of the
> > services show that they failed to start (others do start though).
> > Re-running vmware-config.pl shows everything re-configuring just fine
> > and services starting, but in reality they still show up as being dead.
> >
> > I'm running the 32-bit version of F9 with this system. It's an older
> > due-processor Intel Xeon server that doesn't have 64-bit support.
> >
> > I'm traveling this week too, so I won't be able to do anything with this
> > system for a few days as well...
> >
> > If I could just get an idea of what needs to be there and what doesn't,
> > I'm sure that would help a lot...
>
> One thing that I have to do every time is to do
> # service vmware restart
> (as root) after booting (and after I login). If I don't do that, I get
> no UI. The service is started when the system boots, but I really need
> to restart it for it to work.

Interesting... I'll give that a shot and let you know what happens.

Cheers,

Chris

--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.

--Socrates

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

Michael Eager 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.


I've come up with (at least) a partial solution.

First, my problem was with VMware Server 2.0.0 on Fedora 9
x86_64. Sorry that this was not clear.

I have been running SELinux in permissive mode. I disabled
SELinux and rebooted. I am now able to log in and see the
VI Web Access UI.

--
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