VMWare Workstation - issue compiling module in suse 11

Hi, I am trying to install VMWare Workstation 6.0.4 (the latest version as far as I know) into Suse 11. When running /usr/bin/vmware-config.pl it tries to build the necessary modules. Everything seems to go fine except for the vmblock module.

This is what I get:

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

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmblock-only'
make -C /lib/modules/2.6.25.5-1.1-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make -C /usr/src/linux-2.6.25.5-1.1 O=/usr/src/linux-2.6.25.5-1.1-obj/i386/pae/. modules
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/dentry.o
/tmp/vmware-config1/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/vmware-config1/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata’ has no member named ‘dentry’
/tmp/vmware-config1/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata’ has no member named ‘dentry’
/tmp/vmware-config1/vmblock-only/linux/dentry.c:102: error: implicit declaration of function ‘path_release’
make[4]: *** [/tmp/vmware-config1/vmblock-only/linux/dentry.o] Error 1
make[3]: *** [_module_/tmp/vmware-config1/vmblock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make: *** [vmblock.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmblock-only'
Unable to build the vmblock module.

The vmblock module enables dragging or copying files from within a guest and 
dropping or pasting them onto your host (guest to host drag and drop and file 
copy/paste).  The rest of the software provided by VMware Workstation is 
designed to work independently of this feature (including host to guest drag 
and drop and file copy/paste).

If you would like the guest to host drag and drop and file copy/paste features,
you can install the driver by running vmware-config.pl again after making sure 
that gcc, binutils, make and the kernel sources for your running kernel are 
installed on your machine. These packages are available on your distribution's 
installation CD.
 Press Enter key to continue ]

I have these packages installed:
gcc
gcc-c++
binutils
binutils-devel
linux-kernel-headers
kernel-source
make

Output of uname -r:

Linux opensuse-laptop 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux

Are there any packages I am missing that I need for this?

My understanding is that this module is not essential to run a VM, but part of the reason I want to try VMWare after using virtualbox is for the ability to drag and copy/past between host/guest. As far as I know you can’t do that in Virtualbox.

Oh yeah I have tried applying the vmware-any-any-update117.tar.gz patch as well, which is the latest one I could find, but still get the same result.

Has anyone else had this problem or know how to fix it? I’m stuck!!

I use and prefer VBox. And YES you can copy and paste. You need the VBox additions installed on the guest. Download the .iso and set it to mount in the VM settings.

You can also have folders mounted in the guest from the host.

There is also a work around for usb in the OSE ver. but I don’t need it.

Having used VMWare previously, I have to say I would never go back now.

Add this repo:
Index of /repositories/Virtualization:/VirtualBox/openSUSE_11.0

Software Management - Repo’s - VBox…install

Read the install info
VirtualBox Installation - openSUSE

I haven’t compiled with version 6.0.4 myself yet, but from what I’ve heard from others you don’t need the vmware-any-any patch with it. Could be that is what is causing you issue.

Try uninstalling the VMWare rpm (to clean up all current install scripts and modules, including vmware-any-any addins), reinstall the rpm, and just directly run the vmware-config.pl… that might get things running.

Not confirmed yet, but if you run into the problem that your VM’s are crawling, uninstall the 6.0.4 version once again and reinstall with the 6.0.3 and vmware-any-any117 patch. That version runs fine here.

Good luck! :wink:
Wj

Hey guys and thanks for the replies.

I didn’t realise you could copy/paste with Virtualbox. I have used it before with guest additions installed and always been really happy with it, but really want to be able to drag files back and forth between guest/host. Is this possible in VirtualBox?

@Magic - Yeah I tried configuring first without the any-any patch and had no success, then tried it again with it but still no luck. I think what I’ll do is try uninstalling it completely as you suggested and then go back to 6.0.3 and see if I can get that working with the patch.

At the end of the day I might just end up back on VirtualBox, but theres no harm in giving it a go!

Cheers

UPDATE - Ok I uninstalled 6.0.4 and tried to install 6.0.3 instead. Same problem with the vmblock module not loading (see previous output), whilst other modules appear to load fine.

Running the any-any patch (117) prior to vmware-config.pl did not seem to make any difference either. Output of the ‘runme.pl’ file was

Updating /usr/bin/vmware … No patch needed/available
Updating /usr/bin/vmnet-bridge … No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx … No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx … No patch needed/available
VMware modules in “/usr/lib/vmware/modules/source” has been updated.

Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
“/usr/bin/vmware-config.pl”. Do you want this script to invoke the command for
you now? [no] yes

Still stuck. Any last ideas before I trudge on back to VirtualBox in defeat? (Not that that’s necessarily a bad thing!)

Well, give this one a try: Vmware Installation aborted - openSUSE Forums

To be sure: check that the installed kernel-sources / headers (rpm -qa|grep kernel) and running kernel (uname -a) are the same.

Hope that does it… Nothing wrong with VirtualBox but defeat is the thing we don’t like! :slight_smile:

p.s. when you hit these issues always uninstall vmware before attempting a new install and/or make sure the patches in /usr/bin/vmware & /usr/lib/vmware are deleted. Otherwise you possibly keep running the build script with the wrong rpms.

I didn’t realise you could copy/paste with Virtualbox. I have used it before with guest additions installed and always been really happy with it, but really want to be able to drag files back and forth between guest/host. Is this possible in VirtualBox?

Never tried drag and drop, I suspect no, but there is really very little difference in the two methods. If you use VBox in seamless window mode, drag and drop would be difficult anyway.

I also neglected to mention, I did find VMWare a bit hungry compared to VBox, but I haven’t tried it for a while, as VBox has been so good for me. It doesn’t even throw my processor speed up.

But the best thing is to try them both and find which you prefer, assuming you can get VMWare to configure properly.

Once again, thanks to both of you.

I ran those commands as suggested and got…

rpm -qa|grep kernel:

kernel-source-2.6.25.5-1.1
kernel-pae-2.6.25.5-1.1
linux-kernel-headers-2.6.25-8.1

uname -a:

Linux opensuse-laptop 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux

Hmm, it looks to me like there is a (slight) mismatch in the version numbers between my kernel headers and kernel sources. Could this be part of the problem? If so how would I go about finding the right kernel headers?

As far as I know the kernel headers may be newer but not older.

The key thing here is that the kernel-sources and loaded kernel version match. And that is the case. :confused:

If you’ve tried the uninstall / install with version 6.0.3 I’m out of ideas so far…

What’s the exact error you getting at this moment?

What’s the exact error you getting at this moment?

Ok, I’ll try to be concise but thorough…
I uninstalled vmware completely using /usr/bin/vmware-uninstall.pl, and also did a system-wide search for vmware* and deleted any other vmware-related files I could find. Hopefully I didn’t miss anything.

Then, ran ‘vmware-install.pl’ file to build vmware workstation 6.0.3 (not using rpm). When it got to:

The installation of VMware Workstation 6.0.3 build-80004 for Linux completed 
successfully. You can decide to remove this software from your system at any 
time by invoking the following command: "/usr/bin/vmware-uninstall.pl".

Before running VMware Workstation for the first time, you need to configure it 
by invoking the following command: "/usr/bin/vmware-config.pl". Do you want 
this program to invoke the command for you now? [yes]

…I typed ‘no’, and went back and ran the vmware-any-any-update117 patch, which gave:

Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.

Before running VMware for the first time after update, you need to configure it 
for your running kernel by invoking the following command: 
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for 
you now? [no]

Typed ‘yes’ to run vmware-config.pl and got… (sorry for the code overload… and no I did not intend that to rhyme.)

Making sure services for VMware Workstation are stopped.

Stopping VMware services:
   Virtual machine monitor                                             done

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons? 
[/usr/share/icons] 

What directory contains your desktop menu entry files? These files have a 
.desktop file extension. [/usr/share/applications] 

In which directory do you want to install the application's icon? 
[/usr/share/pixmaps] 

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.

Your kernel was built with "gcc" version "4.3.1", while you are trying to use 
"/usr/bin/gcc" version "4.3". This configuration is not recommended and VMware 
Workstation may crash if you'll continue. Please try to use exactly same 
compiler as one used for building your kernel. Do you want to go with compiler 
"/usr/bin/gcc" version "4.3" anyway? [no] yes

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.25.5-1.1-pae/build/include] 

Extracting the sources of the vmmon module.

Building the vmmon module.

Unknown VMware Workstation 6.0.3 build 80004 detected. Building for Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.25.5-1.1-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make -C /usr/src/linux-2.6.25.5-1.1 O=/usr/src/linux-2.6.25.5-1.1-obj/i386/pae/. modules
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/hash.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/task.o
cc1plus: warning: command line option "-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
In file included from /tmp/vmware-config0/vmmon-only/common/task.c:1194:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:9: warning: ‘typedef’ was ignored in this declaration
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciContext.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDs.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciGroup.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciProcess.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciResource.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciSharedMem.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/compat.o
  CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: modpost: module vmmon.ko uses symbol 'init_mm' marked UNUSED
  CC      /tmp/vmware-config0/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.

/dev is dynamic:
Trying to find a suitable vmblock module for your running kernel.

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

Extracting the sources of the vmblock module.

**Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /lib/modules/2.6.25.5-1.1-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make -C /usr/src/linux-2.6.25.5-1.1 O=/usr/src/linux-2.6.25.5-1.1-obj/i386/pae/. modules
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/dentry.o
/tmp/vmware-config0/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/vmware-config0/vmblock-only/linux/dentry.c:115: error: ‘struct nameidata’ has no member named ‘dentry’
/tmp/vmware-config0/vmblock-only/linux/dentry.c:115: error: ‘struct nameidata’ has no member named ‘dentry’
/tmp/vmware-config0/vmblock-only/linux/dentry.c:116: error: implicit declaration of function ‘path_release’
make[4]: *** [/tmp/vmware-config0/vmblock-only/linux/dentry.o] Error 1
make[3]: *** [_module_/tmp/vmware-config0/vmblock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make: *** [vmblock.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
Unable to build the vmblock module.**

The vmblock module enables dragging or copying files from within a guest and 
dropping or pasting them onto your host (guest to host drag and drop and file 
copy/paste).  The rest of the software provided by VMware Workstation is 
designed to work independently of this feature (including host to guest drag 
and drop and file copy/paste).

If you would like the guest to host drag and drop and file copy/paste features,
you can install the driver by running vmware-config.pl again after making sure 
that gcc, binutils, make and the kernel sources for your running kernel are 
installed on your machine. These packages are available on your distribution's 
installation CD.
 Press Enter key to continue ]

(Eh! Word limits! See next post for rest … )

(…continued from last post)

/dev is dynamic:
Do you want networking for your virtual machines? (yes/no/help) [yes] yes

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: eth0, wlan0. 
Which one do you want to bridge to vmnet0? [eth0] wlan0

The following bridged networks have been defined:

. vmnet0 is bridged to wlan0

Do you wish to configure another bridged network? (yes/no) [no] no

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes] yes

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help) 
[yes] 

Probing for an unused private subnet (this can take some time)...

The subnet 172.16.209.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 172.16.209.0.

Do you wish to configure another NAT network? (yes/no) [no] no

Do you want to be able to use host-only networking in your virtual machines? 
[yes] yes

Configuring a host-only network for vmnet1.

Do you want this program to probe for an unused private subnet? (yes/no/help) 
[yes] yes

Probing for an unused private subnet (this can take some time)...

The subnet 192.168.241.0/255.255.255.0 appears to be unused.

The following host-only networks have been defined:

. vmnet1 is a host-only network on private subnet 192.168.241.0.

Do you wish to configure another host-only network? (yes/no) [no] no

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

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

Extracting the sources of the vmnet module.

Building the vmnet module.

Unknown VMware Workstation 6.0.3 build 80004 detected. Building for Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.25.5-1.1-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make -C /usr/src/linux-2.6.25.5-1.1 O=/usr/src/linux-2.6.25.5-1.1-obj/i386/pae/. modules
  CC [M]  /tmp/vmware-config1/vmnet-only/driver.o
  CC [M]  /tmp/vmware-config1/vmnet-only/hub.o
  CC [M]  /tmp/vmware-config1/vmnet-only/userif.o
  CC [M]  /tmp/vmware-config1/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config1/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-config1/vmnet-only/filter.o
  CC [M]  /tmp/vmware-config1/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-config1/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-config1/vmnet-only/smac_linux.x386.o
  LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config1/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
The module loads perfectly in the running kernel.

Do you want to install the Eclipse Integrated Virtual Debugger? You must have 
the Eclipse IDE installed. [no] no

Creating a new VMware VIX API installer database using the tar4 format.

Installing VMware VIX API.

You must read and accept the VMware VIX API End User License Agreement to 
continue.
Press enter to display it.
*License Agreement...*
Do you accept? (yes/no) yes

Thank you.

In which directory do you want to install the VMware VIX API binary files? 
[/usr/bin] 

In which directory do you want to install the VMware VIX API library files? 
[/usr/lib/vmware-vix/lib] 

The path "/usr/lib/vmware-vix/lib" does not exist currently. This program is 
going to create it, including needed parent directories. Is this what you want?
[yes] 

In which directory do you want to install the VMware VIX API document pages? 
[/usr/share/doc/vmware-vix] 

The path "/usr/share/doc/vmware-vix" does not exist currently. This program is 
going to create it, including needed parent directories. Is this what you want?
[yes] 

The installation of VMware VIX API 1.1.3 build-80004 for Linux completed 
successfully. You can decide to remove this software from your system at any 
time by invoking the following command: "/usr/bin/vmware-uninstall-vix.pl".

Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0                                   done
   Host network detection                                              done
   Host-only networking on /dev/vmnet1 (background)                    done
   DHCP server on /dev/vmnet1                                          done
   Host-only networking on /dev/vmnet8 (background)                    done
   DHCP server on /dev/vmnet8                                          done
   NAT service on /dev/vmnet8                                          done

The configuration of VMware Workstation 6.0.3 build-80004 for Linux for this 
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command: 
"/usr/bin/vmware".

Enjoy,

--the VMware team

Overall appears to be a successful install, but a few things just don’t seem right. The bits in the code that seem funny to me I’ve made red, but the bold bit is the part that prompted my query in the first place.

VMWare starts fine after this, though haven’t tried creating a VM yet so don’t know what will happen there.

Anyway, hope that’s covered everything. Sorry for the long posts. If we don’t know what to try next its not really a big deal but it would be nice to work it out.

Thanks again!

Thanks for taking the time to elaborate on your steps… you never know how it helps other or even might get things fixed :wink:

There is only one small difference between our install ‘methods’…
I do use the rpm to install the VMWare Workstaion initially & it could well be the install script handles things a little different.

Also I do remember seeing a couple of errors flying by while building using the vmware-any-any > vmware-config.pl but never bothered to look futher seeing things work fine here.

As added note, I do have one small annoyance and not sure where the relations lay, but it could have to do with using VMWare VI client (opening a console to another VM in my VM) that runs in my XP VM.

What happens is that at a certain point I can’t use <CTRL> <****> related commands (like opening another TAB in firefox with CRTL-T).
I need to logout of my session (restarting X) to get the keys working again.

Anyway, if you can’t get it ruining VirtualBox is a very good alternative and getting more integrated with each new version.
The seamless feature in VBox is also very nice, if not cool!
But enough babbling about that.

Not giving up but I can imagine you want to move on & won’t hold it against you… but then you can still try the rpm install :wink:

Cheers,
Willem

No problem.

Now that its installed once again I might play around for a while and see how things go. Like I said earlier I haven’t had time to create any VM’s yet so things might just work fine anyway. You said that you also received a few errors but have been largely problem-free when running it so maybe I was just being too pedantic!

Anyway, I will press on with VMWare and can always revert to VirtualBox if necessary. I agree, the seamless mode in VirtualBox is great, although I have had other display issues when using seamless mode in the past that turned me off.

Anyway, can’t thank you enough for taking the time to help out - my past experiences in suse forums where not always very helpful, so you have definitely encouraged me to stick around!

All the best,

Jamin

After I type yest, I get:

I am installing the 6.0.2 version. Any ideas?

neriodavid,

>> The following VMware kernel modules have been found on your system that
>> were
>> not installed by the VMware Installer. Please remove them then run
>> this
>> installer again.
>>
>> vmxnet
>> vmmemctl
>> vmblock
>> vmhgfs
>>
>> Execution aborted.
>>
> I am installing the 6.0.2 version. Any ideas?

The 6.0.2 version wont do with opensuse 11. You need to use 6.0.4 or it wont
compile. Anyhow from the error messages above it looks like toy have the
vmware-kmp-default and open-vm-tools packages installed. Uninstall these
first and then install VMWare Workstation 6.0.4 and it should compile
nicely.


Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Sweden AB

Yeah, it is the vmware-kmp-default and open-vm-tools problem.

Use the any-any-patch, install 6.0.2 nicely!

Thanks.

Is it really works with vm workstation 6.0.2 with openSUSE11?

Which any-any update patch should i used??