Re: [gentoo-user] vmware problem
On Thu, 12 Jun 2008 01:42:50 -0400 Andrey Falko wrote: ...[snip]... Attempted to upgrade vmware-modules from 1.0.0.15-r1 to 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: emerge --oneshot vmware-modules Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 [1.0.0.15-r1] [blocks B ] =app-emulation/vmware-modules-1.0.0.16 (is blocking app-emulation/vmware-server-1.0.5.80187) You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 first...I think. Sorry, I meant vmware-modules-1.0.0.15-r1. It seems that the vmware-server ebuild only permits modules-1.0.0.15 ... Is any of this ringing any bells??? Also, reading the google translation of the German posting, it seems to say there was a conflict with dual core and vmmon and (perhaps) disabling SMP, then building vmmon, then enabling SMP gave a working module. This is a guess and I've not yet tried it. OK. I've removed all vmware builds. emerge -C vmware-modules reports --- Couldn't find 'vmware-modules' to unmerge. and 'find /var/db/pkg/ -name *vmware*' doesn't find anything. Doing a new emerge -aDtqv vmware-server brings in: [ebuild N] app-emulation/vmware-server-1.0.5.80187 [ebuild N] app-emulation/vmware-modules-1.0.0.15-r1 Then modprobe vmmon reports (as before): FATAL: Error inserting vmmon (/lib/modules/2.6.25-gentoo-r4/misc/vmmon.ko): Invalid module format with /var/log/messages saying: Jun 12 07:26:15 osage vmmon: disagrees about version of symbol struct_module I've googled the above message and found this thread (from last night) and another thread in which the running kernel version didn't match the installed version of linux-headers. I've running the 2.6.25-gentoo-r4 kernel and have the same versions of linux-headers and gentoo-sources installed. Looking for more ideas as to what's wrong :- Regards, David -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Thu, Jun 12, 2008 at 7:41 AM, David Relson [EMAIL PROTECTED] wrote: On Thu, 12 Jun 2008 01:42:50 -0400 Andrey Falko wrote: ...[snip]... Attempted to upgrade vmware-modules from 1.0.0.15-r1 to 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: emerge --oneshot vmware-modules Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 [1.0.0.15-r1] [blocks B ] =app-emulation/vmware-modules-1.0.0.16 (is blocking app-emulation/vmware-server-1.0.5.80187) You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 first...I think. Sorry, I meant vmware-modules-1.0.0.15-r1. It seems that the vmware-server ebuild only permits modules-1.0.0.15 ... Is any of this ringing any bells??? Also, reading the google translation of the German posting, it seems to say there was a conflict with dual core and vmmon and (perhaps) disabling SMP, then building vmmon, then enabling SMP gave a working module. This is a guess and I've not yet tried it. OK. I've removed all vmware builds. emerge -C vmware-modules reports --- Couldn't find 'vmware-modules' to unmerge. and 'find /var/db/pkg/ -name *vmware*' doesn't find anything. Doing a new emerge -aDtqv vmware-server brings in: [ebuild N] app-emulation/vmware-server-1.0.5.80187 [ebuild N] app-emulation/vmware-modules-1.0.0.15-r1 Then modprobe vmmon reports (as before): FATAL: Error inserting vmmon (/lib/modules/2.6.25-gentoo-r4/misc/vmmon.ko): Invalid module format with /var/log/messages saying: Jun 12 07:26:15 osage vmmon: disagrees about version of symbol struct_module I've googled the above message and found this thread (from last night) and another thread in which the running kernel version didn't match the installed version of linux-headers. I've running the 2.6.25-gentoo-r4 kernel and have the same versions of linux-headers and gentoo-sources installed. Looking for more ideas as to what's wrong :- Regards, David -- gentoo-user@lists.gentoo.org mailing list Opps, it was my mistake. I have 1.0.0.17 installed with ~x86 workstation, server. According to vmware-server ebuild, only 1.0.0.15 will work with the latest vmware-server. I'd file a bug in bugs.gentoo.org that vmware-server does not work for you with 2.6.25. As a work around, try to use 2.6.24 kernel or earlier. Sorry for my blunder. -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Thu, Jun 12, 2008 at 5:51 AM, Andrey Falko [EMAIL PROTECTED] wrote: On Thu, Jun 12, 2008 at 7:41 AM, David Relson [EMAIL PROTECTED] wrote: On Thu, 12 Jun 2008 01:42:50 -0400 Andrey Falko wrote: ...[snip]... Attempted to upgrade vmware-modules from 1.0.0.15-r1 to 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: emerge --oneshot vmware-modules Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 [1.0.0.15-r1] [blocks B ] =app-emulation/vmware-modules-1.0.0.16 (is blocking app-emulation/vmware-server-1.0.5.80187) You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 first...I think. Sorry, I meant vmware-modules-1.0.0.15-r1. It seems that the vmware-server ebuild only permits modules-1.0.0.15 ... Is any of this ringing any bells??? Also, reading the google translation of the German posting, it seems to say there was a conflict with dual core and vmmon and (perhaps) disabling SMP, then building vmmon, then enabling SMP gave a working module. This is a guess and I've not yet tried it. OK. I've removed all vmware builds. emerge -C vmware-modules reports --- Couldn't find 'vmware-modules' to unmerge. and 'find /var/db/pkg/ -name *vmware*' doesn't find anything. Doing a new emerge -aDtqv vmware-server brings in: [ebuild N] app-emulation/vmware-server-1.0.5.80187 [ebuild N] app-emulation/vmware-modules-1.0.0.15-r1 Then modprobe vmmon reports (as before): FATAL: Error inserting vmmon (/lib/modules/2.6.25-gentoo-r4/misc/vmmon.ko): Invalid module format with /var/log/messages saying: Jun 12 07:26:15 osage vmmon: disagrees about version of symbol struct_module I've googled the above message and found this thread (from last night) and another thread in which the running kernel version didn't match the installed version of linux-headers. I've running the 2.6.25-gentoo-r4 kernel and have the same versions of linux-headers and gentoo-sources installed. Looking for more ideas as to what's wrong :- Regards, David -- gentoo-user@lists.gentoo.org mailing list Opps, it was my mistake. I have 1.0.0.17 installed with ~x86 workstation, server. According to vmware-server ebuild, only 1.0.0.15 will work with the latest vmware-server. I'd file a bug in bugs.gentoo.org that vmware-server does not work for you with 2.6.25. As a work around, try to use 2.6.24 kernel or earlier. Sorry for my blunder. -- gentoo-user@lists.gentoo.org mailing list I have been watching this thread and wondering why my vmware keeps working. Then I noticed that all the 2.6.25 kernels are ~x86. If I were you I'd check if they're ~arch for you too, and if so it might be best to go back to stable versions of both vmware and the kernel. -- Kevin O'Gorman, PhD
Re: [gentoo-user] vmware problem
David - at this point I'd try a couple of things. Since you've upgraded your linux-headers, it's a good idea to recompile your system libc, as per the elog message. Also, since you're getting version error messages, recompile your kernel and reboot into it. Just to make sure, as you've just done headers and libc (may be a long shot, but may as well rule it out). Then unload all vm* modules and recompile them also. (Say no to all vmware-config questions first, then second time around say yes!). If it doesn't work, downgrade to a previous version of modules and try them. I use vmware-modules-1.0.0.11-r1 because that's the only version that works with workstation 4, which I have a license for. Finally, if this all still fails, try with an earlier kernel and see if it magically works. Then you know it's probably a new kernal feature thats bugging you! I hope you have a few spare clock cycles for all this compiling :) HTH, -- Iain Buchanan iaindb at netspace dot net dot au The state law of Pennsylvania prohibits singing in the bathtub. -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Fri, 13 Jun 2008 09:23:51 +0930 Iain Buchanan wrote: David - at this point I'd try a couple of things. Since you've upgraded your linux-headers, it's a good idea to recompile your system libc, as per the elog message. Also, since you're getting version error messages, recompile your kernel and reboot into it. Just to make sure, as you've just done headers and libc (may be a long shot, but may as well rule it out). Then unload all vm* modules and recompile them also. (Say no to all vmware-config questions first, then second time around say yes!). If it doesn't work, downgrade to a previous version of modules and try them. I use vmware-modules-1.0.0.11-r1 because that's the only version that works with workstation 4, which I have a license for. Finally, if this all still fails, try with an earlier kernel and see if it magically works. Then you know it's probably a new kernal feature thats bugging you! I hope you have a few spare clock cycles for all this compiling :) Hi Iain, I've been using 'uname -r' and its reporting '2.6.25-gentoo-r4' matches the module path, i.e. /lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko, in the invalid module message. I'm as certain as can be that there's no mismatch here. Also, I've removed all vm* packages and reinstalled vmware-server (and whatever it pulls in, i.e. vmware-modules). This was done after removing all vmware entries from /etc/portage/package*, so the vm* packages are all stable versions -- no ~amd64 versions. Haven't tried rebuilding glibc ... Instead I've installed the latest stable amd64 versions of 2.6.24 sources and headers. The kernel is now being built. I should know before too long whether this helps. Another possibility not yet tried is to disable CONFIG_MODVERSIONS. That's it for now... Regards, David -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Thu, 2008-06-12 at 21:16 -0400, David Relson wrote: On Fri, 13 Jun 2008 09:23:51 +0930 Iain Buchanan wrote: David - at this point I'd try a couple of things. Since you've upgraded your linux-headers, it's a good idea to recompile your system libc, as per the elog message. Also, since you're getting version error messages, recompile your kernel and reboot into it. Just to make sure, as you've just done headers and libc (may be a long shot, but may as well rule it out). Then unload all vm* modules and recompile them also. (Say no to all vmware-config questions first, then second time around say yes!). If it doesn't work, downgrade to a previous version of modules and try them. I use vmware-modules-1.0.0.11-r1 because that's the only version that works with workstation 4, which I have a license for. Finally, if this all still fails, try with an earlier kernel and see if it magically works. Then you know it's probably a new kernal feature thats bugging you! I hope you have a few spare clock cycles for all this compiling :) Hi Iain, I've been using 'uname -r' and its reporting '2.6.25-gentoo-r4' matches the module path, i.e. /lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko, in the invalid module message. I'm as certain as can be that there's no mismatch here. don't be so sure! Do you know that you won't get the same message if, for example, you used different compilers for the kernel and the module? In my experience, this message can appear when the actual kernel number is ok, but it's been compiled differently... Also, I've removed all vm* packages and reinstalled vmware-server (and whatever it pulls in, i.e. vmware-modules). This was done after removing all vmware entries from /etc/portage/package*, so the vm* packages are all stable versions -- no ~amd64 versions. Haven't tried rebuilding glibc ... Instead I've installed the latest stable amd64 versions of 2.6.24 sources and headers. The kernel is now being built. I should know before too long whether this helps. good! Let's see what happens... Another possibility not yet tried is to disable CONFIG_MODVERSIONS. That's it for now... Regards, David -- Iain Buchanan iaindb at netspace dot net dot au Let me assure you that to us here at First National, you're not just a number. Youre two numbers, a dash, three more numbers, another dash and another number. -- James Estes -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] vmware problem
Greetings, I've got vmware-server installed on my AMD64x2 workstation with kernel 2.6.25-gentoo-r4. It used to work fine with kernel 2.6.22-gentoo-r9. My current versions are: vmware-server: 1.0.5.80187 vmware-modules: 1.0.0.15-r1 Today vmware won't start up. It's complaining: vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /opt/vmware/server/bin/vmware-config.pl. I've run vmware-config.pl and accepted the default answers to all questions -- the same thing I've done several times over the past year. The run ends with the following messages: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Module vmnet is not loaded. Please verify that it is loaded before [ !! ] * running this script. [ !! ] The configuration of VMware Server 1.0.5 build-80187 for Linux for this running kernel completed successfully. Given the module vmnet message, I've run emerge --oneshot vmware-modules and verified that /lib/modules/2.6.25-gentoo-r4/misc has new versions of vmmon.ko and vmnet.ko. When I run modprobe vmnet, it reports: FATAL: Error inserting vmnet (/lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko): Invalid module format What detail am I missing about building vmnet.ko ?? Thanks. David -- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Wed, Jun 11, 2008 at 8:12 PM, David Relson [EMAIL PROTECTED] wrote: Greetings, I've got vmware-server installed on my AMD64x2 workstation with kernel 2.6.25-gentoo-r4. It used to work fine with kernel 2.6.22-gentoo-r9. My current versions are: vmware-server: 1.0.5.80187 vmware-modules: 1.0.0.15-r1 Today vmware won't start up. It's complaining: vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /opt/vmware/server/bin/vmware-config.pl. I've run vmware-config.pl and accepted the default answers to all questions -- the same thing I've done several times over the past year. The run ends with the following messages: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Module vmnet is not loaded. Please verify that it is loaded before [ !! ] * running this script. [ !! ] The configuration of VMware Server 1.0.5 build-80187 for Linux for this running kernel completed successfully. Given the module vmnet message, I've run emerge --oneshot vmware-modules and verified that /lib/modules/2.6.25-gentoo-r4/misc has new versions of vmmon.ko and vmnet.ko. When I run modprobe vmnet, it reports: FATAL: Error inserting vmnet (/lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko): Invalid module format What detail am I missing about building vmnet.ko ?? Thanks. David -- David Relson Osage Software Systems, Inc. [EMAIL PROTECTED] Ann Arbor, MI 48103 www.osagesoftware.com -- gentoo-user@lists.gentoo.org mailing list I have a hunch that vmware-modules-1.0.0.17 is too old for kernel-2.6.25. See what happens if you do: modprobe --force vmnet Perhaps you reconfigured something with your kernel that throws it off. I can't read German too well, I think this guy got it working my fixing his kernel config: http://www.gentooforum.de/artikel/11913/gel-st-problem-nach-vmware-update.html -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
Hi, On Wed, 2008-06-11 at 20:12 -0400, David Relson wrote: Greetings, I've got vmware-server installed on my AMD64x2 workstation with kernel 2.6.25-gentoo-r4. It used to work fine with kernel 2.6.22-gentoo-r9. My current versions are: vmware-server: 1.0.5.80187 vmware-modules: 1.0.0.15-r1 Today vmware won't start up. It's complaining: vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /opt/vmware/server/bin/vmware-config.pl. I've run vmware-config.pl and accepted the default answers to all questions -- the same thing I've done several times over the past year. The run ends with the following messages: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Module vmnet is not loaded. Please verify that it is loaded before [ !! ] * running this script. [ !! ] The configuration of VMware Server 1.0.5 build-80187 for Linux for this running kernel completed successfully. Given the module vmnet message, I've run emerge --oneshot vmware-modules and verified that /lib/modules/2.6.25-gentoo-r4/misc has new versions of vmmon.ko and vmnet.ko. When I run modprobe vmnet, it reports: FATAL: Error inserting vmnet (/lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko): Invalid module format What detail am I missing about building vmnet.ko ?? I have various vmware module problems, and there are a number of tweaks I try when I get to a brick wall: sometimes just `rm /etc/vmware/not_configured` is enough, but given you can't load it manually, maybe not! try both: /etc/init.d/vmware stop /etc/vmware/init.d/vmware stop and make sure all vm* modules are unloaded. run vmware-config, but say no to everthing. Then start start the vmware init.d service, see if it works. (don't run vmware). stop vmware, run vmware-config again, and then add in your options. Start the vmware service again... and cross your fingers :) There might also be some useful messages in dmesg, or syslog (can't remember where they go) about why the module isn't loading - perhaps there's a deprecated kernel option you have to compile in? HTH, -- Iain Buchanan iaindb at netspace dot net dot au Genius may have its limitations, but stupidity is not thus handicapped. -- Elbert Hubbard -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Thu, 12 Jun 2008 11:45:46 +0930 Iain Buchanan wrote: Hi, On Wed, 2008-06-11 at 20:12 -0400, David Relson wrote: Greetings, I've got vmware-server installed on my AMD64x2 workstation with kernel 2.6.25-gentoo-r4. It used to work fine with kernel 2.6.22-gentoo-r9. My current versions are: vmware-server: 1.0.5.80187 vmware-modules: 1.0.0.15-r1 Today vmware won't start up. It's complaining: vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /opt/vmware/server/bin/vmware-config.pl. I've run vmware-config.pl and accepted the default answers to all questions -- the same thing I've done several times over the past year. The run ends with the following messages: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Module vmnet is not loaded. Please verify that it is loaded before [ !! ] * running this script. [ !! ] The configuration of VMware Server 1.0.5 build-80187 for Linux for this running kernel completed successfully. Given the module vmnet message, I've run emerge --oneshot vmware-modules and verified that /lib/modules/2.6.25-gentoo-r4/misc has new versions of vmmon.ko and vmnet.ko. When I run modprobe vmnet, it reports: FATAL: Error inserting vmnet (/lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko): Invalid module format What detail am I missing about building vmnet.ko ?? I have various vmware module problems, and there are a number of tweaks I try when I get to a brick wall: sometimes just `rm /etc/vmware/not_configured` is enough, but given you can't load it manually, maybe not! try both: /etc/init.d/vmware stop /etc/vmware/init.d/vmware stop and make sure all vm* modules are unloaded. run vmware-config, but say no to everthing. Then start start the vmware init.d service, see if it works. (don't run vmware). stop vmware, run vmware-config again, and then add in your options. Start the vmware service again... and cross your fingers :) There might also be some useful messages in dmesg, or syslog (can't remember where they go) about why the module isn't loading - perhaps there's a deprecated kernel option you have to compile in? /var/log/messages says: vmnet: disagrees about version of symbol struct_module So I upgraded linux-headers from 2.6.23-r3 to 2.6.25-r4, then emerged vmware-modules again, ran modprobe vmnet, and (again) got the above message Attempted to upgrade vmware-modules from 1.0.0.15-r1 to 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: emerge --oneshot vmware-modules Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 [1.0.0.15-r1] [blocks B ] =app-emulation/vmware-modules-1.0.0.16 (is blocking app-emulation/vmware-server-1.0.5.80187) It seems that the vmware-server ebuild only permits modules-1.0.0.15 ... Is any of this ringing any bells??? Also, reading the google translation of the German posting, it seems to say there was a conflict with dual core and vmmon and (perhaps) disabling SMP, then building vmmon, then enabling SMP gave a working module. This is a guess and I've not yet tried it. Regards, David -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Wed, Jun 11, 2008 at 11:57 PM, David Relson [EMAIL PROTECTED] wrote: On Thu, 12 Jun 2008 11:45:46 +0930 Iain Buchanan wrote: Hi, On Wed, 2008-06-11 at 20:12 -0400, David Relson wrote: Greetings, I've got vmware-server installed on my AMD64x2 workstation with kernel 2.6.25-gentoo-r4. It used to work fine with kernel 2.6.22-gentoo-r9. My current versions are: vmware-server: 1.0.5.80187 vmware-modules: 1.0.0.15-r1 Today vmware won't start up. It's complaining: vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /opt/vmware/server/bin/vmware-config.pl. I've run vmware-config.pl and accepted the default answers to all questions -- the same thing I've done several times over the past year. The run ends with the following messages: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Module vmnet is not loaded. Please verify that it is loaded before [ !! ] * running this script. [ !! ] The configuration of VMware Server 1.0.5 build-80187 for Linux for this running kernel completed successfully. Given the module vmnet message, I've run emerge --oneshot vmware-modules and verified that /lib/modules/2.6.25-gentoo-r4/misc has new versions of vmmon.ko and vmnet.ko. When I run modprobe vmnet, it reports: FATAL: Error inserting vmnet (/lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko): Invalid module format What detail am I missing about building vmnet.ko ?? I have various vmware module problems, and there are a number of tweaks I try when I get to a brick wall: sometimes just `rm /etc/vmware/not_configured` is enough, but given you can't load it manually, maybe not! try both: /etc/init.d/vmware stop /etc/vmware/init.d/vmware stop and make sure all vm* modules are unloaded. run vmware-config, but say no to everthing. Then start start the vmware init.d service, see if it works. (don't run vmware). stop vmware, run vmware-config again, and then add in your options. Start the vmware service again... and cross your fingers :) There might also be some useful messages in dmesg, or syslog (can't remember where they go) about why the module isn't loading - perhaps there's a deprecated kernel option you have to compile in? /var/log/messages says: vmnet: disagrees about version of symbol struct_module So I upgraded linux-headers from 2.6.23-r3 to 2.6.25-r4, then emerged vmware-modules again, ran modprobe vmnet, and (again) got the above message Attempted to upgrade vmware-modules from 1.0.0.15-r1 to 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: emerge --oneshot vmware-modules Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 [1.0.0.15-r1] [blocks B ] =app-emulation/vmware-modules-1.0.0.16 (is blocking app-emulation/vmware-server-1.0.5.80187) You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 first...I think. It seems that the vmware-server ebuild only permits modules-1.0.0.15 ... Is any of this ringing any bells??? Also, reading the google translation of the German posting, it seems to say there was a conflict with dual core and vmmon and (perhaps) disabling SMP, then building vmmon, then enabling SMP gave a working module. This is a guess and I've not yet tried it. Regards, David -- gentoo-user@lists.gentoo.org mailing list -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] vmware problem
On Thu, Jun 12, 2008 at 1:41 AM, Andrey Falko [EMAIL PROTECTED] wrote: On Wed, Jun 11, 2008 at 11:57 PM, David Relson [EMAIL PROTECTED] wrote: On Thu, 12 Jun 2008 11:45:46 +0930 Iain Buchanan wrote: Hi, On Wed, 2008-06-11 at 20:12 -0400, David Relson wrote: Greetings, I've got vmware-server installed on my AMD64x2 workstation with kernel 2.6.25-gentoo-r4. It used to work fine with kernel 2.6.22-gentoo-r9. My current versions are: vmware-server: 1.0.5.80187 vmware-modules: 1.0.0.15-r1 Today vmware won't start up. It's complaining: vmware is installed, but it has not been (correctly) configured for this system. To (re-)configure it, invoke the following command: /opt/vmware/server/bin/vmware-config.pl. I've run vmware-config.pl and accepted the default answers to all questions -- the same thing I've done several times over the past year. The run ends with the following messages: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Module vmnet is not loaded. Please verify that it is loaded before [ !! ] * running this script. [ !! ] The configuration of VMware Server 1.0.5 build-80187 for Linux for this running kernel completed successfully. Given the module vmnet message, I've run emerge --oneshot vmware-modules and verified that /lib/modules/2.6.25-gentoo-r4/misc has new versions of vmmon.ko and vmnet.ko. When I run modprobe vmnet, it reports: FATAL: Error inserting vmnet (/lib/modules/2.6.25-gentoo-r4/misc/vmnet.ko): Invalid module format What detail am I missing about building vmnet.ko ?? I have various vmware module problems, and there are a number of tweaks I try when I get to a brick wall: sometimes just `rm /etc/vmware/not_configured` is enough, but given you can't load it manually, maybe not! try both: /etc/init.d/vmware stop /etc/vmware/init.d/vmware stop and make sure all vm* modules are unloaded. run vmware-config, but say no to everthing. Then start start the vmware init.d service, see if it works. (don't run vmware). stop vmware, run vmware-config again, and then add in your options. Start the vmware service again... and cross your fingers :) There might also be some useful messages in dmesg, or syslog (can't remember where they go) about why the module isn't loading - perhaps there's a deprecated kernel option you have to compile in? /var/log/messages says: vmnet: disagrees about version of symbol struct_module So I upgraded linux-headers from 2.6.23-r3 to 2.6.25-r4, then emerged vmware-modules again, ran modprobe vmnet, and (again) got the above message Attempted to upgrade vmware-modules from 1.0.0.15-r1 to 1.0.0.17-r1 and found it blocked by vmware-server-1.0.5.80187: emerge --oneshot vmware-modules Calculating dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.17-r1 [1.0.0.15-r1] [blocks B ] =app-emulation/vmware-modules-1.0.0.16 (is blocking app-emulation/vmware-server-1.0.5.80187) You need to emerge -C =app-emulation/vmware-modules-1.0.0.16 first...I think. Sorry, I meant vmware-modules-1.0.0.15-r1. It seems that the vmware-server ebuild only permits modules-1.0.0.15 ... Is any of this ringing any bells??? Also, reading the google translation of the German posting, it seems to say there was a conflict with dual core and vmmon and (perhaps) disabling SMP, then building vmmon, then enabling SMP gave a working module. This is a guess and I've not yet tried it. Regards, David -- gentoo-user@lists.gentoo.org mailing list -- gentoo-user@lists.gentoo.org mailing list
