VMWare Installation Error

secureoffice · 01-06-2005, 12:56 PM

Hi

I'm trying to install VMware workstation on Suse 9.1 but get this error:

Code:

linux:/usr/src/linux-2.6.5-7.111.19 # vmware-config.pl
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor done

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux-2.6.5-7.111.19/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/linux-2.6.5-7.111.19/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. mod ules
make[1]: Entering directory `/usr/src/linux-2.6.5-7.111.19'

WARNING: Symbol version dump /usr/src/linux-2.6.5-7.111.19/Module.symvers is mi ssing, modules will have CONFIG_MODVERSIONS disabled.

CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
/bin/sh: line 1: scripts/genksyms/genksyms: No such file or directory
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.5-7.111.19'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "vmware.com/download/modules/modules.html" and
"vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

Appreciate any ideas

Kind regards

Link

cjcox · 01-06-2005, 03:39 PM

You know... this has been asked and answered a gazillion times...

But.. I'm generous...

(assuming you the suse kernel sources installed and enough tools to compile programs)

# cd /usr/src/linux
# make cloneconfig
# make prepare-all

Then you can

# vmware-config.pl

Hope that helps

secureoffice · 01-07-2005, 06:55 AM

Thanks for your generousity, I had done what you mentioned but left out the make prepare....

However, once I tried to run vmware I got this error message:

linux:/usr/src/linux #
linux:/usr/src/linux # /usr/bin/vmware
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Gtk-WARNING **: cannot open display: :0.0

Any ideas whats causing it?

Thanks a mill

SlackerLX · 01-07-2005, 07:16 AM

Just trying to help. Please, don't judge me

I had suse before

Novell posted some solutions
http://www.novell.com/coolsolutions/qna/1805.html

secureoffice · 01-07-2005, 07:36 AM

Hmm I think those workarounds are for people trying to get suse working ON vmware.

I am simply just trying to get vmware to work on suse....

Thanks for the help

secureoffice · 01-07-2005, 07:44 AM

Hmm I think the problem is that you must not be root when running vmware, I will try this and revert....

SlackerLX · 01-07-2005, 07:47 AM

Almost forgot. Reisers format behaves explicitly strange on SUSE. Sort of extra security. Always root permissions. Do you have reisers?

secureoffice · 01-07-2005, 11:06 AM

no ext2.

cjcox · 01-07-2005, 01:48 PM

Quote:

Originally posted by secureoffice
Thanks for your generousity, I had done what you mentioned but left out the make prepare....

However, once I tried to run vmware I got this error message:

linux:/usr/src/linux #
linux:/usr/src/linux # /usr/bin/vmware
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Gtk-WARNING **: cannot open display: :0.0

Any ideas whats causing it?

Thanks a mill

You are probably logged in as a normal user and trying to attach to the X server as root.
You really should not run vmware as root.. so just run it as the user that owns the
X server.

secureoffice · 01-07-2005, 01:55 PM

Yes this was the problem, thanks for the help folks.

Best wishes