I have a problem with my SLED11SP3 box and VMware player 5.0.4. The installation procedure ended fine with no errors, but when I start the VMware Player software the “Vmware Kernel Module updater” stop with this error:
"kernel headers for version 3.0.101-0.35-pae was not found"
Is there anybody who knows where can I find and how to install them?
I have a problem with my SLED11SP3 box and VMware player 5.0.4. The installation procedure ended fine with no errors, but when I start the VMware Player software the “Vmware Kernel Module updater” stop with this error:
"kernel headers for version 3.0.101-0.35-pae was not found"
Is there anybody who knows where can I find and how to install them?
[/QUOTE]
Install the packages linux-kernel-headers and kernel-source. (The description for the linux-kernel-headers package says 'Â compiling external kernel modules requires kernel-source instead.")
in my SLED11SP3 box already there are installed the linux-kernel-headers (version 2.6.32-1.15.1) and the kernel source (version 3.0.101-0.35.1) but my system run with “3.0.101-0.35-pae” kernel release. Most probably VMwarePlayer want the kernel-headers version 3.0.101-0.35-pae and kernel source 3.0.101-0.35-pae but I don’t know where download them…
It’s just occurred to me that given your mention of pae suggests you’re using 32bit SLED, is that correct? All my SLED 11 SP3 installs are 64bit. There’s free and not-free Pro versions of VMware Player and I don’t know which you’re using. Can you try VMware Player 6?
You are right, i’m using the 32bit SLDE11SP3,and my VMware Player version is the free version. Is vmware player 6 free too?[/QUOTE]
The free version of VMware Player 6 is free, the Pro version isn’t The free version of 6 can be downloaded from the same place as the free version of 5. Just change the ‘Major Version’ drop down selector.
[QUOTE=mauriB;24231]I have downloaded and installed it but the modules compilation failed. In the vmware-modconfig-23989.log there are these errors:
2014-10-17T14:07:35.727+01:00| vthread-3| I120: Building module with command “/usr/bin/make -j4 -C /tmp/modconfig-ilN85D/vmmon-only auto-build HEADER_DIR=/lib/modules/3.0.101-0.35-pae/build/include CC=/usr/bin/gcc-4.3 IS_GCC_3=no”
2014-10-17T14:07:36.442+01:00| vthread-3| W110: Failed to build vmmon. Failed to execute the build command.
2014-10-17T14:07:36.443+01:00| vthread-3| I120: Setting destination path for vmnet to “/lib/modules/3.0.101-0.35-pae/misc/vmnet.ko”.
[etc]
[/QUOTE]
I just installed the free version of VMware Player 6 (VMware-Player-6.0.3-1895310.x86_64.bundle) and it ‘just worked’. I can’t locate any vmware-modconfig log files.
Rather unhelpful that the log doesn’t contain anything more informative than ‘Failed to execute the build command’. Do you have /usr/bin/make ? I’m guessing you do since it’s mentioned in the log and similarly I’m guessing you do have gcc since /usr/bin/gcc-4.3 is mentioned. DO the /tmp/modconfig- files mentioned in the log still exist? If so what happens when you run one of the commands in the log that apparently couldn’t be executed manually?
For future reference, when pasting output of commands or contents of log files it helps with readability to wrap it in CODE tags. Look for the # button on the toolbar when composing.
I checked again the “vmware-modconfig-23989.log” and before the errors I posted, there are also these errors… Can them be of some help?
2014-10-17T14:07:35.430+01:00| vthread-3| I120: Invoking modinfo on "vmmon".
2014-10-17T14:07:35.432+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2014-10-17T14:07:35.432+01:00| vthread-3| I120: Invoking modinfo on "vmnet".
2014-10-17T14:07:35.437+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2014-10-17T14:07:35.437+01:00| vthread-3| I120: Invoking modinfo on "vmci".
2014-10-17T14:07:35.439+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2014-10-17T14:07:35.439+01:00| vthread-3| I120: Invoking modinfo on "vsock".
2014-10-17T14:07:35.444+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
P.S. I can’t find the # botton on the toolbar, so i added the code tags manually. I hope i’m not wrong
Doesn’t mean anything to me I’m afraid. You’re using version 6 yes? Assuming yes then all I can suggest is the rather drastic solution of switching to 64bit SLED, or assuming you’re not tied to VMware Player specifically and just want something that lets you play with virtual machines, try VirtualBox. https://www.virtualbox.org/wiki/Linux_Downloads The SLES 11 version works so long as the kernel-source package is installed. Of course, I’ve only tried on 64bit SLED.
[QUOTE=mauriB;24252]
P.S. I can’t find the # botton on the toolbar, so i added the code tags manually. I hope i’m not wrong[/QUOTE]
Come to think of it, it only shows up after you click ‘Go Advanced’. Which I always do.
Before delete all the system and switch to 64 version I would like change the kernel release. As you now I have the 3.0.101-0.35-pae and it is an extension for addressing more than 4 Gbyte of RAM. But I have only 4Gbyte so I don’t need it, therefore I woul try to downgrade the kernel at the 3.0.101-0.35-default.
Before delete all the system and switch to 64 version I would like change the kernel release. As you now I have the 3.0.101-0.35-pae and it is an extension for addressing more than 4 Gbyte of RAM. But I have only 4Gbyte so I don’t need it, therefore I woul try to downgrade the kernel at the 3.0.101-0.35-default.
Have you any idea how to do this?
[/QUOTE]
As far as I recall you just install the kernel-default package. You’ll still get kernel-pae as the default boot option but you can select kernel-default during boot and try it out. If it does what you hope then you can set it as the default boot option (YaST > System > Bootloader). You might not have 4GB of memory available with kernel-default.
I have installed the kernel-default package and boot with the new kernel but still the error exist; and also the VirtualBox doesn’t work (it’s unable to compile and load the modules). It very strange that the both packages does’t work and have the same errors… I don’t understand where I’m wrong
Most probably I will install the 64 bit version, but I don’t know if this will change the result…
That all looks very odd. In the output of ‘zypper verify’ a bunch of SLES repos have been added but not enabled. I’ve no idea why. The output of ‘zypper lr’ shows a single SLED repo, which points at the DVD drive. So before you ran ‘zypper verify’ you had no SLED repos other than one pointing at the DVD drive yet I know you have installed updates because your first post says you’re running kernel 3.0.101-0.35 which is the latest version for SLED 11 SP3. Given that there’s no SLED Updates repo I wonder where did the updates come from?
Then when you’ve run ‘zypper lu’ all the SLES repos have been removed and SLED repos added. Again, I’ve no idea why.
Given your repos now appear to have completely changed, what does the output of these commands look like now look like now?