Hi
I recently installed smxi on my linux debian laptop with there kernal
but im having trouble setting up the vm player it cant locate the there kernal
and when i find it a pop up saying
C header files matching your running kernel were not found. Refer to your distribution's documentation for installation instructions

since i installed the vm via smxi i dont know where to look for the c headers
can anybody help
Back to top

You're giving no meaningful information.

Which kernel? The vmware installer in svmi doesn't support version 3.0, I just updated that to indicate that fact a day or two ago.

If you are using a new kernel, then the vmware that smxi installs won't work no matter what, but I can't say until you provide details.

New kernels require 3.0 vmware player or later, and as svmi now says, that is only installable via direct download after filling out a vmware form and running the installer manually, that's out of svmi's hands at this point.

If you installed the kernel via smxi, it would install the kernel headers package as well, which for some odd reason debian doesn't consider a dependency of the kernel image package.

I don't remember if svmi checks the headers, maybe it doesn't, not sure.
Back to top

sorry about that
the kernel headers i have installed are 2,6.35.-6.dmz .4 liquoirix -686
Back to top

You're still giving no meaningful information, sorry.

What KERNEL are you running? What VMWARE player are you using?

vmware player 3.0 may have an issue with building the module on 2.6.35, it does on my system, that's not my fault or problem, it's a vmware issue. 2.5 does NOT work with 2.6.35,period.

vbox non ose 3.2.10 / 2.6.35-6 liquorix installs and run and builds fine, I use it.

vmware seems to build the module with one failure using its own module builder I just tried it, not sure about the svmi vmware module builder, I have seen a vsock module error not sure the status of that. But the module failure forces a recompile of the module each start, so that's useless.
Back to top

That error happens here:



Please do not mistake a vmware failure to support a specific kernel, which is common for latest kernels, with an svmi issue, there's no connection, you have to post on vmware forums for patches/fixes.

Not enough vmware/svmi users exist to warrant tracking patches any longer, it takes too much of my time, so if vmware stuff works, great, if not, fine.

vmware stopped supporting current kernels quite a while ago, some people make patches for them, and I used to track those patches, but too few users run svmi now and I stopped actively using vmware because of these ongoing support failures, so svmi vmware support isn't very good any more.

vbox-non-ose works fine for almost all normal user cases, that's what I use now, after years of vmware.
Back to top

This is a known issue, with patch/fix: www.linuxinsight.com/persuading-vmware-workstation-7.1-to-cooperate-with-linux-kernel-2.6.35.html

More on that here: www.google.com/search?q=%2Ftmp%2Fvmware-root%2Fmodules%2Fvsock-only%27+Unable+to+install+vsock&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

However, I find it absurd that a major corporation like vmware is incapable of having released their installer with the patched files, unless it's a gpl issue, but then it's a design flaw, known, and still unfixed.

So I'm not going to chase after companies that can't solve issues like this in a timely manner, I don't have the time or desire to waste my life in this way, sorry.

If stuff works, great, it will work, if not, we'll wait until it does.
Back to top