vmware-modules-1.0.0.15-r2 works fine with vmware-server-1.0.8.126538, but not with vmware-workstation-5.5.7.91707. With workstation, the services won't start. I tried to configure several times and to restart services and to remove /etc/vmware/not_configured. Either no services start or at least the "Bridged networking on /dev/vmnet0" does not start. I had workstation-5.5.7 working properly with vmware-modules-1.0.0.15-r1 on kernel 2.6.25.
First off, please could you include the out put of emerge --info, as you're always asked to when filing a bug. It's always handy to have. 5:) Secondly, my guess is that the init script/kernel isn't automatically loading the modules. Please could you attach the output of dmesg after attempting to configure vmware. Afterwards, could you try modprobing the various vmware modules (vmblock, vmmon, vmnet) and removing not_configured, and let me know the output of /etc/init.d/vmware. Thanks...
My guess in fact is that this has been fixed in vmware-workstation-5.5.9 (which by the way *should* be the stable one, since all the others are hit by security bug 245941), so also *after* all those other things (just so we can make sure it's the bug I think it is) please try upgrading to vmware-workstation-5.5.9. Thanks... 5:)
Created attachment 178085 [details] emerge --info
dmesg shows nothing after running vmware-config.pl. Then, I did: # modprobe vmblock # modprobe vmmon # modprobe vmnet # rm /etc/vmware/not_configured # /etc/init.d/vmware start * WARNING: vmware has already been started. # /etc/init.d/vmware restart * Stopping VMware services: [ ok ] * Virtual machine monitor [ ok ] * Bridged networking on /dev/vmnet0 [ ok ] * Virtual ethernet [ ok ] * Loading vmblock for drag and drop support ... [ ok ] * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ]
Thanks thomas, So, it looks as though the vmware services were started without problem (since you had to stop them and they stopped fine). Could you please paste the output from running vmware-config.pl (specifically the end where it tries to start the services)... Also, can I ask whether that's with vmware-workstation-5.5.7 or vmware-workstation-5.5.9?
Output from dmesg after manuelly loading the modules: Symbol init_mm is marked as UNUSED, however this module is using it. This symbol will go away in the future. Please evalute if this is the right api to use and if it really is, submit a report the linux kernel mailinglist together with submitting your code for inclusion. [23733]: VMCI: Driver initialized. [23733]: Module vmmon: registered with major=10 minor=165 [23733]: Module vmmon: initialized proc_dir_entry '/proc/vmnet' already registered Pid: 23738, comm: modprobe Tainted: P 2.6.27-gentoo-r7 #1 [<c019479d>] [<c01948fc>] [<f935ce41>] [<f935ce67>] [<f93596f2>] [<c010111f>] [<c013cc97>] [<c010382d>] ======================= [23836]: Module vmmon: unloaded parport_pc 00:0a: disabled IT8716 SuperIO detected. parport_pc 00:0a: activated parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Running config, still with 5.5.7: linux ~ # vmware-config.pl Making sure services for VMware Workstation are stopped. * Stopping VMware services: [ ok ] * Virtual machine monitor [ ok ] * Bridged networking on /dev/vmnet0 [ ok ] * Virtual ethernet [ ok ] Configuring fallback GTK+ 2.4 libraries. You have already setup networking. Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes] * Loading vmblock for drag and drop support ... [ ok ] * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] The configuration of VMware Workstation 5.5.7 build-91707 for Linux for this running kernel completed successfully. You can now run VMware Workstation by invoking the following command: "/opt/vmware/workstation/bin/vmware". Enjoy, --the VMware team
Ok, cool. That suggests there's some kind of conflict between the module you're trying to load and the module already in the kernel, so can you please run rmmod on vmblock, vmmon and vmnet. If your kernel doesn't support module unloading, then you'll need to reboot. Then re-run the config.pl and please paste the output again. Thanks... 5:)
Hmm, there should be no conflict. Because I was running vmware-server 1.x with the *same* vmware-modules as I try now with vmware-workstation. # rmmod vmblock # rmmod vmmon ERROR: Module vmmon does not exist in /proc/modules # rmmod vmnet ERROR: Module vmnet does not exist in /proc/modules # vmware-config.pl Making sure services for VMware Workstation are stopped. * WARNING: vmware has not yet been started. Configuring fallback GTK+ 2.4 libraries. You have already setup networking. Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes] * Loading vmblock for drag and drop support ... [ ok ] * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] The configuration of VMware Workstation 5.5.7 build-91707 for Linux for this running kernel completed successfully. You can now run VMware Workstation by invoking the following command: "/opt/vmware/workstation/bin/vmware". Enjoy, --the VMware team
After reboot: # vmware-config.pl Making sure services for VMware Workstation are stopped. * WARNING: vmware has not yet been started. Configuring fallback GTK+ 2.4 libraries. This program previously created the file /dev/vmnet0, and was about to remove it. Somebody else apparently did it already. You have already setup networking. Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes] * Loading vmblock for drag and drop support ... [ ok ] * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] The configuration of VMware Workstation 5.5.7 build-91707 for Linux for this running kernel completed successfully. You can now run VMware Workstation by invoking the following command: "/opt/vmware/workstation/bin/vmware". Enjoy, --the VMware team
Ok, that's *very* odd then. Could you rmmod all the modules again, and then try modprobing them and see if there's any errors, and please post what dmesg says afterwards. Since you've said these are the same modules as you had been using for vmware-server, they should modprobe fine. After that, we can try changing /etc/vmware/init.d/vmware from using "modprobe -f" to "modprobe" which may solve the problem (and, as I say, has been fixed in vmware-workstation-5.5.9)...
I cannot rmmod vmblock: # /etc/init.d/vmware stop * Stopping VMware services: [ ok ] * Virtual machine monitor [ ok ] * Bridged networking on /dev/vmnet0 [ ok ] * Virtual ethernet [ ok ] # rmmod vmblock ERROR: Module vmblock is in use
Ok, you can rmmod after you umount the directory that vmblock mounts. It should be somewhere under /proc, you can find it by running just plain mount...
# modprobe vmblock # modprobe vmmon # modprobe vmnet dmesg: Symbol init_mm is marked as UNUSED, however this module is using it. This symbol will go away in the future. Please evalute if this is the right api to use and if it really is, submit a report the linux kernel mailinglist together with submitting your code for inclusion. [15377]: VMCI: Driver initialized. [15377]: Module vmmon: registered with major=10 minor=165 [15377]: Module vmmon: initialized
Ok, so the modules load up fine. Could you rmmod them, then try modprobing them with -f to force them. This is how the vmware init script from 5.5.7 loads them, and my guess is that this will cause the error messages you were seeing in dmesg...
# modprobe -f vmblock FATAL: Error inserting vmblock (/lib/modules/2.6.27-gentoo-r7/misc/vmblock.ko): Invalid module format # modprobe -f vmmon FATAL: Error inserting vmmon (/lib/modules/2.6.27-gentoo-r7/misc/vmmon.ko): Invalid module format # modprobe -f vmnet FATAL: Error inserting vmnet (/lib/modules/2.6.27-gentoo-r7/misc/vmnet.ko): Invalid module format dmesg: proc_dir_entry '/proc/vmnet' already registered Pid: 15743, comm: modprobe Tainted: P 2.6.27-gentoo-r7 #1 [<c019479d>] [<c01948fc>] [<f9356e41>] [<f9356e67>] [<f93536f2>] [<c010111f>] [<c013cc97>] [<c010382d>] ======================= /dev/vmnet: open called by PID 15753 (vmnet-bridge) /dev/vmnet: hub 0 does not exist, allocating memory. /dev/vmnet: port on hub 0 successfully opened bridge-eth0: enabling the bridge bridge-eth0: up bridge-eth0: already up bridge-eth0: attached [15828]: Module vmmon: unloaded parport_pc 00:0a: disabled bridge-eth0: down bridge-eth0: detached Then, I removed -f from /etc/init.d/vmware like this: vmware_load_module() { /sbin/modprobe -s "$1" || exit 1 exit 0 } And now it works! Thanks!
No problem, this has already been fixed in vmware-workstation-5.5.9, so I'll mark this as fixed once that's gone stable...
vmware-workstation-5.5.9 is now stable, so I'm marking this as FIXED.
