Comments for blog.limedaley.com/post/vmware-1.0.5-patch-for-2.6.25-kernel

Comment #1739

2009-06-18T15:37:17Z

I ended up switching over to VirtualBox. Though even that wasn't as straightforward as I am used to on Debian. (I am running "squeeze", and the modules package for virtualbox hasn't been updated properly to run with the kernel that is distributed with squeeze, so I had to play around with it).

Comment #1738

2008-09-27T16:06:59Z

So, the stopwatches have been running an awfully long time. I have been unable to get vmware 1.0.7 running on 2.6.26. I even tried out some other virtual systems, but I can't find one that allows direct access to the hard drive, rather than a virtual hard drive file. urgh.

I guess I'll need to dual-boot to DOS to finish up a project.

Comment #1737

2008-09-23T19:16:22Z

I apparently haven't run vmware in a while, and went to try it today, but discovered that I have upgraded my kernel since the last time I ran it, and of course, vmware is using old API calls, and so doesn't work on 2.6.26...

So, off to try virtualbox instead, which seems to be kept much more up-to-date by the authors, rather than users having to depend on people like me to do the authors' work for them.

Start your stopwatches, let's see how this switchover goes.

Comment #1736

2008-06-11T11:23:30Z

Doesn't work for me (VMware-server-1.0.5-80187.i386.rpm, kernel 2.6.25.4):

/tmp/vmware-config2/vmmon-only/./include/compat_wait.h:60: error: conflicting types for 'poll_initwait'

include/linux/poll.h:65: error: previous declaration of 'poll_initwait' was here

/tmp/vmware-config1/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type

/tmp/vmware-config1/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type

Simply killing the bogus poll_initwait redefinition in compat_wait.h fixes that.

Next error:

/tmp/vmware-config3/vmmon-only/linux/hostif.c:3363: error: 'struct task_struct' has no member named 'nice'

Looks like for some reason the Makefiles didn't define VMW_HAVE_SET_USER_NICE even though 2.6.25.3 has it, simply replacing #if defined(VMW_HAVE_SET_USER_NICE) with #if 1 fixes that (and of course breaks old kernels)

After that, it compiles, but hits the init_mm reference which a quick grep can't locate.

Comment #1735

2008-05-17T07:46:30Z

Hi,

I just want to say - thank you. These patches has been solved my problem with very new 2.6.25.3 kernel and vmware-server-1.0.5. Thanks a lot.

P.S. It seems we should migrate to server 2.0 is there any who already play with it ? I'm litle bit worried about native console ...

Comment #1734

2008-05-11T20:25:55Z

I guess I'll need to make the "next" links more obvious, since two of you haven't seen it.

Comment #1733

2008-05-11T19:15:17Z

Jorge :

make menuconfig

then search with / keyword "symbols"

This is in kernel hacking section

Comment #1732

2008-05-09T18:00:35Z

First, thanks so much for this patch.

Second, to jondaley: in the directory where you extraceted the kernel source type (as root) `make menuconfig`. Towards the bottom you will have a Kernel Hacking section. select it and hit enter. The option is there. After you enable the unused/obsolete symbols you will have to recompile and install the new kernel.

Comment #1731

2008-05-06T18:55:49Z

I came here to report sucess and unsucess.

Now i have the other problem herwarth reported, but I just using 2.6.26-rc1.

What it can be done?

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config6/vmmon-only'

make -C /lib/modules/2.6.26-rc1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.25'

CC [M] /tmp/vmware-config6/vmmon-only/linux/driver.o

/tmp/vmware-config6/vmmon-only/linux/driver.c:146: error: unknown field 'nopage' specified in initializer

/tmp/vmware-config6/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type

/tmp/vmware-config6/vmmon-only/linux/driver.c:150: error: unknown field 'nopage' specified in initializer

/tmp/vmware-config6/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type

make[2]: *** [/tmp/vmware-config6/vmmon-only/linux/driver.o] Error 1

make[1]: *** [_module_/tmp/vmware-config6/vmmon-only] Error 2

make[1]: Leaving directory `/usr/src/linux-2.6.25'

make: *** [vmmon.ko] Error 2

make: Leaving directory `/tmp/vmware-config6/vmmon-only'

Unable to build the vmmon module.

Comment #1730

2008-05-06T13:10:55Z

hmmm -mm kernel is the problem....

compiled the vanilla kernel with the patches and works. do not install the -mm patchbundle

Comment #1729

2008-05-05T14:23:52Z

hello,

applied your patches but now i get the nopage error..... can you help me out?

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config6/vmmon-only'

make -C /lib/modules/2.6.25-mm1-helux/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD /. modules

make[1]: Entering directory `/usr/src/linux-2.6.25-mm1-helux'

CC [M] /tmp/vmware-config6/vmmon-only/linux/driver.o

/tmp/vmware-config6/vmmon-only/linux/driver.c:146: error: unknown field ânopageâ specified in initializer

/tmp/vmware-config6/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type

/tmp/vmware-config6/vmmon-only/linux/driver.c:150: error: unknown field ânopageâ specified in initializer

/tmp/vmware-config6/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type

make[2]: *** [/tmp/vmware-config6/vmmon-only/linux/driver.o] Error 1

make[1]: *** [_module_/tmp/vmware-config6/vmmon-only] Error 2

make[1]: Leaving directory `/usr/src/linux-2.6.25-mm1-helux'

make: *** [vmmon.ko] Error 2

make: Leaving directory `/tmp/vmware-config6/vmmon-only'

Unable to build the vmmon module.

Comment #1728

2008-05-04T20:59:42Z

patches worked perfectly on vmware 1.0.5 and custom linux-2.6.25.1-x64 host.

i just patched the installer tar files, makes it easier :)

many thanks

Comment #1727

2008-05-04T11:39:21Z

Ok i asked google and it's on "Kernel Hacking".

I'm compiling kernel and tomorow when i'll be next to the machine i'll reboot it and test and let you know.

Thanks,

Jorge

Comment #1726

2008-05-04T11:09:14Z

Kernel hacking -> CONFIG_UNUSED_SYMBOLS

Comment #1725

2008-05-04T11:01:05Z

Oh i see, can you tell me where is the option to enable/desable the unused/obsolete symbols in kernel?

I mean, in wich menu.

Comment #1724

2008-05-04T09:42:14Z

Jorge: see the comment by Brice above. Unfortunately, some of his text was lost, but he says you have to enable unused/obsolete symbols. We need a "real" updated version of the module so you don't need that workaround.

Comment #1723

2008-05-04T08:59:47Z

This works great but i just have one problem.

When trying to load the module is complains about "init_mm" and the vmware setup fails.

My Kernel is a 2.6.25 vanilla.

Any help?

Comment #1722

2008-04-28T17:41:08Z

That was a PEBKAC on my part. I assumed the 1.0.5 was referring to your patch, not vmware. Having not used vmware server until now ;).

Comment #1721

2008-04-27T20:42:03Z

Thanks Brice. Note that some of your comment was truncated - it must have thought your < was the start of an HTML tag You can type it as < I should probably figure out some way of saying "ignore HTML" in the comment, or even have that set to the default.

Comment #1720

2008-04-27T18:31:23Z

Jon -> apologies for the delay! I migrated to VMware beta 2... and then went to Xen for a bit. I just got around to testing your patches and they worked flawlessly!

Here's the steps I took;

VMWare 1.0.5 on 2.6.25 steps;

Download the TAR binary from http://www.vmware.com/download/server/
Uncompress, run vmware-install.pl as root.

2a. I choose to install the binaries to /opt/vmware/bin for organizational purposes.

2b. Do not choose to run vmware-config.pl. If you do by accident, no problem. Proceed to step 3 when compilation fails.

Download the vmmon-2.6.25.patch and vmnet-2.6.25 path courtesy of Jon Daley [above]

3a. Copy the patches to the VMware module source [e.g. /opt/vmware/lib/vmware/modules/source or /usr/lib/vmware/modules/source ]

Apply the patches to the VMware modules (see 3a above for example of file locations)

4a. Uncompress vmnet.tar and vmmon.tar

4b. Apply the appropriate patch for example;

--  

cd vmmon-only  

patch -p1  Enable unused/obsolete exported symbols )

1a. If it is not, you will recieve complaints about unrecognized symbol (init_mm) during vmmon compilation.

2b. You can always rebuild your kernel and compile VMware 1.0.5 later, so don't worry too much about this at first.

Comment #1719

2008-04-26T22:46:26Z

Tested with 2.6.25 vanilla and vmware-server-1.0.5: all went ok except some minor warnings

…

Building the vmmon module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config2/vmmon-only’

make -C /lib/modules/2.6.25/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/home/tmp214/Downloads/linux-2.6.25′

CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o

CC [M] /tmp/vmware-config2/vmmon-only/linux/hostif.o

CC [M] /tmp/vmware-config2/vmmon-only/common/cpuid.o

CC [M] /tmp/vmware-config2/vmmon-only/common/hash.o

CC [M] /tmp/vmware-config2/vmmon-only/common/memtrack.o

CC [M] /tmp/vmware-config2/vmmon-only/common/phystrack.o

CC [M] /tmp/vmware-config2/vmmon-only/common/task.o

CC [M] /tmp/vmware-config2/vmmon-only/common/vmx86.o

/tmp/vmware-config2/vmmon-only/common/vmx86.c: In function ‘Vmx86_GetkHzEstimate’:

/tmp/vmware-config2/vmmon-only/common/vmx86.c:1899: warning: passing argument 4 of ‘Div643264’ from incompatible pointer type

/tmp/vmware-config2/vmmon-only/common/vmx86.c:1908: warning: passing argument 4 of ‘Div643232’ from incompatible pointer type

CC [M] /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o

LD [M] /tmp/vmware-config2/vmmon-only/vmmon.o

Building modules, stage 2.

MODPOST 1 modules

WARNING: modpost: module vmmon.ko uses symbol ‘init_mm’ marked UNUSED

CC /tmp/vmware-config2/vmmon-only/vmmon.mod.o

LD [M] /tmp/vmware-config2/vmmon-only/vmmon.ko

make[1]: Leaving directory `/home/tmp214/Downloads/linux-2.6.25′

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory `/tmp/vmware-config2/vmmon-only’

The module loads perfectly in the running kernel.

Comment #1718

2008-04-26T21:46:05Z

I guess my post got spammed so I thought I would write it again to help others.

I finally got vmware up and running. Thanks Jon for the patch. However, it would be great to supply more complete info for linux noobs like me.

I did the same mistake as Matthew but downloaded vmplayer instead of vmserver.

I provided additional detailed info on setting up vmserver on the 2.6.25 kernel at lenrek's site.

Cheers

Frank

Comment #1717

2008-04-26T21:39:33Z

Hi, I finally got it to work!

Thanks Jon for the patch!

I left a detailed explanation for a linux noob like me on how to get it up and running at the following link:

http://lenrek.wordpress.com/2008/04/24/vmware-105-and-kernel-2625/

I had the same problem as Matthew. I downloaded wmplayer instead of vmserver.

More detailed instructions would be a great help.

Thanks a bunch.

Frank

Comment #1716

2008-04-26T16:39:55Z

Ah, this patch is meant for the vmware server, not workstation.

Comment #1715

2008-04-26T04:40:03Z

So I tried the patch, got a few rejections

For those that do not know the patches apply to the contents of the source tar files that live in /usr/lib/vmware/modules/source (if you installed via RPM). One untars the file (via sudo or as the root user), and then applies the patch files with the aptly named patch command. This can be achieved via the normal form:

patch -p0 < $FOO

where $FOO is the name of the patch file.

Here was my mileage-

sudo patch -p0 < ~/vmnet-2.6.25.patch

patching file vmnet-only/bridge.c

Hunk #1 succeeded at 106 (offset 4 lines).

patching file vmnet-only/compat_wait.h

Hunk #1 succeeded at 38 (offset 4 lines).

patching file vmnet-only/driver.c

Hunk #1 FAILED at 516.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/driver.c.rej

patching file vmnet-only/Makefile.kernel

Hunk #1 FAILED at 7.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/Makefile.kernel.rej

patching file vmnet-only/netif.c

Hunk #1 FAILED at 295.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/netif.c.rej

patching file vmnet-only/sk_alloc.c

Hunk #1 succeeded at 12 with fuzz 2 (offset 8 lines).

Hunk #2 succeeded at 13 with fuzz 2.

patching file vmnet-only/vm_basic_types.h

Hunk #1 FAILED at 154.

Hunk #2 succeeded at 187 with fuzz 1 (offset 19 lines).

Hunk #3 succeeded at 294 with fuzz 1 (offset 32 lines).

1 out of 3 hunks FAILED -- saving rejects to file vmnet-only/vm_basic_types.h.rej

patching file vmnet-only/vmnetInt.h

Hunk #1 FAILED at 35.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/vmnetInt.h.rej

patching file vmnet-only/vnetInt.h

Hunk #1 FAILED at 29.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/vnetInt.h.rej

wget -qO - https://jon.limedaley.com/plog/gallery/1/vmmon-2.6.25.patch | sudo patch -p0

patching file vmmon-only/include/vcpuset.h

Hunk #1 FAILED at 71.

1 out of 1 hunk FAILED -- saving rejects to file vmmon-only/include/vcpuset.h.rej

patching file vmmon-only/include/vm_basic_types.h

Hunk #1 succeeded at 163 (offset 9 lines).

Hunk #3 succeeded at 273 with fuzz 1 (offset 11 lines).

patching file vmmon-only/linux/driver.c

Hunk #1 FAILED at 1655.

1 out of 1 hunk FAILED -- saving rejects to file vmmon-only/linux/driver.c.rej

patching file vmmon-only/Makefile.kernel

I'll be happy to provide the *.rejs or the whole source tar.

FWIW, This was a virginal install of VMware-workstation-6.0.2-59824.x86_64.rpm

No vmware-any-any-116.tgz.

Comment #1714

2008-04-26T03:27:18Z

Could you be more detailed in how to use the patch? As a rather new linux user, I am not sure what to do with it.

I tried Lenrek's suggestion but I got a bunch errors when patching. I posted on his site also.

I just compiled the new kernel and now want to install vmware. What I really want to do is log into my window's partition using vmware.

Thanks

Frank

Comment #1713

2008-04-24T16:40:58Z

Ah, sorry about the filename problem, and yes, I should have used links to the direct filenames, instead the html. I'll fix that as well.

Comment #1712

2008-04-24T15:52:50Z

Hi, confirmed. The patches work as supposed to. I got a bit confused, because I tried to wget the patches from the links above. That results in garbage being downloaded since the links point to another page first (doh!).

I also had reconfigure all my virtual networks, but then everything works fine. Thanks for the help everyone.

Comment #1711

2008-04-24T13:17:29Z

Hi,

I have successfully installed vmware server 1.0.5 on my vanilla kernel 2.6.25 following the simple passes explained at lenrek.wordpress.com and, of course, using your patches.

I'd only point out two things:

* I applied the patches to a standard vmware server 1.0.5 without "any-any" pathes

* since you have posted the vmmon patch attachment with "vmnet 2.6.25" name, it's too easy to miss its download.

Thank you very much

Comment #1710

2008-04-23T21:11:56Z

I just copied the modules from vmware's forums for 1.0.4 -> 2.6.24, added the one line that the guy forgot to add, and mentioned in his post.

The only "real" work I did was copying the one function from 2.6.25 that was made static. No interesting changes from the prior patch.

Comment #1709

2008-04-23T18:34:14Z

I would try it, but I'm afraid I am not that familiar with vmware server's inner workings. Can you go a bit into detail on what to apply those patches on, and where to find those modules etc? So far I always used the any-any patches, this one seems a bit too heavy right now.

Appreciate your effort, thanks in advance!

Comment #1708

2008-04-23T15:05:41Z

Has anyone else tried the patch? It'd be nice to comment here and let folks know if it does or does not work.

Comment #1707

2008-04-20T17:01:45Z

Yeah, I was thinking I should post the complete patch, to make it easier for folks. I just made the patch, let me know if it works - it has a bit of extra stuff in it due to the way my kernels are compiled on the machine that I generated the patch. I think it won't affect the build, but it might cause a make error.

If it has an error, I can rebuild the patch.

I also don't have a 2.6.25 machine at the moment, and so I guessed at the format of the #if kernel version part. The simple way would be to comment out the if statement, since you are compiling for a 2.6.25 kernel, but leaving the if statement in means it will compile on 2.6.24 or 2.6.25 for vmware 1.04 or 1.05, which seemed like a nicer patch.

vmnet 2.6.25

vmmon 2.6.25

Comment #1706

2008-04-20T03:47:39Z

Were you going to include a patch [for VMware server on 2.6.25]? :)