Table of Content

The opensuse 11.3 finally released out by July 15, 2010.

I used opensuse vmware as desktop alternative in my laptop, quickly test on KDE SC 4.4.4 installation on vmware workstation 7.

The installation is faster than 11.2 since it didn’t ask you any question, kind of silent installation on default setup.

Here are some post installation issues and workaround.

1) cd/dvd mount

Before mount, need to find out cd/dvd device by:

# dmesg | more | grep dvd
[   10.242564] sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray

By default there is not entry in /etc/fstab, so add to it manually.

# mkdir /media/cdrom
Add entry:
/dev/sr0             /media/cdrom         auto       ro,noauto,user,exec   0 0

# mount /dev/sr0
or
# mount /media/cdrom

Verify by:

# df -lh |grep cdrom
/dev/sr0              4.1G  4.1G     0 100% /media/cdrom

You need to issue mount when needed since it's in "noauto" mode, you also can change to auto-mount as:
/dev/sr0             /media/cdrom         auto        ro,auto,user,exec   0 0

2) usb mount

Similar as cd/dvd mount, need to check usb device at first:

# dmesg | more|grep sdb
[ 2464.590711]  sdb: sdb1

# mkdir /media/usb
# mount /dev/sdb1 /media/usb
or add entry to /etc/fstab if want to mount easily later:
/dev/sdb1             /media/usb         auto       defaults   0 0

Mount by:

# mount /media/usb

Verify by:

# df -lh |grep usb
/dev/sdb1             3.8G  4.6M  3.8G   1% /media/usb

3) vmware tool

vmware tool seems by installed during opensuse 11.3 installation, you can move in/out mouse and copy/paste, but hgfs share folder not working, need to re-install vmware tool again, will re-compile hgfs module to match current kernel.

note: before re-install vmware tool, need to make sure to install kernel-devel in YaST2, otherwise will get below error:

Searching for a valid kernel header path...
The path "" is not valid.
Would you like to change it? [yes]
Ok let's start to launch vmware tool installation, just press return until the end.

# mount /media/cdrom
# df -lh |grep cdrom
/dev/sr0              101M  101M     0 100% /media/cdrom

# cd /tmp
# tar zxpf /media/cdrom/VMwareTools-5.0.0-<xxxx>.tar.gz
# umount /media/cdrom
# cd vmware-tools-distrib
# ./vmware-install.pl
The installer found the following conflicting packages installed on the system and will now remove them:

vmware-guest-kmp-desktop

A previous installation of VMware Tools has been detected.

The previous installation was made by the tar installer (version 4).

Keeping the tar4 installer database format.

You have a version of VMware Tools installed.  Continuing this install will
first uninstall the currently installed version.  Do you wish to continue?
(yes/no) [yes]

Uninstalling the tar installation of VMware Tools.

Stopping services for VMware Tools

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon:                                      done
Virtual Printing daemon:                                            done
Unmounting HGFS shares:                                             done
Guest filesystem driver:                                            done

File /usr/lib/vmware-tools/lib32/libconf/etc/pango/pangorc is backed up to
/usr/lib/vmware-tools/lib32/libconf/etc/pango/pangorc.old.2.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gtk.immodules, and was about to
remove it.  Somebody else apparently did it already.

File /usr/lib/vmware-tools/lib32/libconf/etc/pango/pangox.aliases is backed up
to /usr/lib/vmware-tools/lib32/libconf/etc/pango/pangox.aliases.old.2.

File /usr/lib/vmware-tools/lib32/libconf/etc/gtk-2.0/gdk-pixbuf.loaders is
backed up to
/usr/lib/vmware-tools/lib32/libconf/etc/gtk-2.0/gdk-pixbuf.loaders.old.2.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/pango/pangorc, and was about to remove it.
Somebody else apparently did it already.

File /etc/vmware-tools/vmware-user.desktop is backed up to
/etc/vmware-tools/vmware-user.desktop.old.2.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/pango/pangox.aliases, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file
/usr/lib/vmware-tools/lib32/libconf/etc/pango/pango.modules, and was about to
remove it.  Somebody else apparently did it already.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gdk-pixbuf.loaders, and was about to
remove it.  Somebody else apparently did it already.

File /usr/lib/vmware-tools/lib32/libconf/etc/gtk-2.0/gtk.immodules is backed up
to /usr/lib/vmware-tools/lib32/libconf/etc/gtk-2.0/gtk.immodules.old.2.

Restoring the kernel initrd image.:

Kernel image:   /boot/vmlinuz-2.6.34-12-desktop
Initrd image:   /boot/initrd-2.6.34-12-desktop
cp: cannot stat `/usr/lib/libpng12.so.0': No such file or directory
Root device:    /dev/sda2 (mounted on / as ext4)
Resume device:  /dev/sda1
Kernel Modules: scsi_transport_spi mptbase mptscsih mptspi ata_generic thermal_sys processor thermal fan crc16 jbd2 ext4
Features:       block usb resume.userspace resume.kernel
41573 blocks
The removal of VMware Tools 8.4.2 build-261024 for Linux completed
successfully.

Installing VMware Tools.

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

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc/init.d]

What is the directory that contains the init scripts?
[/etc/init.d]

In which directory do you want to install the daemon files?
[/usr/sbin]

In which directory do you want to install the library files?
[/usr/lib/vmware-tools]

In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]

The path "/usr/share/doc/vmware-tools" 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 Tools 8.4.2 build-261024 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-tools.pl".

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

Initializing...

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon:                                      done
Virtual Printing daemon:                                            done
Unmounting HGFS shares:                                             done
Guest filesystem driver:                                            done

The module vmmemctl has already been installed on this system by another
installer or package and will not be modified by this installer.  Use the flag
--clobber-kernel-modules=vmmemctl to override.

Before you can compile modules, you need to have the following installed...

make
gcc
kernel headers of the running kernel

Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]

Searching for a valid kernel header path...
Detected the kernel headers of the running kernel at
"/lib/modules/2.6.34-12-desktop/build/include".
The path "/lib/modules/2.6.34-12-desktop/build/include" appears to be a valid
path to the kernel headers of the running kernel.
Would you like to change it? [no]

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/2.6.34-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C ../../../linux-2.6.34-12 O=/usr/src/linux-2.6.34-12-obj/i386/desktop/. modules
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc32.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpName.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dentry.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dir.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/file.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/fsutil.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/inode.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/link.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/message.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/messageBackdoor.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/module.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/page.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/request.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/rpcout.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/stubs.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/super.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/tcp.o
CC [M]  /tmp/vmware-root/modules/vmhgfs-only/transport.o
LD [M]  /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.mod.o
LD [M]  /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make -C /lib/modules/2.6.34-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C ../../../linux-2.6.34-12 O=/usr/src/linux-2.6.34-12-obj/i386/desktop/. modules
CC [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC      /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o
LD [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/2.6.34-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C ../../../linux-2.6.34-12 O=/usr/src/linux-2.6.34-12-obj/i386/desktop/. modules
CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
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/file.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/module.o
CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.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]: Leaving directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.34-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C ../../../linux-2.6.34-12 O=/usr/src/linux-2.6.34-12-obj/i386/desktop/. modules
CC [M]  /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciDatagram.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciEvent.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciProcess.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciUtil.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmci_drv.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]: Leaving directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/2.6.34-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C ../../../linux-2.6.34-12 O=/usr/src/linux-2.6.34-12-obj/i386/desktop/. modules
CC [M]  /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciDatagram.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciEvent.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciProcess.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmciUtil.o
CC [M]  /tmp/vmware-root/modules/vmci-only/vmci_drv.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]: Leaving directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/2.6.34-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C ../../../linux-2.6.34-12 O=/usr/src/linux-2.6.34-12-obj/i386/desktop/. modules
CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:312:4: warning: initialization from incompatible pointer type
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:359:4: warning: initialization from incompatible pointer type
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c: In function 鈥榁SockVmciStreamConnect鈥?
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:3163:4: warning: case value 鈥?55鈥?not in enumerated type 鈥榮ocket_state鈥?  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notify.o
CC [M]  /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M]  /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.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]: Leaving directory `/usr/src/linux-2.6.34-12-obj/i386/desktop'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'

The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer.  Use the flag
--clobber-kernel-modules=vmxnet3 to override.

The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer.  Use the flag
--clobber-kernel-modules=pvscsi to override.

Detected X.org version 7.7.0.

No drivers for X.org version: 7.7.0.
Skipping X configuration because X drivers are not included.

Creating a new initrd boot image for the kernel.

Kernel image:   /boot/vmlinuz-2.6.34-12-desktop
Initrd image:   /boot/initrd-2.6.34-12-desktop
cp: cannot stat `/usr/lib/libpng12.so.0': No such file or directory
Root device:    /dev/sda2 (mounted on / as ext4)
Resume device:  /dev/sda1
Kernel Modules: vmxnet vmxnet3 vmw_pvscsi scsi_transport_spi mptbase mptscsih mptspi ata_generic thermal_sys processor thermal fan crc16 jbd2 ext4
Features:       block usb resume.userspace resume.kernel
42303 blocks
Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration:                                   done
Guest filesystem driver:                                            done
Mounting HGFS shares:                                               done
Guest vmxnet fast network device:                                   done
VM communication interface:                                         done
VM communication interface socket family:                           done
Blocking file system:                                               done
Guest operating system daemon:                                      done
Virtual Printing daemon:                                            done

The configuration of VMware Tools 8.4.2 build-261024 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the
command line or by invoking "/usr/bin/vmware-toolbox" from the command line
during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/network stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/network start

Enjoy,

--the VMware team

After reboot you will see hgfs share folder:

# cd /mnt/hgfs/share

There are some issue not solved yet for me

1) display resolution 800×600 cannot be changed

I tried to run xorg configuration and add high resolution line in /etc/X11/xorg.conf, still come back after reboot, the good thing is you can switch to full window mode to get big display in vmware.

2) sometimes mouse lost focus in opensuse vmware, so display got frozen

3) don’t support transparent terminal