Installing VMWARE PLayer in openSUSE 12.1

This is a list of steps to install VMWare Player (AKA VMPlayer) in openSUSE 12.1. Although it’s written for 64-bit architecture, it’s the same for 32-bit installs, just grab the 32-bit bundle.

Usually the open-source community prefer Virtualbox (AKA VBox) due to it’s community edition. However, AFAIK it lacks the usb feature found in Oracle’s edition, licensed only for personal use (you can’t use it at work), and after the original developer, Sun, was sold to Oracle, there are some concerns about the future of Sun’s opensource projects (see what happened to Ooo).

As a user of vmplayer for years, I’ve always found it reliable and easy to use, and perceptibly faster than vbox, at least the couple of times I experimented both side by side. That is not to say that vbox is not good - it is.

So here it is:

  1. Make sure that Kernel-sources, gcc and make are installed.

  2. go to VMware and register, it’s free but they do ask for a valid e-mail, name and address.

  3. Activate your account from the e-mail you’ll receive a couple minutes after registering.

  4. VMWare Player download is somewhat buried in their site, they’d prefer you buy workstation, but you can get it from here. If this link get outdated google vmware player download, it’ll be faster than navigating their site.

  5. Download the latest package (extension .bundle) for your architecture. As of this writing it is VMware-Player-4.0.1-528992.x86_64.bundle.

  6. Make it executable: from Dolphin, right-click on the .bundle file -> Properties -> Permissions -> check “Is Executable”.

  7. Open a terminal and navigate to the folder where you downloaded the file, or if you’re still in Dolphin just press F4, it will open a terminal in the current directory.

  8. Type su <ENTER> and give your root password to acquire admin rights.

  9. Type ./VMware-Player-4.0.1-528992.x86_64.bundle <ENTER>
    (Note the dot-slash immediately before the filename. You’ll obviously substitute the filename above for the one you actually downloaded.)

  10. After it finishes installing, and while you still have admin rights, type vmware-modconfig --console --install-all <ENTER> to compile the necessary service modules (drivers).

  11. After a couple minutes of compilation, the vmware services will be started. You can then close the terminal - or press F4 again if still on Dolphin - and start VMPlayer from the Applications menu > System > More Programs > VMWare Player. Accept the end-user license and you’re ready to go.

Of course, you now need to create a virtual machine (vm) where you’ll install your OS of choice. In my case I have a windows vm to run a couple apps I’m forced to use.

VMPlayer’s interface for usage and vm creation is quite friendly and intuitive, you’ll have no problems using it. Just remember to install vmware tools in the guest OS - the OS you’re running in the virtual machine - for a much better experience.

There are a number of cool things, like the unity view (nothing to do with Ubuntu), where only the guest OS apps windows are shown directly in your HOST (the real computer) desktop, almost as if they where native apps.

USB, shared folders, bridged/NAT networking and all other facilities are included, you just have to configure them.

That’s it, a nicely done and extremely useful free app, even if not opensource.

Good job brunomcl. I have added a link to your How To in the Virtualization Sticky. Just let me know if you need to make any changes to your original here and we can help out.

http://forums.opensuse.org/english/get-technical-help-here/virtualization/469824-welcome-new-opensuse-virtualization-forum.html

Thank You,

On 2012-01-03 00:36, brunomcl wrote:

> 10) After it finishes installing, and while you still have admin
> rights, type -vmware-modconfig --console --install-all- <ENTER> to
> compile the necessary service modules (drivers).

I found that running “vmplayer” directly will do that if necessary. But it
will also then start the “player” running as root, which I dislike. I stop
it that moment and start vmplayer again, this time as user.

> The interface for usage and image creation is quite friendly and
> intuitive, you’ll have no problems using it. Just remember to install
> vmware tools in the guest OS - the OS you’re running in the virtual
> machine - for a much better experience.

If the guest is an openSUSE machine, just install the rpms from openSUSE,
like “vmware-guest-kmp-desktop”, “open-vm-tools-gui”, and “open-vm-tools”.
Installing from vmware doesn’t always work as well, I think it needs
compilation and they don’t have the guest tools for all Linux flavours and
versions

> There are a number of cool things, like the unity view (nothing to do
> with Ubuntu), where only the guest OS apps windows are shown directly in
> your HOST (the real computer) desktop, almost as if they where native
> apps.

Didn’t know what Unity was, thanks.

> That’s it, a nicely done and extremely useful free app, even if not
> opensource.

It is good indeed. But still, vmware server was better, IMO. My Tom-Tom
navigator worked there, and not with player.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

That more often than not will give you the following error message:

Couldn’t run command ’ ‘’’’/usr/bin/vmware-modconfig’’’ --icon=’’‘vmware-player’’’ --appname=’’‘VMware’’’ --gcc=’’’/usr/bin/gcc’’’ --headers=’’’/lib/modules/2.6.37.6-0.11-desktop/build/include’’’ --gcc-ignore-minor ‘’.

Thus the recommendation to run with the –console --install-all option.

The user must be very careful to NOT create his VM as root, as this will create all kinds of permissions/ownership problems and will only allow the VM to be run as root. I recall one of our experienced users here recently running into this very issue.

Below is the full output of the install command. The last block, Starting VMware services, should have done after each service.

# vmware-modconfig --console --install-all
Stopping VMware services:
   VMware USB Arbitrator                                               done
   VM communication interface socket family                            done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Blocking file system                                                done
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/2.6.37.6-0.11-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C ../../../linux-2.6.37.6-0.11 O=/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’:
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:2004:37: warning: ‘newUpBase’ may be used uninitialized in this function
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Saindo do diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entrando no diretório `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' está atualizado.
make[1]: Saindo do diretório `/tmp/vmware-root/modules/vmmon-only'                                        
cp -f vmmon.ko ./../vmmon.o                                                                               
make: Saindo do diretório `/tmp/vmware-root/modules/vmmon-only'                                           
Built vmmon module                                                                                        
Using 2.6.x kernel build system.                                                                          
make: Entrando no diretório `/tmp/vmware-root/modules/vmnet-only'                                         
make -C /lib/modules/2.6.37.6-0.11-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                 
  MODULEBUILDDIR= modules                                                                                 
make[1]: Entrando no diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'                          
make -C ../../../linux-2.6.37.6-0.11 O=/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop/. modules          
  CC [M]  /tmp/vmware-root/modules/vmnet-only/driver.o                                                    
  CC [M]  /tmp/vmware-root/modules/vmnet-only/hub.o                                                       
  CC [M]  /tmp/vmware-root/modules/vmnet-only/userif.o                                                    
  CC [M]  /tmp/vmware-root/modules/vmnet-only/netif.o                                                     
  CC [M]  /tmp/vmware-root/modules/vmnet-only/bridge.o                                                    
  CC [M]  /tmp/vmware-root/modules/vmnet-only/filter.o                                                    
  CC [M]  /tmp/vmware-root/modules/vmnet-only/procfs.o                                                    
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac_compat.o                                               
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac.o                                                      
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetEvent.o                                                 
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o                                          
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.o                                                     
  Building modules, stage 2.                                                                              
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Saindo do diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entrando no diretório `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' está atualizado.
make[1]: Saindo do diretório `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Saindo do diretório `/tmp/vmware-root/modules/vmnet-only'
Built vmnet module
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/2.6.37.6-0.11-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C ../../../linux-2.6.37.6-0.11 O=/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Saindo do diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entrando no diretório `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' está atualizado.
make[1]: Saindo do diretório `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Saindo do diretório `/tmp/vmware-root/modules/vmblock-only'
Built vmblock module
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.37.6-0.11-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C ../../../linux-2.6.37.6-0.11 O=/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciProcess.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDs.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciGroup.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Saindo do diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entrando no diretório `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' está atualizado.
make[1]: Saindo do diretório `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Saindo do diretório `/tmp/vmware-root/modules/vmci-only'
Built vmci module
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/2.6.37.6-0.11-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C ../../../linux-2.6.37.6-0.11 O=/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/util.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/stats.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notify.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vsock-only/vsock.mod.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Saindo do diretório `/usr/src/linux-2.6.37.6-0.11-obj/x86_64/desktop'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entrando no diretório `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' está atualizado.
make[1]: Saindo do diretório `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Saindo do diretório `/tmp/vmware-root/modules/vsock-only'
Built vsock module
Starting VMware services:
   VMware USB Arbitrator                                               done
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   Shared Memory Available                                             done

On 2012-01-21 22:16, brunomcl wrote:
>
> robin_listas;2427654 Wrote:
>> I found that running “vmplayer” directly will do that if necessary.
>
> That more often than not will give you the following error message:

I have not seen it. I actually did the process a minute ago, no problems.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

That would depend on file system, it will work for all users if created on a FAT32 partition. Not that I recommend running it as root, it’s probably a bad idea.

AFAIK that’s because FAT32 has no permissions per se, so any file in such a system will belong to whomever is accessing (or perhaps mounted) it under linux.

Lucky you. This happened in the last 6 installs/updates I did in four different machines running oS 11.3/11.4/12.1 64-bits + KDE4.6/4.7. You’ll also find many reports on this error in these and vmware’s fora and, of course, if you google it.

So for me it makes sense to give a solution straight away, even if it does not affect everybody. Piecemeal information is for misers :slight_smile:

On 2012-01-23 02:36, brunomcl wrote:
>
> robin_listas;2432832 Wrote:
>> I have not seen it. I actually did the process a minute ago, no
>> problems.
>
> Lucky you. This happened in the last 6 installs/updates I did in four
> different machines running oS 11.3/11.4/12.1 64-bits + KDE4.6/4.7.
> You’ll also find many reports on this error in these and vmware’s fora
> and, of course, if you google it.

Maybe there is something different in the way I do it and the way they do
it. I can not google the error because I don’t know what error it is.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-01-03 00:36, brunomcl wrote:

> 1) Make sure that -Kernel-sources-, -gcc- and -make- are installed.

I have installed a fresh install (for testing) of 12.1, and just added vm player. I found that the
kernel sources are not needed: what I installed is, first the “base development pattern”, and then
kernel-desktop-devel (2.7M) and kernel-devel (37.3M), which have a smaller size than the package
“kernel-source” (371M).

I normally install kernel-source, but this time I needed to minimize size. And it works :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.1 “Asparagus” GM (bombadillo))