Skip navigation
VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1,239 Views 15 Replies Last post: Oct 4, 2008 2:26 AM by frank001 RSS
1 2 Previous Next
axelseaa Novice 6 posts since
Apr 7, 2007
Currently Being Moderated

Sep 12, 2008 8:28 PM

VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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.

 

 

 

 

 

 

 

 

fnj Lurker 5 posts since
Jan 28, 2007
Currently Being Moderated
1. Sep 12, 2008 8:57 PM in response to: axelseaa
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

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?

fnj Lurker 5 posts since
Jan 28, 2007
Currently Being Moderated
3. Sep 13, 2008 6:11 PM in response to: axelseaa
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

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.

SMB Expert 404 posts since
Mar 14, 2006
Currently Being Moderated
4. Sep 15, 2008 9:05 AM in response to: fnj
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

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.

rayvd Enthusiast 51 posts since
Jun 13, 2007
Currently Being Moderated
5. Sep 15, 2008 8:03 PM in response to: SMB
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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.

 

 

frank001 Lurker 4 posts since
Sep 16, 2008
Currently Being Moderated
6. Sep 16, 2008 6:30 AM in response to: rayvd
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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

rayvd Enthusiast 51 posts since
Jun 13, 2007
Currently Being Moderated
7. Sep 16, 2008 6:45 AM in response to: frank001
Re: VMWare 1.0.7 on 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.

fnj666 Lurker 1 posts since
Jan 6, 2005
Currently Being Moderated
8. Sep 16, 2008 6:53 AM in response to: axelseaa
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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.

 

 

rayvd Enthusiast 51 posts since
Jun 13, 2007
Currently Being Moderated
9. Sep 16, 2008 7:11 AM in response to: fnj666
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

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.

EVillageProwl… Lurker 3 posts since
May 15, 2007
Currently Being Moderated
10. Sep 16, 2008 6:31 PM in response to: rayvd
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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

 

 

frank001 Lurker 4 posts since
Sep 16, 2008
Currently Being Moderated
11. Sep 20, 2008 5:26 AM in response to: rayvd
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

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.

Red Squirrel Enthusiast 106 posts since
Jul 3, 2006
Currently Being Moderated
12. Sep 21, 2008 5:18 PM in response to: frank001
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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?   

 

 

frank001 Lurker 4 posts since
Sep 16, 2008
Currently Being Moderated
13. Sep 22, 2008 2:50 AM in response to: Red Squirrel
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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

 

 

 

 

 

johnlumby Novice 24 posts since
Apr 4, 2006
Currently Being Moderated
14. Oct 3, 2008 10:41 AM in response to: frank001
Re: VMWare 1.0.7 on 2.6.26.3-29.fc9.x86_64

 

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

 

 

Bookmarked By (0)

Share This Page

Communities