VMware re-configure every time for network support

Message

MattSharp · Post by **MattSharp** » Tue May 04, 2004 12:12 am

Everytime I reboot my host box and try run vmware the network support is not there. When I the proceed to run "/etc/init.d/vmware start" and then try to run vmware it errors out and I am forced to run vmware-conf.pl (or whatever teh file is) and reset all the confiuration. What is wrong that is causing this to happen?

Is this easily fixable? Would adding Vmware to the RC fix this at all?

badMojo · Post by **badMojo** » Tue May 04, 2004 2:25 am

I have had the same annoying problem and am also interested in a solution.

sfcfagwdse · Post by **sfcfagwdse** » Tue May 04, 2004 5:10 am

I remeber i had this problem and i removed a file called not.configured or something like that in /etc/vmware. I dont know the exact file name cause its gone. After that the /etc/init.d/vmware start script worked fine for me.

MattSharp · Post by **MattSharp** » Thu May 06, 2004 7:36 pm

sfcfagwdse wrote:I remeber i had this problem and i removed a file called not.configured or something like that in /etc/vmware. I dont know the exact file name cause its gone. After that the /etc/init.d/vmware start script worked fine for me.

I don't have a file like that anywhere....

Moonlight-Flower · Post by **Moonlight-Flower** » Thu Jul 15, 2004 12:43 pm

I don't have any such file either, and I have to reconfigure vmware every time I reboot as well...

Kabuto · Post by **Kabuto** » Thu Jul 15, 2004 2:31 pm

What do you mean by network support? As in any IP support?

malone · Post by **malone** » Thu Jul 15, 2004 2:46 pm

Are you using udev?

acid2000 · Post by **acid2000** » Thu Jul 15, 2004 5:48 pm

Check that /etc/init.d/vmware is the gentoo version and not the vmware version.

Moonlight-Flower · Post by **Moonlight-Flower** » Fri Jul 16, 2004 5:19 am

I'm using udev, and my vmware is from portage.

ikaro · Post by **ikaro** » Fri Jul 16, 2004 5:43 am

i dont think you need to start /etc/init.d/vmware
i use udev too, and once i run the configuration script after a new kernel, I can start using vmware right away with no problems, and the network works fine.

which kernel are you using, and did you remember to fix the link from linux -> kernel dir

searcher · Post by **searcher** » Fri Jul 16, 2004 7:30 am

just to be on the safe side, try

Code: Select all

rc-update add vmware default

and start vmware services by typing

Code: Select all

/etc/init.d/vmware start

If you get some error run

Code: Select all

vmware-config.pl

first, and if that breaks you have to remove a single file in /etc/vmware called something like `not_configured'.

~searcher

Moonlight-Flower · Post by **Moonlight-Flower** » Fri Jul 16, 2004 7:36 am

Well... that's the problem. It's in default, and every time it tries to reboot and start, I have to reconfigure it, or it doesn't work. It works fine after I reconfigure, as long as I don't reboot... and there's nothing like no_configured in /etc/vmware...

Code: Select all

amackenzie@chaos vmware $ ls
config  init.d  installer.sh  installer.sh.old.0  locations  vmnet8

malone · Post by **malone** » Fri Jul 16, 2004 10:41 am

If you're using udev, then every time you reboot the special device nodes created by the config script are lost. I added the following to /etc/init.d/vmware ( right after start() ):

Code: Select all

	# ========================================================
	# create device nodes for use with udev
	# ========================================================
	einfo "Creating Vmware device nodes" 
	
	if [ ! -e "/dev/vmnet0" ]; then 
		mknod -m 600  /dev/vmnet0 c 119 0 
	fi 
	if [ ! -e "/dev/vmnet1" ]; then 
		mknod -m 600  /dev/vmnet1 c 119 1 
	fi 
	if [ ! -e "/dev/vmnet8" ]; then 
		mknod -m 600  /dev/vmnet8 c 119 8 
	fi 
	if [ ! -e "/dev/vmmon" ]; then 
		mknod -m 666  /dev/vmmon c 10 165 
	fi 
	if [ ! -e "/dev/parport0" ]; then 
		mknod -m 600  /dev/parport0 c 99 0 
	fi 
	if [ ! -e "/dev/parport1" ]; then 
		mknod -m 600  /dev/parport1 c 99 1 
	fi 
	if [ ! -e "/dev/parport2" ]; then 
		mknod -m 600  /dev/parport2 c 99 2 
	fi 
	if [ ! -e "/dev/parport3" ]; then 
		mknod -m 600  /dev/parport3 c 99 3 
	fi
	# ========================================================
	# end of device node creation
	# ========================================================

You may want to put it in a different file, so that any updates wont overwrite it. Just be sure that they are created before /etc/init.d/vmware is run.

Cheers.

Moonlight-Flower · Post by **Moonlight-Flower** » Fri Jul 16, 2004 11:15 am

Ahhh... that would be it then... many many thanks! ^_^

2lt.chronic · Post by **2lt.chronic** » Sat Jun 11, 2005 11:57 pm

wow nearly a year after this post and the same problem still occurs..... I solved it by above method.. :S