VMware

This Question is Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
1 Replies Last post: Jul 27, 2009 12:09 PM by rfong1  

Unable to install Vmware 2.01 on 2.6.29 kernel[RESOLVED] posted: May 1, 2009 6:44 AM

Click to view cis4smack's profile Lurker
cis4smack
4 posts since
Apr 30, 2009
Hi all,

I've just upgraded to Mandriva 2009.1 and now I'm unable to re-install Vmware 2.01. I get the following message....

Kernel: 2.6.29.1-server-4mnb


Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config5/vmmon-only'
make -C /lib/modules/2.6.29.1-server-4mnb/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.29.1-server-4mnb'
+ CC [M] /root/tmp/vmware-config5/vmmon-only/linux/driver.o+
In file included from /root/tmp/vmware-config5/vmmon-only/linux/driver.c:31:
/root/tmp/vmware-config5/vmmon-only/./include/compat_wait.h:78: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:67: error: previous declaration of ‘poll_initwait’ was here
In file included from /root/tmp/vmware-config5/vmmon-only/./common/vmx86.h:31,
+ from /root/tmp/vmware-config5/vmmon-only/linux/driver.h:29,+
+ from /root/tmp/vmware-config5/vmmon-only/linux/driver.c:101:+
/root/tmp/vmware-config5/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined
In file included from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/numa_64.h:5,
+ from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/numa.h:4,+
+ from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/acpi.h:28,+
+ from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/fixmap_64.h:15,+
+ from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/fixmap.h:7,+
+ from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/apic.h:8,+
+ from /usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/smp.h:13,+
+ from include/linux/smp.h:36,+
+ from include/linux/topology.h:33,+
+ from include/linux/mmzone.h:767,+
+ from include/linux/gfp.h:4,+
+ from include/linux/kmod.h:22,+
+ from include/linux/module.h:13,+
+ from /root/tmp/vmware-config5/vmmon-only/./include/compat_module.h:27,+
+ from /root/tmp/vmware-config5/vmmon-only/linux/driver.c:26:+
/usr/src/linux-2.6.29.1-server-4mnb/arch/x86/include/asm/apicdef.h:132:1: warning: this is the location of the previous definition
/root/tmp/vmware-config5/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1423: error: too many arguments to function ‘smp_call_function’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1987: error: ‘struct task_struct’ has no member named ‘euid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1987: error: ‘struct task_struct’ has no member named ‘uid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1988: error: ‘struct task_struct’ has no member named ‘fsuid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1988: error: ‘struct task_struct’ has no member named ‘uid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1989: error: ‘struct task_struct’ has no member named ‘egid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1989: error: ‘struct task_struct’ has no member named ‘gid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1990: error: ‘struct task_struct’ has no member named ‘fsgid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:1990: error: ‘struct task_struct’ has no member named ‘gid’
/root/tmp/vmware-config5/vmmon-only/linux/driver.c:2007: error: too many arguments to function ‘smp_call_function’
make[2]: *** [/root/tmp/vmware-config5/vmmon-only/linux/driver.o] Error 1
make[1]: *** --_module_/root/tmp/vmware-config5/vmmon-only-- Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.29.1-server-4mnb'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/root/tmp/vmware-config5/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and
"http://www.vmware.com/go/unsup-linux-tools".

Execution aborted.


Any ideas on how to resolve...thank you in advance.

RESOLVED:

After creating a thread, I started to read other threads and one user posted a site with a solution that helped him. The solution also help fix the problem I was having.

http://www.saarlinux.de/blog/?p=5

Tags: vmware_server_2.0, mandriva, mandriva, 2009.1, 2009, 1, server, 2.01, installation, linux, 64

Re: Unable to install Vmware 2.01 on 2.6.29 kernel[RESOLVED]

1. Jul 27, 2009 12:09 PM in response to: cis4smack
Click to view rfong1's profile Novice
rfong1
2 posts since
Jul 23, 2009

For anyone interested, here's the solution in more detail:

1. After installing VMware, go to the source directory under
vmware-server-distrib and unpack vmware-server-modules-2629.tar

root downloads#
pwd
/extra/downloads root downloads#
ls config
VMware-server-2.0.1-156745.i386.tar
MAYCANON35WEST_EXCHANGE_07222009-144042.PDF
VMware-server-console-1.0.1-29996.i386.rpm
runtest.log
VMware-server-console-1.0.1-29996.tar.gz
vmci.tar
vmware-server-distrib/
vmmon.tar
VMware-server-linux-client-1.0.1-29996.zip
vmnet.tar
vmware-server-modules-2629.tar
vmware-6.5.2-modules-2.6.29-fix.sh
VMware-vix-1.0.1-29996.tar.gz
vmwarepatches/
VMware-VmPerlAPI-1.0.1-29996.tar
VMware-server-1.0.1-29996.tar
VMware-VmPerlAPI-1.0.1-29996.tar.gz
VMware-server-1.0.9-156507.tar
vsock.tar
root downloads#
pwd
/extra/downloads root downloads# cd
vm*b
root vmware-server-distrib# cd
lib
root lib# cd
mod* root modules# cd source

root source# tar xvf
/extra/downloads/vmware-server-modules-2629.tar

vmci.tar
vmmon.tar
vmnet.tar
vsock.tar root source#
ls vmci.tar vmmon.tar vmnet.tar
vsock.tar
root source# cd
.. root modules#
ls binary/
source/
root modules# cd
.. root lib#
ls bin/ help/ include/ licenses/ net-services.sh*
share/ webAccess/
config hostd/ isoimages/ messages/ perl/
tools-upgraders/ xkeymap/
configurator/ icu/ lib/ modules/ python/
vmacore/
root lib# cd
.. root vmware-server-distrib#
ls
bin/ doc/ etc/ FILES installer/ lib/ man/ sbin/
vmware-install.pl@ vmware-vix/

2. Install VMWare using ./vmware-install.pl and receive an error

root vmware-server-distrib#
./vmware-install.pl
A previous installation of VMware Server has been
detected.

The previous installation was made by the rpm installer (version
3).

Converting the rpm3 installer database format
to the tar3 installer database format.

You have a product that conflicts with VMware Server installed.
Continuing
this install will first uninstall this product. Do you wish to
continue?
(yes/no)
yes

Creating a new VMware Server installer database using the tar4
format.

Installing VMware Server.

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/rc.d]
What is the directory that contains the init scripts?
[/etc/rc.d/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]

In which directory do you want to install the manual files?
[/usr/share/man]

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

The path "/usr/share/doc/vmware" 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 Server 2.0.1 build-156745 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 Server 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

Making sure services for VMware Server are stopped.

Stopping VMware autostart virtual machines:
Virtual machines
FAILED
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent
FAILED
Stopping VMware services:
VMware Authentication Daemon [
OK ]
Virtual machine monitor [
OK ]

You must read and accept the End User License Agreement to
continue.
Press enter to display it.
NOTICE: BY DOWNLOADING AND INSTALLING, COPYING OR OTHERWISE USING
THE
SOFTWARE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS VMWARE MASTER
END
USER LICENSE AGREEMENT ("EULA"). IF YOU DO NOT AGREE TO THE TERMS
OF
<snip>
Software for internal or external use, promotion, review or as
part of a
solution, please apply now at
http://www.vmware.com/go/distribution.

Do you accept? (yes/no) yes

Thank you.

None of the pre-built vmmon modules for VMware Server 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?
[/lib/modules/2.6.29.3-desktop-1mnb/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config27/vmmon-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M]
/root/tmp/vmware-config27/vmmon-only/linux/driver.o CC [M]
/root/tmp/vmware-config27/vmmon-only/linux/driverLog.o CC [M]
/root/tmp/vmware-config27/vmmon-only/linux/hostif.o /root/tmp/vmware-config27/vmmon-only/linux/hostif.c:3600:2:
warning: #warning current->cred->fsuid = 0;
/root/tmp/vmware-config27/vmmon-only/linux/hostif.c:3607:2:
warning: #warning current->cred->fsuid =
fsuid; /root/tmp/vmware-config27/vmmon-only/linux/hostif.c:3625:2:
warning: #warning cap_lower(current->cred->cap_effective,
CAP_SYS_RESOURCE); CC [M]
/root/tmp/vmware-config27/vmmon-only/common/comport.o CC [M]
/root/tmp/vmware-config27/vmmon-only/common/cpuid.o CC [M]
/root/tmp/vmware-config27/vmmon-only/common/hashFunc.o CC [M]
/root/tmp/vmware-config27/vmmon-only/common/memtrack.o CC [M]
/root/tmp/vmware-config27/vmmon-only/common/phystrack.o CC [M]
/root/tmp/vmware-config27/vmmon-only/common/task.o CC [M]
/root/tmp/vmware-config27/vmmon-only/common/vmx86.o CC [M]
/root/tmp/vmware-config27/vmmon-only/vmcore/moduleloop.o LD [M]
/root/tmp/vmware-config27/vmmon-only/vmmon.o Building modules, stage
2. MODPOST 1
modules CC
/root/tmp/vmware-config27/vmmon-only/vmmon.mod.o LD [M]
/root/tmp/vmware-config27/vmmon-only/vmmon.ko make[1]: Leaving directory
`/usr/src/linux-2.6.29.3-desktop-1mnb' cp -f vmmon.ko
./../vmmon.o make: Leaving directory
`/root/tmp/vmware-config27/vmmon-only' The vmmon module loads perfectly into the running
kernel.

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

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config27/vmci-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M]
/root/tmp/vmware-config27/vmci-only/linux/driver.o CC [M]
/root/tmp/vmware-config27/vmci-only/linux/driverLog.o CC [M]
/root/tmp/vmware-config27/vmci-only/linux/vmciKernelIf.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciContext.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciDatagram.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciDriver.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciDs.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciEvent.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciGroup.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciHashtable.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciProcess.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciQueuePair.o CC [M]
/root/tmp/vmware-config27/vmci-only/common/vmciResource.o LD [M]
/root/tmp/vmware-config27/vmci-only/vmci.o Building modules, stage
2.
MODPOST 1
modules CC
/root/tmp/vmware-config27/vmci-only/vmci.mod.o LD [M]
/root/tmp/vmware-config27/vmci-only/vmci.ko make[1]: Leaving directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
cp -f vmci.ko
./../vmci.o make: Leaving directory
`/root/tmp/vmware-config27/vmci-only'
The vmci module loads perfectly into the running
kernel.

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

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config27/vsock-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M]
/root/tmp/vmware-config27/vsock-only/linux/af_vsock.o CC [M] /root/tmp/vmware-config27/vsock-only/linux/driverLog.o
CC [M] /root/tmp/vmware-config27/vsock-only/linux/util.o
CC [M] /root/tmp/vmware-config27/vsock-only/linux/vsockAddr.o
LD [M] /root/tmp/vmware-config27/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd"
[/root/tmp/vmware-config27/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd"
[/root/tmp/vmware-config27/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID"
[/root/tmp/vmware-config27/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send"
[/root/tmp/vmware-config27/vsock-only/vsock.ko] undefined!
CC /root/tmp/vmware-config27/vsock-only/vsock.mod.o
LD [M] /root/tmp/vmware-config27/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-2.6.29.3-desktop-1mnb'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/root/tmp/vmware-config27/vsock-only'
Unable to make a vsock module that can be loaded in the running
kernel:
insmod: error inserting '/root/tmp/vmware-config27/vsock.o': -1
Unknown symbol in module
There is probably a slight difference in the kernel configuration
between the
set of C header files you specified and your running kernel. You
may want to
rebuild a kernel based on that directory, or specify another
directory.

The VM communication interface socket family is used in
conjunction with the VM
communication interface to provide a new communication path among
guests and
host. The rest of this software provided by VMware Server is
designed to work
independently of this feature. If you wish to have the VSOCK
feature 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.
http:// Press the Enter key to continue.
(Type ^C to abort the script)

3. Notice the error

insmod: error inserting '/root/tmp/vmware-config27/vsock.o': -1
Unknown symbol in module

This is fixed by looking at:

http://communities.vmware.com/thread/208316
and see the script:

# Here's a simple batch file for fixing this error

cd /usr/lib/vmware/modules/source || exit

tar xvf vmci.tar

if [ ! -f vsock.tar.original ] ; then

mv vsock.tar vsock.tar.original && cp vsock.tar.original
vsock.tar

else

/bin/cp vsock.tar.original vsock.tar

fi

tar xvf vsock.tar

cd vmci-only

make || exit

mv Module.symvers ../vsock-only

cd ..

mv -i vsock.tar vsock.tar.bak_$( date '+%F_%H-%M-%S' ) &&
tar cvf vsock.tar vsock-only

echo "===== List of backups of vsock.tar in
/usr/lib/vmware/modules/source ====="

ls -1trd vsock.tar.bak_*

echo

rm -rf vsock-only vmci-only

#now run:

#/usr/bin/vmware-config.pl

I did not run this script, but followed the script's instructions as if
I ran the script. Note that a tar files is fixed and recreated
with "tar cvf". You will also need to remove the files in
rm /lib/modules/2.6.29.3-desktop-1mnb/misc.

root vsock-only# cd /usr/lib/vmware/modules/source
root source# tar xvf vmci.tar

./vmci-only/

./vmci-only/linux/

./vmci-only/linux/driverLog.c

./vmci-only/linux/driverLog.h

./vmci-only/linux/driver.c

./vmci-only/linux/vmciKernelIf.c

./vmci-only/Makefile.normal

./vmci-only/Makefile

./vmci-only/Makefile.kernel

./vmci-only/autoconf/

./vmci-only/autoconf/epoll.c

./vmci-only/autoconf/geninclude.c

./vmci-only/COPYING

./vmci-only/common/

./vmci-only/common/vmciProcess.h

./vmci-only/common/vmciHashtable.h

./vmci-only/common/vmciProcess.c

./vmci-only/common/vmciCommonInt.h

./vmci-only/common/vmciHashtable.c

./vmci-only/common/vmciEvent.h

./vmci-only/common/vmciEvent.c

./vmci-only/common/vmciContext.c

./vmci-only/common/vmciQueuePair.h

./vmci-only/common/vmciDatagram.h

./vmci-only/common/vmciDatagram.c

./vmci-only/common/vmciGroup.c

./vmci-only/common/vmciGroup.h

./vmci-only/common/vmciQueuePair.c

./vmci-only/common/vmciDs.c

./vmci-only/common/vmciDriver.h

./vmci-only/common/vmciResource.h

./vmci-only/common/vmciDriver.c

./vmci-only/common/vmciDsInt.h

./vmci-only/common/vmciResource.c

./vmci-only/common/vmciContext.h

./vmci-only/include/

./vmci-only/include/compat_wait.h

./vmci-only/include/compat_version.h

./vmci-only/include/driver-config.h

./vmci-only/include/includeCheck.h

./vmci-only/include/compat_mm.h

./vmci-only/include/compat_spinlock.h

./vmci-only/include/compat_slab.h

./vmci-only/include/compat_page.h

./vmci-only/include/vmci_infrastructure.h

./vmci-only/include/compat_pgtable.h

./vmci-only/include/circList.h

./vmci-only/include/compat_interrupt.h

./vmci-only/include/compat_kernel.h

./vmci-only/include/vm_assert.h

./vmci-only/include/compat_module.h

./vmci-only/include/vm_device_version.h

./vmci-only/include/compat_file.h

./vmci-only/include/pgtbl.h

./vmci-only/include/vmci_call_defs.h

./vmci-only/include/vmware_pack_end.h

./vmci-only/include/vmci_queue_pair.h

./vmci-only/include/vmware.h

./vmci-only/include/vm_atomic.h

./vmci-only/include/vmware_pack_init.h

./vmci-only/include/vm_basic_defs.h

./vmci-only/include/vmci_handle_array.h

./vmci-only/include/vmci_defs.h

./vmci-only/include/vmci_iocontrols.h

./vmci-only/include/compat_highmem.h

./vmci-only/include/compat_sched.h

./vmci-only/include/compat_semaphore.h

./vmci-only/include/vmci_kernel_if.h

./vmci-only/include/vm_basic_types.h

./vmci-only/include/vmware_pack_begin.h
root source# mv vsock.tar vsock.tar.original
root source# cp vsock.tar.original vsock.tar
root source# tar xvf vsock.tar

./vsock-only/

./vsock-only/linux/

./vsock-only/linux/vmci_sockets.h

./vsock-only/linux/vsockAddr.h

./vsock-only/linux/vsockSocketWrapper.h

./vsock-only/linux/af_vsock.h

./vsock-only/linux/af_vsock.c

./vsock-only/linux/vsockPacket.h

./vsock-only/linux/vsockVmci.h

./vsock-only/linux/vsockAddr.c

./vsock-only/linux/util.h

./vsock-only/linux/driverLog.c

./vsock-only/linux/vsock_version.h

./vsock-only/linux/vmciDatagram.h

./vsock-only/linux/driverLog.h

./vsock-only/linux/util.c

./vsock-only/linux/vsockCommon.h

./vsock-only/linux/vmciContext.h

./vsock-only/Makefile.normal

./vsock-only/Makefile

./vsock-only/Makefile.kernel

./vsock-only/autoconf/

./vsock-only/autoconf/statfs1.c

./vsock-only/autoconf/getsb1.c

./vsock-only/autoconf/skas1.c

./vsock-only/autoconf/setnice.c

./vsock-only/autoconf/filldir1.c

./vsock-only/autoconf/sk_filter.c

./vsock-only/autoconf/epoll.c

./vsock-only/autoconf/geninclude.c

./vsock-only/autoconf/cachecreate.c

./vsock-only/README

./vsock-only/COPYING

./vsock-only/include/

./vsock-only/include/compat_namei.h

./vsock-only/include/compat_wait.h

./vsock-only/include/compat_version.h

./vsock-only/include/driver-config.h

./vsock-only/include/compat_string.h

./vsock-only/include/includeCheck.h

./vsock-only/include/compat_init.h

./vsock-only/include/compat_mm.h

./vsock-only/include/compat_spinlock.h

./vsock-only/include/compat_slab.h

./vsock-only/include/compat_workqueue.h

./vsock-only/include/compat_sock.h

./vsock-only/include/compat_uaccess.h

./vsock-only/include/compat_page.h

./vsock-only/include/vmci_infrastructure.h

./vsock-only/include/circList.h

./vsock-only/include/compat_kernel.h

./vsock-only/include/vm_assert.h

./vsock-only/include/compat_module.h

./vsock-only/include/compat_file.h

./vsock-only/include/compat_statfs.h

./vsock-only/include/vmci_call_defs.h

./vsock-only/include/vmware_pack_end.h

./vsock-only/include/vmware.h

./vsock-only/include/vmware_pack_init.h

./vsock-only/include/vm_basic_defs.h

./vsock-only/include/vmci_defs.h

./vsock-only/include/compat_completion.h

./vsock-only/include/vmci_iocontrols.h

./vsock-only/include/compat_fs.h

./vsock-only/include/compat_sched.h

./vsock-only/include/compat_list.h

./vsock-only/include/compat_semaphore.h

./vsock-only/include/vmci_kernel_if.h

./vsock-only/include/vm_basic_types.h

./vsock-only/include/vmware_pack_begin.h
root source# cd vmci-only
root vmci-only# make
Using 2.6.x kernel build
system.
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
Building modules, stage
2.
MODPOST 1
modules make[1]: Leaving directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
cp -f vmci.ko
./../vmci.o root vmci-only# mv Module.symvers
../vsock-only
mv: overwrite `../vsock-only/Module.symvers'?
y
root vmci-only# cd
..
root source# mv -i vsock.tar vsock.tar.bak_$( date
'+%F_%H-%M-%S' )
root source# tar cvf vsock.tar
vsock-only

vsock-only/
vsock-only/linux/
vsock-only/linux/af_vsock.o
vsock-only/linux/.af_vsock.o.cmd
vsock-only/linux/driverLog.o
vsock-only/linux/.driverLog.o.cmd
vsock-only/linux/util.o
vsock-only/linux/.util.o.cmd
vsock-only/linux/vsockAddr.o
vsock-only/linux/.vsockAddr.o.cmd
vsock-only/linux/vmci_sockets.h
vsock-only/linux/vsockAddr.h
vsock-only/linux/vsockSocketWrapper.h
vsock-only/linux/af_vsock.h
vsock-only/linux/af_vsock.c
vsock-only/linux/vsockPacket.h
vsock-only/linux/vsockVmci.h
vsock-only/linux/vsockAddr.c
vsock-only/linux/util.h
vsock-only/linux/driverLog.c
vsock-only/linux/vsock_version.h
vsock-only/linux/vmciDatagram.h
vsock-only/linux/driverLog.h
vsock-only/linux/util.c
vsock-only/linux/vsockCommon.h
vsock-only/linux/vmciContext.h
vsock-only/autoconf/
vsock-only/autoconf/statfs1.c
vsock-only/autoconf/getsb1.c
vsock-only/autoconf/skas1.c
vsock-only/autoconf/setnice.c
vsock-only/autoconf/filldir1.c
vsock-only/autoconf/sk_filter.c
vsock-only/autoconf/epoll.c
vsock-only/autoconf/geninclude.c
vsock-only/autoconf/cachecreate.c
vsock-only/include/
vsock-only/include/compat_namei.h
vsock-only/include/compat_wait.h
vsock-only/include/compat_version.h
vsock-only/include/driver-config.h
vsock-only/include/compat_string.h
vsock-only/include/includeCheck.h
vsock-only/include/compat_init.h
vsock-only/include/compat_mm.h
vsock-only/include/compat_spinlock.h
vsock-only/include/compat_slab.h
vsock-only/include/compat_workqueue.h
vsock-only/include/compat_sock.h
vsock-only/include/compat_uaccess.h
vsock-only/include/compat_page.h
vsock-only/include/vmci_infrastructure.h
vsock-only/include/circList.h
vsock-only/include/compat_kernel.h
vsock-only/include/vm_assert.h
vsock-only/include/compat_module.h
vsock-only/include/compat_file.h
vsock-only/include/compat_statfs.h
vsock-only/include/vmci_call_defs.h
vsock-only/include/vmware_pack_end.h
vsock-only/include/vmware.h
vsock-only/include/vmware_pack_init.h
vsock-only/include/vm_basic_defs.h
vsock-only/include/vmci_defs.h
vsock-only/include/compat_completion.h
vsock-only/include/vmci_iocontrols.h
vsock-only/include/compat_fs.h
vsock-only/include/compat_sched.h
vsock-only/include/compat_list.h
vsock-only/include/compat_semaphore.h
vsock-only/include/vmci_kernel_if.h
vsock-only/include/vm_basic_types.h
vsock-only/include/vmware_pack_begin.h
vsock-only/.tmp_versions/
vsock-only/.tmp_versions/vsock.mod
vsock-only/vsock.o
vsock-only/.vsock.o.cmd
vsock-only/modules.order
vsock-only/vsock.mod.c
vsock-only/Module.markers
vsock-only/vsock.mod.o
vsock-only/.vsock.mod.o.cmd
vsock-only/vsock.ko
vsock-only/.vsock.ko.cmd
vsock-only/Module.symvers.orig
vsock-only/Module.symvers
vsock-only/Makefile.normal
vsock-only/Makefile
vsock-only/Makefile.kernel
vsock-only/README
vsock-only/COPYING root source# ls -1trd
vsock.tar.bak_*

vsock.tar.bak_2009-07-23_16-08-25 root source# rm -rf vsock-only
vmci-only

root source#
/usr/bin/vmware-config.pl
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.
vmci
vmmon

I.e. - 'rm
/lib/modules/2.6.29.3-desktop-1mnb/misc/<ModuleName>.{o,ko}'

Execution aborted.

root source# ls /lib/modules/2.6.29.3-desktop-1mnb/misc/
vmci.ko@ vmci.o vmmon.ko@
vmmon.o
root source# rm /lib/modules/2.6.29.3-desktop-1mnb/misc/*
rm: remove symbolic link
`/lib/modules/2.6.29.3-desktop-1mnb/misc/vmci.ko'? y
rm: remove regular file
`/lib/modules/2.6.29.3-desktop-1mnb/misc/vmci.o'? y
rm: remove symbolic link
`/lib/modules/2.6.29.3-desktop-1mnb/misc/vmmon.ko'? y
rm: remove regular file
`/lib/modules/2.6.29.3-desktop-1mnb/misc/vmmon.o'? y

4. Now that the script has fixed Module.symvers, you can run the VMware
config
script again. Notice that the error is removed.

root source# /usr/bin/vmware-config.pl
Making sure services for VMware Server are stopped.

Stopping VMware autostart virtual machines:
Virtual machines
FAILED
Stopping VMware management
services:
VMware Virtual Infrastructure Web
Access
VMware Server Host Agent
FAILED
Stopping VMware
services:
VMware Authentication Daemon [
OK ]
Virtual machine communication interface [
OK ]
Virtual machine monitor [
OK ]

None of the pre-built vmmon modules for VMware Server 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?
[/lib/modules/2.6.29.3-desktop-1mnb/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config34/vmmon-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M]
/root/tmp/vmware-config34/vmmon-only/linux/driver.o CC [M]
/root/tmp/vmware-config34/vmmon-only/linux/driverLog.o CC [M]
/root/tmp/vmware-config34/vmmon-only/linux/hostif.o /root/tmp/vmware-config34/vmmon-only/linux/hostif.c:3600:2:
warning: #warning current->cred->fsuid = 0;
/root/tmp/vmware-config34/vmmon-only/linux/hostif.c:3607:2:
warning: #warning current->cred->fsuid =
fsuid; /root/tmp/vmware-config34/vmmon-only/linux/hostif.c:3625:2:
warning: #warning cap_lower(current->cred->cap_effective,
CAP_SYS_RESOURCE); CC [M]
/root/tmp/vmware-config34/vmmon-only/common/comport.o CC [M]
/root/tmp/vmware-config34/vmmon-only/common/cpuid.o CC [M]
/root/tmp/vmware-config34/vmmon-only/common/hashFunc.o CC [M]
/root/tmp/vmware-config34/vmmon-only/common/memtrack.o CC [M]
/root/tmp/vmware-config34/vmmon-only/common/phystrack.o CC [M]
/root/tmp/vmware-config34/vmmon-only/common/task.o CC [M]
/root/tmp/vmware-config34/vmmon-only/common/vmx86.o CC [M]
/root/tmp/vmware-config34/vmmon-only/vmcore/moduleloop.o LD [M]
/root/tmp/vmware-config34/vmmon-only/vmmon.o Building modules, stage
2. MODPOST 1
modules CC
/root/tmp/vmware-config34/vmmon-only/vmmon.mod.o LD [M]
/root/tmp/vmware-config34/vmmon-only/vmmon.ko make[1]: Leaving directory
`/usr/src/linux-2.6.29.3-desktop-1mnb' cp -f vmmon.ko
./../vmmon.o make: Leaving directory
`/root/tmp/vmware-config34/vmmon-only' This program previously created the
file
/lib/modules/2.6.29.3-desktop-1mnb/misc/vmmon.o, and was about to
remove it.
Somebody else apparently did it
already.

This program previously created the file
/lib/modules/2.6.29.3-desktop-1mnb/misc/vmmon.ko, and was about to
remove it.
Somebody else apparently did it
already.

The vmmon module loads perfectly into the running kernel.

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

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config34/vmci-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M]
/root/tmp/vmware-config34/vmci-only/linux/driver.o CC [M]
/root/tmp/vmware-config34/vmci-only/linux/driverLog.o CC [M]
/root/tmp/vmware-config34/vmci-only/linux/vmciKernelIf.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciContext.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciDatagram.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciDriver.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciDs.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciEvent.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciGroup.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciHashtable.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciProcess.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciQueuePair.o CC [M]
/root/tmp/vmware-config34/vmci-only/common/vmciResource.o LD [M]
/root/tmp/vmware-config34/vmci-only/vmci.o Building modules, stage
2.
MODPOST 1
modules CC
/root/tmp/vmware-config34/vmci-only/vmci.mod.o LD [M]
/root/tmp/vmware-config34/vmci-only/vmci.ko make[1]: Leaving directory
`/usr/src/linux-2.6.29.3-desktop-1mnb'
cp -f vmci.ko
./../vmci.o make: Leaving directory
`/root/tmp/vmware-config34/vmci-only'
This program previously created the
file
/lib/modules/2.6.29.3-desktop-1mnb/misc/vmci.o, and was about to
remove it.
Somebody else apparently did it
already.

This program previously created the file
/lib/modules/2.6.29.3-desktop-1mnb/misc/vmci.ko, and was about to
remove it.
Somebody else apparently did it
already.

The vmci module loads perfectly into the running kernel.

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

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config34/vsock-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M] /root/tmp/vmware-config34/vsock-only/linux/af_vsock.o
CC [M] /root/tmp/vmware-config34/vsock-only/linux/driverLog.o
CC [M] /root/tmp/vmware-config34/vsock-only/linux/util.o
CC [M] /root/tmp/vmware-config34/vsock-only/linux/vsockAddr.o
LD [M] /root/tmp/vmware-config34/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /root/tmp/vmware-config34/vsock-only/vsock.mod.o
LD [M] /root/tmp/vmware-config34/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-2.6.29.3-desktop-1mnb'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/root/tmp/vmware-config34/vsock-only'
The vsock module loads perfectly into the running kernel.

Do you want networking for your virtual machines? (yes/no/help)
yes

Configuring a bridged network for vmnet0.

Please specify a name for this network.
Bridged

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

All your ethernet interfaces are already bridged.

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

Configuring a NAT network for vmnet8.

Please specify a name for this network. NAT

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.155.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.155.0.

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

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

None of the pre-built vmnet modules for VMware Server 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.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config34/vmnet-only'
make -C /lib/modules/2.6.29.3-desktop-1mnb/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.29.3-desktop-1mnb'
CC [M] /root/tmp/vmware-config34/vmnet-only/driver.o
CC [M] /root/tmp/vmware-config34/vmnet-only/hub.o
CC [M] /root/tmp/vmware-config34/vmnet-only/userif.o
CC [M] /root/tmp/vmware-config34/vmnet-only/netif.o
CC [M] /root/tmp/vmware-config34/vmnet-only/bridge.o
/root/tmp/vmware-config34/vmnet-only/bridge.c:652:2: warning:
#warning EHUD gotta figure out what this does and how to fix it:
atomic_add(skb->truesize, &sk->sk_wmem_alloc);
CC [M] /root/tmp/vmware-config34/vmnet-only/filter.o
CC [M] /root/tmp/vmware-config34/vmnet-only/procfs.o
CC [M] /root/tmp/vmware-config34/vmnet-only/smac_compat.o
CC [M] /root/tmp/vmware-config34/vmnet-only/smac.o
CC [M] /root/tmp/vmware-config34/vmnet-only/vnetEvent.o
CC [M] /root/tmp/vmware-config34/vmnet-only/vnetUserListener.o
LD [M] /root/tmp/vmware-config34/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /root/tmp/vmware-config34/vmnet-only/vmnet.mod.o
LD [M] /root/tmp/vmware-config34/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.29.3-desktop-1mnb'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/root/tmp/vmware-config34/vmnet-only'
The vmnet module loads perfectly into the running kernel.

The default port : 902 is not free. We have selected a suitable
alternative
port for VMware Server use. You may override this value now.
Remember to use this port when installing remote clients on other
machines.
Please specify a port for remote connections to use 903

WARNING: VMware Server has been configured to run on a port
different from the
default port. Please make sure to use this port when installing
remote clients
on other machines.

Do you want this program to set up permissions for your registered
virtual
machines? This will be done by setting new permissions on all
files found in
the "/etc/vmware/vm-list" file. no yes

Please specify a port for standard http connections to use 8222

Please specify a port for secure http (https) connections to use
8333


The current administrative user for VMware Server is ''. Would
you like to
specify a different administrator? no

Using root as the VMware Server administrator.

You have a pre-existing vmInventory.xml. The new version will be
created as
/etc/vmware/hostd/NEW_vmInventory.xml. Please check the new file
for any new
values that you may need to migrate to your current
vmInventory.xml.

By the way, you can choose a different directory to store your virtual
machines.

In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines] /extra/vmware

You have a pre-existing datastores.xml. The new version will be
created as
/etc/vmware/hostd/NEW_datastores.xml. Please check the new file
for any new
values that you may need to migrate to your current datastores.xml.

Do you want to enter a serial number now? (yes/no/help) no yes

Please enter your 20-character serial number.

Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel: <Enter your
serial number here>

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

Installing VMware VIX API.

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.6.2 build-156745 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".

Enjoy,

--the VMware team

Starting VMware services:
Virtual machine monitor [
OK ]
Virtual machine communication interface [
OK ]
VM communication interface socket family: [
OK ]
Virtual ethernet [
OK ]
Bridged networking on /dev/vmnet0 [
OK ]
Host-only networking on /dev/vmnet8 (background) [
OK ]
DHCP server on /dev/vmnet8 [
OK ]
NAT service on /dev/vmnet8 [
OK ]
VMware Server Authentication Daemon (background) [
OK ]
Shared Memory Available [
OK ]
Starting VMware management services:
VMware Server Host Agent (background) [
OK ]
VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
Virtual machines [
OK ]

The configuration of VMware Server 2.0.1 build-156745 for Linux
for this
running kernel completed successfully.

5. You will get one last error. Ignore it.

root downloads# vmware
Launching VMware Web Access using /usr/bin/xdg-open
kioclient(8837): Session bus not found

6. Log in using your root Unix password.

Go to

http://localhost:8222

You may have to reboot your machine if your system is sluggish.
Open with Mozilla Firefox and on Console tab, click "Install
plug-in".
Create a virtual machine.

Attachments:

Actions

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities