vmware-config.pl not starting automatically
Jonath
I think all these problems began when I thought it would be a good idea to
monitor the temperature of my CPU (as I had bought a new heat-sink). I
thought this would be straightforward. How naive I was.
What I'm saying here is that once upon a time I did not need to run
vmware-config.pl every time I rebooted my machine, as this happened during
the boot-up process. Those were the days . . .
Now, when I try to run vmware I get the following error (I ought to say at
this point that I'm running SuSE 7.3 and VMware Workstation 3.2.0
build-2230 . . . do you need my version of gcc? Right, it's 2.95.3):
VMware Workstation Error:
Could not open /dev/vmmon: No such device.
Please make sure that the kernel module `vmmon' is loaded.
Press "Enter" to continue...
VMware Workstation Error:
Failed to initialize monitor device.
Press "Enter" to continue...
VMware Workstation Error:
Could not open /dev/vmmon: No such device.
Please make sure that the kernel module `vmmon' is loaded.
Press "Enter" to continue...
VMware Workstation Error:
Failed to initialize monitor device.
Press "Enter" to continue...
and then, just for the hell of it, I thought I'd try again and, bizarely, I
get this error:
Cannot open/create log file '/tmp/vmware-jonathan-1309.log': Permission
denied
Unable to open log file "/tmp/vmware-jonathan-1309.log". Check your
configuration to make sure that the path specified for the log file is
valid, and that you have write privileges in this directory.
Unable to proceed without a log file.
Press "Enter" to continue...
Then when I try yet again I just get the first error repeated over and over.
If I do an lsmod, sure enough, vmmon is not listed.
and in the /dev directory:
crw------- 1 root root 119, 0 May 11 17:39 /dev/vmnet0
crw------- 1 root root 119, 1 Mar 4 19:24 /dev/vmnet1
crw------- 1 root root 119, 2 Mar 4 19:24 /dev/vmnet2
crw------- 1 root root 119, 3 Mar 4 19:24 /dev/vmnet3
crw------- 1 root root 119, 4 Mar 4 19:24 /dev/vmnet4
crw------- 1 root root 119, 5 Mar 4 19:24 /dev/vmnet5
crw------- 1 root root 119, 6 Mar 4 19:24 /dev/vmnet6
crw------- 1 root root 119, 7 Mar 4 19:24 /dev/vmnet7
crw------- 1 root root 119, 8 May 11 17:39 /dev/vmnet8
crw------- 1 root root 119, 9 Mar 4 19:24 /dev/vmnet9
Also, there is no instance of /etc/vmware/not_configured
A search for files with vmware somewhere in the title done in the directory
/etc reveals the following:
./init.d/init.d/vmware
./init.d/init.d/rc3.d/S01vmware -> ../vmware
./init.d/init.d/rc3.d/K01vmware -> ../vmware
./init.d/init.d/rc5.d/S01vmware -> ../vmware
./init.d/init.d/rc5.d/K01vmware -> ../vmware
./vmware
I got hacked off with those strange symbolic links in rc3.d and rc5.d and so
deleted them once but vmware just put them right back again.
Anyway, as soon as I run vmware-config.pl, everything works fine but this is
hardly ideal.
Anyone know what's wrong? Is there a simple fix? Is there some way of
getting vmware-config.pl to do its stuff during boot-up, rather than having
to run this file as root every time I want to use vmware?
Many thanks in advance,
Jonathan.
Chuck Gladu
>Hi there,
>
>I think all these problems began when I thought it would be a good idea to
>monitor the temperature of my CPU (as I had bought a new heat-sink). I
>thought this would be straightforward. How naive I was.
>
>What I'm saying here is that once upon a time I did not need to run
>vmware-config.pl every time I rebooted my machine, as this happened during
>the boot-up process. Those were the days . . .
>
>Now, when I try to run vmware I get the following error (I ought to say at
>this point that I'm running SuSE 7.3 and VMware Workstation 3.2.0
>build-2230 . . . do you need my version of gcc? Right, it's 2.95.3):
>
>VMware Workstation Error:
>Could not open /dev/vmmon: No such device.
>Please make sure that the kernel module `vmmon' is loaded.
>
>Press "Enter" to continue...
Sounds like you are using devfs on your host.
Either:
1. Learn how to use/configure devfs properly.
or
2. Stop using devfs.
>
>
>VMware Workstation Error:
>Failed to initialize monitor device.
>
>Press "Enter" to continue...
>
>
>VMware Workstation Error:
>Could not open /dev/vmmon: No such device.
>Please make sure that the kernel module `vmmon' is loaded.
>
>Press "Enter" to continue...
>
>
>VMware Workstation Error:
>Failed to initialize monitor device.
>
>Press "Enter" to continue...
>
>and then, just for the hell of it, I thought I'd try again and, bizarely, I
>get this error:
>
>Cannot open/create log file '/tmp/vmware-jonathan-1309.log': Permission
>denied
>Unable to open log file "/tmp/vmware-jonathan-1309.log". Check your
>configuration to make sure that the path specified for the log file is
>valid, and that you have write privileges in this directory.
>Unable to proceed without a log file.
>
>Press "Enter" to continue...
Of source....this is because you are trying to run VMware when you
haven't resolved the fatal error that caused it to stop previously.
>
>Then when I try yet again I just get the first error repeated over and over.
>
>If I do an lsmod, sure enough, vmmon is not listed.
>
>and in the /dev directory:
>
>crw------- 1 root root 119, 0 May 11 17:39 /dev/vmnet0
>crw------- 1 root root 119, 1 Mar 4 19:24 /dev/vmnet1
>crw------- 1 root root 119, 2 Mar 4 19:24 /dev/vmnet2
>crw------- 1 root root 119, 3 Mar 4 19:24 /dev/vmnet3
>crw------- 1 root root 119, 4 Mar 4 19:24 /dev/vmnet4
>crw------- 1 root root 119, 5 Mar 4 19:24 /dev/vmnet5
>crw------- 1 root root 119, 6 Mar 4 19:24 /dev/vmnet6
>crw------- 1 root root 119, 7 Mar 4 19:24 /dev/vmnet7
>crw------- 1 root root 119, 8 May 11 17:39 /dev/vmnet8
>crw------- 1 root root 119, 9 Mar 4 19:24 /dev/vmnet9
Only reason a /dev entry 'goes away" is that you deleted it...or that
you are using devfs and have not configured devfs properly.
>
>Also, there is no instance of /etc/vmware/not_configured
Of course not. VMware DID configure your system sucessfully.....it's
not vMware's fault that you misconfigured devfs removed one of your
/dev entries.
>
>A search for files with vmware somewhere in the title done in the directory
>/etc reveals the following:
>
>./init.d/init.d/vmware
>./init.d/init.d/rc3.d/S01vmware -> ../vmware
>./init.d/init.d/rc3.d/K01vmware -> ../vmware
>./init.d/init.d/rc5.d/S01vmware -> ../vmware
>./init.d/init.d/rc5.d/K01vmware -> ../vmware
>./vmware
>
>I got hacked off with those strange symbolic links in rc3.d and rc5.d and so
>deleted them once but vmware just put them right back again.
Ok, WHY would you try to delete these? They are quite important to
VMware working (which is why vmware-config.pl puts them back)
Hint: If you don't know what they are or if they are important....and
you delete them blindly.....you run a good chance of trashing your
system.
>
>Anyway, as soon as I run vmware-config.pl, everything works fine but this is
>hardly ideal.
>
>Anyone know what's wrong?
Misconfigured Host OS.
> Is there a simple fix?
See above.
> Is there some way of
>getting vmware-config.pl to do its stuff during boot-up, rather than having
>to run this file as root every time I want to use vmware?
VMware shouldn't have to recreate it's devices after every boot.
Devices aren't supposed to "go away".
The problem is that you have chosen to use devfs, which tries to
"dynamically" create and remove devices....and have not configured
devfs properly.
>
>Many thanks in advance,
>
>Jonathan.
----
Chuck Gladu
Please note: I am not a VMware employee and I do not
provide VMware support or answer VMware questions via
e-mail. Please limit your replies/questions to the
VMware newsgroups rather then e-mailing me directly.
Jonath
> On Sun, 11 May 2003 21:46:07 +0100, Jonath <j...@ulph.co.ku> wrote:
>
>>Hi there,
>>
>>I think all these problems began when I thought it would be a good idea to
>>monitor the temperature of my CPU (as I had bought a new heat-sink). I
>>thought this would be straightforward. How naive I was.
>>
>>What I'm saying here is that once upon a time I did not need to run
>>vmware-config.pl every time I rebooted my machine, as this happened during
>>the boot-up process. Those were the days . . .
>>
>>Now, when I try to run vmware I get the following error (I ought to say at
>>this point that I'm running SuSE 7.3 and VMware Workstation 3.2.0
>>build-2230 . . . do you need my version of gcc? Right, it's 2.95.3):
>>
>>VMware Workstation Error:
>>Could not open /dev/vmmon: No such device.
>>Please make sure that the kernel module `vmmon' is loaded.
>>
>>Press "Enter" to continue...
>
> Sounds like you are using devfs on your host.
>
> Either:
>
> 1. Learn how to use/configure devfs properly.
> or
> 2. Stop using devfs.
Chuck,
Many, many thanks for your help so far (perhaps we're getting there).
Unfortunately, I have no idea what devfs is. I wasn't aware I was using
this and so have no idea how to configure it.
So . . . yes, I guess I could stop using devfs (?!). How do I go about this?
I have no recollection of deleting a /dev entry. I have no reason to do
that, and I would probably end up screwing my system, so the misconfigured
devfs option is far more likely.
>>
>>Also, there is no instance of /etc/vmware/not_configured
>
> Of course not. VMware DID configure your system sucessfully.....it's
> not vMware's fault that you misconfigured devfs removed one of your
> /dev entries.
Well, in all fairness, as I suggested before, I never really thought it was
VMware's fault . . . far more likely me screwing up my system. Yes, I know,
it's all my fault.
>>
>>A search for files with vmware somewhere in the title done in the
>>directory /etc reveals the following:
>>
>>./init.d/init.d/vmware
>>./init.d/init.d/rc3.d/S01vmware -> ../vmware
>>./init.d/init.d/rc3.d/K01vmware -> ../vmware
>>./init.d/init.d/rc5.d/S01vmware -> ../vmware
>>./init.d/init.d/rc5.d/K01vmware -> ../vmware
>>./vmware
>>
>>I got hacked off with those strange symbolic links in rc3.d and rc5.d and
>>so deleted them once but vmware just put them right back again.
>
> Ok, WHY would you try to delete these? They are quite important to
> VMware working (which is why vmware-config.pl puts them back)
>
> Hint: If you don't know what they are or if they are important....and
> you delete them blindly.....you run a good chance of trashing your
> system.
Sorry, can't help it. It's only through breaking things that I learn how to
mend them. I neglected to mention that the first time around I simply
renamed these files (I would never just delete files blindly out of
frustration). Upon renaming them, I noticed vmware-config.pl simply created
new instances of these files, so I figured deleting them wouldn't hurt.
>>
>>Anyway, as soon as I run vmware-config.pl, everything works fine but this
>>is hardly ideal.
>>
>>Anyone know what's wrong?
>
> Misconfigured Host OS.
Yes, I thought as much. I guess I just need to fix this devfs thingy now.
>> Is there a simple fix?
>
> See above.
>
>> Is there some way of
>>getting vmware-config.pl to do its stuff during boot-up, rather than
>>having to run this file as root every time I want to use vmware?
>
> VMware shouldn't have to recreate it's devices after every boot.
> Devices aren't supposed to "go away".
>
> The problem is that you have chosen to use devfs, which tries to
> "dynamically" create and remove devices....and have not configured
> devfs properly.
As above, I just need to know how to configure devfs now. Is this something
straightforward? Does a howto file exist for this kind of thing?
many thanks for your help so far,
jonathan.
Chuck Gladu
>As above, I just need to know how to configure devfs now. Is this something
>straightforward? Does a howto file exist for this kind of thing?
This is the part where you turn to the Suse documentation and any of
the linux documentation sites (which is where the generic devfs
documentation would be located)
>
>many thanks for your help so far,
>
>jonathan.
----
Petr Vandrovec
> On Mon, 12 May 2003 21:27:20 +0100, Jonath <j...@ulph.co.ku> wrote:
>
>
>>As above, I just need to know how to configure devfs now. Is this something
>>straightforward? Does a howto file exist for this kind of thing?
>
>
> This is the part where you turn to the Suse documentation and any of
> the linux documentation sites (which is where the generic devfs
> documentation would be located)
If SuSE distributes at least a bit populated /dev, it should be
enough just add devfs=nomount to the kernel command line
(if you are using grub, select image you want to boot, hit 'e' (edit),
select line with kernel image (/boot/vmlinuz....), hit 'e' again, add
devfs=nomount at the end of line, enter, and hit 'b' for boot.
If system dies with error saying that it was unable to open
initial console, or mount root filesystem, you are pretty much out
of luck, and only fix is fixing devfs...
If system works, fine...
Another possible fix is: Open /etc/init.d/vmware (or /etc/rc.d/init.d/vmware
if first one does not exist) in text editor (vi), and at the beginning,
just below '#!/bin/sh' line add
mknod /dev/vmmon c 10 165 > /dev/null 2>&1
mknod /dev/vmnet0 c 119 0 > /dev/null 2>&1
mknod /dev/vmnet1 c 119 1 > /dev/null 2>&1
mknod /dev/vmnet2 c 119 2 > /dev/null 2>&1
mknod /dev/vmnet3 c 119 3 > /dev/null 2>&1
mknod /dev/vmnet4 c 119 4 > /dev/null 2>&1
mknod /dev/vmnet5 c 119 5 > /dev/null 2>&1
mknod /dev/vmnet6 c 119 6 > /dev/null 2>&1
mknod /dev/vmnet7 c 119 7 > /dev/null 2>&1
mknod /dev/vmnet8 c 119 8 > /dev/null 2>&1
and it should work even with devfs then...
Petr
Jonath
> Chuck Gladu wrote:
>> On Mon, 12 May 2003 21:27:20 +0100, Jonath <j...@ulph.co.ku> wrote:
>>
>>
>>>As above, I just need to know how to configure devfs now. Is this
>>>something straightforward? Does a howto file exist for this kind of
>>>thing?
>>
>>
>> This is the part where you turn to the Suse documentation and any of
>> the linux documentation sites (which is where the generic devfs
>> documentation would be located)
>
> If SuSE distributes at least a bit populated /dev, it should be
> enough just add devfs=nomount to the kernel command line
> (if you are using grub, select image you want to boot, hit 'e' (edit),
> select line with kernel image (/boot/vmlinuz....), hit 'e' again, add
> devfs=nomount at the end of line, enter, and hit 'b' for boot.
I really am a beginner to all of this and I'm afraid I don't understand much
of what you're saying here. How do I get to the kernel command line? I
don't think I am using 'grub' . . . well, I can't find it anywhere on the
system anyway.
> If system dies with error saying that it was unable to open
> initial console, or mount root filesystem, you are pretty much out
> of luck, and only fix is fixing devfs...
Phrases like 'system dies' and 'unable to open initial console' don't
exactly fill with confidence. I think I would rather fix devfs (so long as
this is not going to impact on the performance of any other
program/resource) then risk being unable to mount root filesystem (which
sounds horrendous). I guess then that devfs would have once been working
and it was only around the time that I tried to upgrade my kernel with I2C
that I somehow broke/removed this. I wonder if this is a common thing . .
> If system works, fine...
Like I said above, I don't really want to risk breaking my computer (because
after all, this is currently only a minor inconvenience) if there's a safer
alternative.
> Another possible fix is: Open /etc/init.d/vmware (or
> /etc/rc.d/init.d/vmware if first one does not exist) in text editor (vi),
> and at the beginning, just below '#!/bin/sh' line add
>
> mknod /dev/vmmon c 10 165 > /dev/null 2>&1
> mknod /dev/vmnet0 c 119 0 > /dev/null 2>&1
> mknod /dev/vmnet1 c 119 1 > /dev/null 2>&1
> mknod /dev/vmnet2 c 119 2 > /dev/null 2>&1
> mknod /dev/vmnet3 c 119 3 > /dev/null 2>&1
> mknod /dev/vmnet4 c 119 4 > /dev/null 2>&1
> mknod /dev/vmnet5 c 119 5 > /dev/null 2>&1
> mknod /dev/vmnet6 c 119 6 > /dev/null 2>&1
> mknod /dev/vmnet7 c 119 7 > /dev/null 2>&1
> mknod /dev/vmnet8 c 119 8 > /dev/null 2>&1
>
> and it should work even with devfs then...
> Petr
I tried the above, but it made no difference. Thank you for your help so
far. I might try a Google search for devfs, if indeed we're sure this is
the problem.
jonathan.