vmware and SuSE-8.0
What a nice product, but what it's very picky about the kernel versions. Can someone explain why vmware-3.2 works with kernel 2.4.18-53, but not with kernel 2.4.18-253 (SuSE-8.0). In the later case vmware complains that the vmnet.o is not right and it wants to create by building it. So I decided to download the latest available kernel-source rpm... This is release 2.4.18-135... and as vmware is very picky about the right sources, it did not accept that the sources (...-135) differ from the binaries (..-235). Any glues, how to deal with this? -- Richard Bos Without a home the journey is endless
What a nice product, but what it's very picky about the kernel versions.
Can someone explain why vmware-3.2 works with kernel 2.4.18-53, but not with kernel 2.4.18-253 (SuSE-8.0). In the later case vmware complains
vmnet.o is not right and it wants to create by building it. So I decided to download the latest available kernel-source rpm... This is release 2.4.18-135... and as vmware is very picky about the right
I'm not sure I quite understand... but anyway. If you have a non-standard kernel then VMWare will recompile itself to match the kernel. You need to have the same header files as the kernel that you are running. VMWare looks for the kernal id that you are running (say 2.4.18-4GB in a standard SuSE) and then looks for the headers in /lib/modules/2.4.18-4GB/build/include, which is a symlink to the source tree ( ->/usr/src/linux-2.4.18-4GB ) which is where it picks up the necessaries. I've just (today) setup VMWare-3.2 and it worked without a hitch. Well, almost... there were a few tweaks needed. HTH, jalal Richard Bos wrote: that the sources,
it did not accept that the sources (...-135) differ from the binaries (..-235).
Any glues, how to deal with this?
On Friday 20 September 2002 5:12 pm, Richard Bos wrote:
What a nice product, but what it's very picky about the kernel versions.
Can someone explain why vmware-3.2 works with kernel 2.4.18-53, but not with kernel 2.4.18-253 (SuSE-8.0). In the later case vmware complains that the vmnet.o is not right and it wants to create by building it. So I decided to download the latest available kernel-source rpm... This is release 2.4.18-135... and as vmware is very picky about the right sources, it did not accept that the sources (...-135) differ from the binaries (..-235).
Any glues, how to deal with this?
I have found that I need to install the official kernel sources from kernel.org to make things like VMware or my company's VPN software to work. This is one reason why I wish vendors wouldn't modify the kernel, or, at least give me the option at installation or upgrade time to use a vendor modified kernel or the official kernel. -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org
On Friday 20 September 2002 23.12, Richard Bos wrote:
What a nice product, but what it's very picky about the kernel versions.
Can someone explain why vmware-3.2 works with kernel 2.4.18-53, but not with kernel 2.4.18-253 (SuSE-8.0). In the later case vmware complains that the vmnet.o is not right and it wants to create by building it. So I decided to download the latest available kernel-source rpm... This is release 2.4.18-135... and as vmware is very picky about the right sources, it did not accept that the sources (...-135) differ from the binaries (..-235).
Any glues, how to deal with this?
1. When you compile kernel modules it is important that you have the same sources installed that was used to build the kernel. This is regardless of where you get the kernel. If you build a module against different sources it could be that it uses features that was added or removed, and that could potentially cause the kernel to crash 2. I doubt that vmware complains that SuSE's build numbers for the rpms differ. They are *never* identical between kernel-source.rpm and k_*.rpm, so if vmware was sensitive to that it couldn't build on any installation. I think you could get by with cd /usr/src/linux make mrproper make cloneconfig make dep Assuming nothing drastic has been patched between the kernel you use and the kernel-source.rpm you downloaded, that should give you a source tree configured to match your running kernel. //Anders
participants (4)
-
Anders Johansson -
Andy Stewart -
jalal -
Richard Bos