This Question is Possibly Answered
1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
Unable to change virtual machine power state: The process exited with an error:
vmxvmdb: Index name being generated from config file
POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 208.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Server.
POST(no connection): Failed to initialize monitor device.
Failed to initialize VM.
End of error message.
vmxvmdb: Index name being generated from config file
POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 208.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Server.
POST(no connection): Failed to initialize monitor device.
Failed to initialize VM.
End of error message.
Unable to change virtual machine power state: The process exited with an error:
vmxvmdb: Index name being generated from config file
POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 208.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Server.
POST(no connection): Failed to initialize monitor device.
Failed to initialize VM.
End of error message.
vmxvmdb: Index name being generated from config file
POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 208.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Server.
POST(no connection): Failed to initialize monitor device.
Failed to initialize VM.
End of error message.
Just like you, I couldn't manage to get vmware-server-1.0.9 working correctly with 2.6.29. Even the hard trick from tetstuser didn't pan out for me. Something else seems to get in the way.
Maybe it's because odd kernel numbers are considered as 'dev' that vmware people aren't providing ay guidance. vmware-server-2 doesn't fit my needs, it's way too big for what I have to do and because of our internal IT setup (ldap with >5k accounts), the web-interface of vmware-server-2 is crashing all the time... Not really cool...
If anyone got another avenue to try, I'm willing...
Many thanks for your answer JP,
You are the only one to did that ....!! I think that nobody from VMware has the time to answer products bugs ....
If you look at the other products, it's the same ... patch this , that ... without source authentification.
tetstuser for example, told me about debian vmware package which is carrying extra modules which are not
present in vmware-server-1.0.7 or 9 ... You have no chance to compile any scripts.
By essence, virtualization is for production ... so very dangerous to play with beta toys ....
The problem is that Xen solution needs processor virtualisation ability (like in Dual Core) and I have to deal
with several Pentiums 4 .... for an astronomy servers application ... I'm now afraid about initial VMware choice
if they proceed to such a mess of different player, server, webSphere, workstation ....
If you add Cloud Computing mess and the guys who are congratulating themselves as VMware recordmen in VMware Posting ....
Good luck and tell me if you find a better way !
Granted that i don't work for VMware, but i think if you need virtualization for production pourpose you may use commercial products (pay), which guarantee better support with these problems. I think the free versions are only for evaluation or research/test puorposes and we cannot expect too much.
However, i have the same problem with Fedora 11 (kernel 2.6.29) and vmware server 1.0.9. Actually the temporary workaround was to use old Fedora 10 kernel 2.6.27 and relative patch which still works.
However, i have the same problem with Fedora 11 (kernel 2.6.29) and vmware server 1.0.9. Actually the temporary workaround was to use old Fedora 10 kernel 2.6.27 and relative patch which still works.
The patches from the http://www.insecure.ws/warehouse/vmware-update-2.6.29-5.5.9-3.tar.bz2 that tetstuser mentioned worked just fine for me,
(Win2K virt mc under linex kernel 2.6.29.1)
but I think there are two latent bugs in that code. I tried to contact the developer of the patches on his blogpage here
http://www.insecure.ws/2009/04/21/vmware-specific-specific-55x-and-kernel-2629
but could not get my response to take. (As obspsr said "... today's new internet methods is not easing the process ..." )
If anyone here knows how to deliver a message to the person/persons running that site (the name Kang floats around there )
This is what I was trying to say to him/her, and FWIW anyone who hits problems with this patch can if they wish try my changes (no guarantees, I am only guessing and I didn't hit any problems in my short run anyway)
Thanks for this patch. It works fine for me but I have two questions on the code -
one relating to yours and second relating to the original vmware code :
1. in vmmon-only/linux/driver_compat.h LinuxDriverLockedNoPage() (file added by www.insecure.ws)
after line
pg = fdata->pgoff;
need
pg = VMMON_MAP_OFFSET(pg); /* jel */
2. linux kernel #defines
#define VM_FAULT_SIGBUS 0x0002
but in vmmon-only/include/compat_mm.h has
#ifndef NOPAGE_SIGBUS
#define NOPAGE_SIGBUS (0)
#endif
and I believe vmware's use of its NOPAGE_SIGBUS is same as linux kernel's use of its VM_FAULT_SIGBUS
so shouldn't the vmware define be
#define NOPAGE_SIGBUS (2) /* jel */
I also had the version mismatch issue when using these patches. I didn't quite get to the root of it, but tracked it far enough to see a simple fix. Un-tar vmmon.tar, and edit Makefile. Comment-out ("#") lines 25 and 28, the "ifndef VMWARE_VER" and matching "endif" lines. Re-tar the "vmmon-only" directory, re-run "vmware-config.pl". "getversion.pl" is correctly detecting VMware Server v1, but that variable had already been defined somewhere (the build process?) and was incorrect.
Now running VMware Server v1.0.9 on kernel v2.6.30.1 (thought I'd try it) on Slackware 12.2. Other than expected software-RAID speed issues, works great so far.
Now running VMware Server v1.0.9 on kernel v2.6.30.1 (thought I'd try it) on Slackware 12.2. Other than expected software-RAID speed issues, works great so far.
I was able to get VMWare server 2 working on kernel 2.6.29.
I am on a Mandriva 2009.1 server.
Needed is vmware-server-modules-2629.tar.gz attached
(and thanks to the author).
How to Install VMWare Server 2 on a 2.6.29 kernel
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. Install from a CD, not an ISO image.
Attachments:
- vmware-server-modules-2629.tar.gz (582.1 K)
> I was able to get VMWare server 2 working on kernel 2.6.29.
Thank you BUT here we are talking about vmware server 1 not 2.
Just an FYI, I recompiled with v2.6.30.5 for the CVE-2009-2692 NULL dereference. Works so far.
For those who may stumble into this thread by a search and wonder what the "final" state of affairs was:
1) Yes, you can run VMware Server v1.0.9 on kernels 2.6.29 and 2.6.30 (at least to 2.6.30.6).
2) Yes, if you are running 2.6.29 or 2.6.30 your kernel MUST have the "export-init_mm" patch.
3) No, the patch doesn't work on 2.6.31.
4) Make sure "Enable unused/obsolete exported symbols" is turned on under the kernel's "Kernel hacking" section.
5) Yes, you must apply a 3rd party (non-VMware) patch to VMware Server. I used http://www.insecure.ws/warehouse/vmware-update-2.6.29-5.5.9-3.tar.bz2 (MD5 8b5da10ece0ecbe5e0227ca081e65ec1, attached). It includes the kernel patch BUT DOES NOT apply it, that is YOUR job.
I am not affiliated with VMware. It seems that VMware has largely abandoned Server v1.0.x. I remain hopeful that some bright person with some C and kernel experience will sit down with the v1.0.9 module code and develop a PROPER patch, one that does not require any kernel modifications and that uses the newer kernel interfaces as appropriate.
1) Yes, you can run VMware Server v1.0.9 on kernels 2.6.29 and 2.6.30 (at least to 2.6.30.6).
2) Yes, if you are running 2.6.29 or 2.6.30 your kernel MUST have the "export-init_mm" patch.
3) No, the patch doesn't work on 2.6.31.
4) Make sure "Enable unused/obsolete exported symbols" is turned on under the kernel's "Kernel hacking" section.
5) Yes, you must apply a 3rd party (non-VMware) patch to VMware Server. I used http://www.insecure.ws/warehouse/vmware-update-2.6.29-5.5.9-3.tar.bz2 (MD5 8b5da10ece0ecbe5e0227ca081e65ec1, attached). It includes the kernel patch BUT DOES NOT apply it, that is YOUR job.
I am not affiliated with VMware. It seems that VMware has largely abandoned Server v1.0.x. I remain hopeful that some bright person with some C and kernel experience will sit down with the v1.0.9 module code and develop a PROPER patch, one that does not require any kernel modifications and that uses the newer kernel interfaces as appropriate.
- Daniel Johnson
Attachments:
- vmware-update-2.6.29-5.5.9-3.tar.bz2 (388.9 K)
Thanks but ... for your info, we are a lot to have dropped it in favor
of KVM and QEMU-KVM which is included in the kernel !
and works perfectly.
Best regards,
Serge.
Linus Torvalds"
Serge Montagnac
http://www.obs-psr.com
obs-psr@orange.fr
I think vmware 1.0.x is still important for many people who use it with low-end hardware and in general in all situations where vmware 2.0 cannot be used.
It don't require a cpu with virtualization support and permit easy transport of virtual machines between different hosts.
Vmware is becoming a standard virtualization system in business and industrial environment, this is why we are here searching a solution.
Probably qemu-kvm is better in performance, but in business this is not the only aspect to keep account.
It don't require a cpu with virtualization support and permit easy transport of virtual machines between different hosts.
Vmware is becoming a standard virtualization system in business and industrial environment, this is why we are here searching a solution.
Probably qemu-kvm is better in performance, but in business this is not the only aspect to keep account.
You have a point there, we can't relly too much on a free software.
Best Regards,
Jan Manzer
Jan Manzer
Best Regards,
Jan Manzer
Jan Manzer
we can't relly too much on a free software. ?? !!
please, note that :
- 1 : it is better to rely on the official kernel code of kvm .... maintained by Linus Torvalds and friends than
(We will reach an end very fast as patches are not working everywhere, on all distribs ..)
- 2 : vmware-server-1.09 is +100 Mb .... 2.0 is now +500 Mb ...
- 3 : we never got any answer nor help from VMWare developpers who are only proud claiming their amusing "post" rank position !
Best regards,
Serge
1
2
Previous
Next
Go to original post
Actions
VMworld Sessions & Labs
Online access to the latest VMworld Sessions & Labs and online services.
Learn morePurchase PSO Credits Online
Purchase credits to redeem training and consulting services online.
Buy Now