I'm trying to install vmware on FC9 with the 2.6.26.3-29.fc9.x86_64 kernel, and it fails to build the kernel module. I have tried the vmware any any patch with no success. Does anyone have any suggestions?
What is the location of the directory of C header files that match your running
kernel?
/lib/modules/2.6.26.3-29.fc9.x86_64/build/include
Extracting the sources of the vmmon module.
Building the vmmon module.
VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmmon-only'
make -C /lib/modules/2.6.26.3-29.fc9.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.26.3-29.fc9.x86_64'
CC VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64 /tmp/vmware-config4/vmmon-only/linux/driver.o
/tmp/vmware-config4/vmmon-only/linux/driver.c:171: error: unknown field ânopageâ specified in initializer
/tmp/vmware-config4/vmmon-only/linux/driver.c:172: warning: initialization from incompatible pointer type
/tmp/vmware-config4/vmmon-only/linux/driver.c:175: error: unknown field ânopageâ specified in initializer
/tmp/vmware-config4/vmmon-only/linux/driver.c:176: warning: initialization from incompatible pointer type
make[2]: *** /tmp/vmware-config4/vmmon-only/linux/driver.o Error 1
make[1]: *** VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64 Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.26.3-29.fc9.x86_64'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/tmp/vmware-config4/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/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
Execution aborted.
Same problem exists with 2.6.26.3-29.fc9.i686
Also, please note that 2.6.26.3-14 has been pushed to Fedora 8 as an update and may suffer the same problem. I am thanking my stars I had the better judgement to hold off on this upgrade.
What the heck has happened to maintenance of vmware-any-any?
vmware server 2.0 rc2 installs with no problems.
Thanks for the info but I'm afraid I wouldn't touch Server 2.0 with a 10 foot pole. The dreadful web based console is a deal breaker. It's just an unspeakably awful regression.
2.6.26 is too new to be officially supported by VMWare Server 1. You would have to use the unofficial any-any patch.
Official support for newer kernels will come in Server 2.
Is there another "unofficial" patch available besides the vmware-any-any-update117-itpsycho one? That patch gets vmware to build, install and I can start up the server -- but when I try to power up a VM the host machine instantaneously reboots (well, one VM causes a segfault).
This is on Fedora 9 x86_64 with 2.6.26.3-29.fc9.x86_64 installed.
Previous versions of the kernel seem to work alright. Oh yeah, have tried with both VMware Server 1.0.6 and 1.0.7.
for what it's worth, I had the same experience with the itpsycho patch.Sudden reboot when starting a vm.
2.6.26.3-29.fc9.x86_64
Good to know I'm not the only one having the problem! ![]()
I'm back to using 2.6.25.14-108.fc9.x86_64 with 1.0.7 and everything seems ok. This is the last of the 2.6.25-based kernels for Fedora 9 I believe. Anyone have success with the 2.6.26 ones? I'd be curious which is the "last working" of that series.
As indicated, vmware server 2.0 rc2 does install on Fedora 9 with kernel 2.6.26.3-29. I would hardly say "with no problems". The monstrosity known as selinux, even in permissive mode (which supposedly does not actually limit access at all), screws with it royally and you get into a state where the various server processes are not all running, and you cannot even stop the vmware service or rerun vmware-config.pl. At length, with selinux completely disabled and after rebooting and reinstalling, I did get vmware to install, vmware-config.pl to run, and the vmware service to fully start and the console to run.
HOWEVER, at this point, trying to start any vm from the console, after a lengthy timeout, I get nothing better than (paraphrasing from memory here), "no can do, somebody is already using the cpu's virtualization mode". Which is not the case. I'm not using xen or anything like that.
Geesh. That sounds sucky. I typically turn SELinux off unless my Fedora machine is going to be doing something production or living in our DMZ. I'm all in favor of filing bugs to help them improve the system, but sometimes productivity just gets in the way. ![]()
I tried VMware Server 2.x a while back and the interface and other bugs were show-stoppers (not unexpected as it was an alpha). I haven't tried it again.
This problem indeed does exist for 2.6.26.3-14 (I'm running F8 x86_64). I'll be trying 2.0 rc2 when I get a chance.
EVP
Got it working with kernel 2.6.26.3-29.fc9.x86_64 / vmware server 1.0.7.
Start the vmware-server 1.0.7 installation. It won't compile at this point.
Download the vmmon- and vmnet patches from http://lenrek.wordpress.com/2008/08/09/vmware-server-106-for-linux-kernel-2626x/
Follow the instructions on http://lenrek.wordpress.com/2008/04/24/vmware-105-and-kernel-2625/
after copying the vmnet.tar and vmmon.tar to /usr/lib/vmware/modules/source start /usr/bin/vmware-config.pl
enjoy.
I have this problem too but figured I'd post here.
I tried that patch but I don't understand part of the tutorial. In this part: $> cd vmnet-only
$> patch -p1 < ../vmnet-2.6.25.patch
$> cd ../vmmon-only
$> patch -p1 < ../vmmon-2.6.25.patch
Where does vmnet-2.6.25.patch come from? And the other .patch file?
the instruction says to create a new folder and download the patches in this folder. Copy the vmnet.tar and vmmon.tar from /usr/lib/vmware/modules/source/ also in the new folder. Extract them, there will be two new folders, i.e. vmnet-only and vmmon-only. change to vmmon-only and execute patch -p1 < ../vmmon-2.6.25.patch. the patch file will be in the parent folder where you downloaded it. change back to the parent folder and then to vmnet-only. execute patch -p1 < ../vmnet-2.6.25.patch. Change to the parent folder and tar both directories. copy them back to /usr/lib/vmware/modules/source and start vmware-config.pl
cheers...
I think maybe your patch for the vmmon-only/linux/driver.c is missing an instruction :
in patch to function LinuxDriverLockedFault
after the lines
#ifdef VMW_NOPAGE_2624
pg = fault->pgoff;
you should add
pg = VMMON_MAP_OFFSET(pg);
(you included it in the corresponding LinuxDriverFault() patch earlier on in same file)
I don't know how serious this is - it amounts to a mask I think
John