Re: [gentoo-user] vmware server problem
On Sun, 17 Dec 2006 23:48:37 -0700, Richard Fish wrote: Since .config contains # CONFIG_BRIDGE is not set I do believe I know the cause of _this_ problem. Just to be sure, my next (newbie) question is Is bridged networking the the right option to choose? I'm not sure...I don't have that set, but also I don't use bridged networking in vmware. I used bridged networking in VMware and don't have this kernel option. You are only bridging within VMware, between the guest and host OSes, so the kernel option is not needed. -- Neil Bothwick There are two standards for anything... One for the U.S. and one for the rest of the world. signature.asc Description: PGP signature
Re: [gentoo-user] vmware server problem
On Monday 18 December 2006 06:34, David Relson wrote: Running insmod for vmmon and vmnet gets them installed and output from /etc/init.d/vmware start indicated success. However running .../vmware status immediately afterwards says vmware has stopped. Looking at dmesg I suspect the following is the key: vmware-start: Bridged networking on /dev/vmnet0 failed I've had similar weird problems like this myself. I use vmware-workstation but afaik the modules and underlying code is the same as -server. Causes I have found are: original kernel and new vmware-modules compiled with different gcc versions A LOCALVERSION was set in the kernel .config but modules were built without it - caused by copying a 2.6.17-x .config over to 2.6.18 source dir and not noticing this value was set Not applying the vmware-any-any-xxx patch (the ebuild should have taken care of this for you) If all else fails, you might have to run /etc/vmware/init.d/vmware by hand and see where it is failing. As Neil mentioned, the bridged networking in vmware has nothing to do with the host kernel. Try set up your vm to use NATing and see if you can persuade vmware to run that way. If so, this will be a further clue as to the underlying cause. Is the config of your old and new kernel different in any relevant way? Perhaps you should post the output of diff -u old kernel config new kernel config especially the networking options alan -- gentoo-user@gentoo.org mailing list
[gentoo-user] vmware server problem
I've just installed vmware-server and it doesn't start. Environment: 2.6.19-gentoo-r1 kernel on x86 vmware-modules-1.0.0.15-r1 vmware-server-1.0.1.29996-r4 vmware-server-console-1.0.1.29996-r4 When I run /etc/init.d/vmware start, the following messages appear in /var/log/messages ... rc-scripts: Vmware Server is installed, but it has not been (correctly) configured ... rc-scripts: for the running kernel. ... rc-scripts: Please ensure that the modules have been compiled for this kernel: ... rc-scripts: emerge --oneshot vmware-modules ... rc-scripts: Also ensure Vmware Server has been configured: ... rc-scripts: /opt/vmware/server/bin/vmware-config.pl ... rc-scripts: VMware is not properly configured! See above. ... modprobe: FATAL: Module vmmon not found. ... modprobe: FATAL: Module vmnet not found. ... vmware-start: Virtual machine monitor ... failed ... vmware-start: Virtual ethernet ... failed ... vmware-start: Bridged networking on /dev/vmnet0 ... failed I've run both suggested commands (several times) to no avail. Looking in /lib/modules/2.6.19-gentoo-r1 directory misc has newly built modules vmmon.ko and vmnet.ko It would seem that modprobe is looking in the wrong directory. Running strace modprobe vmmon shows a read of /lib/modules/2.6.19-gentoo-r1/ke..., which is (unfortunately) an incomplete path. Anybody know what's wrong and how to fix it? Thank you. David -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware server problem
On 12/17/06, David Relson [EMAIL PROTECTED] wrote: Looking in /lib/modules/2.6.19-gentoo-r1 directory misc has newly built modules vmmon.ko and vmnet.ko You need to make sure that /usr/src/linux points to the configured sources of your currently running kernel. Otherwise vmmon and vmnet will be built for the wrong kernel version (or wrong kernel config) and fail to load. It would seem that modprobe is looking in the wrong directory. Running strace modprobe vmmon shows a read of /lib/modules/2.6.19-gentoo-r1/ke..., which is (unfortunately) an incomplete path. Use the -s option to increase the length of the strings that strace prints before truncating them...fex: strace -s256 ... -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware server problem
On Sun, 17 Dec 2006 18:43:52 -0700 Richard Fish wrote: On 12/17/06, David Relson [EMAIL PROTECTED] wrote: Looking in /lib/modules/2.6.19-gentoo-r1 directory misc has newly built modules vmmon.ko and vmnet.ko You need to make sure that /usr/src/linux points to the configured sources of your currently running kernel. Otherwise vmmon and vmnet will be built for the wrong kernel version (or wrong kernel config) and fail to load. It would seem that modprobe is looking in the wrong directory. Running strace modprobe vmmon shows a read of /lib/modules/2.6.19-gentoo-r1/ke..., which is (unfortunately) an incomplete path. Use the -s option to increase the length of the strings that strace prints before truncating them...fex: strace -s256 ... -Richard Hi Richard, Feedback appreciated! /usr/src/linux is a symlink to the currently running kernel. The dates/times of the relevant files, i.e. /usr/src/linux/.config /etc/kernels/kernel-config-x86-2.6.19-gentoo-r1 /boot/initramfs-genkernel-x86-2.6.19-gentoo-r1 /boot/System.map-genkernel-x86-2.6.19-gentoo-r1 /boot/kernel-genkernel-x86-2.6.19-gentoo-r1 all match up. Using strace -s4096 modprobe vmmon show that file /lib/modules/2.6.19-gentoo-r1/modules.alias is being read just before the FATAL: Module vmmon not found. message is displayed. It sounds like you have a working vmware-server environment. If so, where are your copies of vmmon.ko and vmnet.ko located and are they referenced in modules.alias? Also, any additional thoughts on what I should be looking at/for to solve the modprobe issue? Thanks. David -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware server problem
On 12/17/06, David Relson [EMAIL PROTECTED] wrote: It sounds like you have a working vmware-server environment. If so, where are your copies of vmmon.ko and vmnet.ko located and are they referenced in modules.alias? Also, any additional thoughts on what I should be looking at/for to solve the modprobe issue? ~ uname -r 2.6.19-gentoo-r1 ~ find /lib/modules/ | grep -e vmmon -e vmnet /lib/modules/2.6.19-gentoo-r1/misc/vmmon.ko /lib/modules/2.6.19-gentoo-r1/misc/vmnet.ko ~ grep -e vmmon -e vmnet /lib/modules/`uname -r`/* /lib/modules/2.6.19-gentoo-r1/modules.dep:/lib/modules/2.6.19-gentoo-r1/misc/vmnet.ko: /lib/modules/2.6.19-gentoo-r1/modules.dep:/lib/modules/2.6.19-gentoo-r1/misc/vmmon.ko: /lib/modules/2.6.19-gentoo-r1/modules.symbols:alias symbol:VMX86_RegisterMonitor vmmon Try insmod'ing the drivers manually: insmod /lib/modules/`uname -r`/misc/vmmon.ko Also, the output of dmesg might hold some clue. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware server problem
On Sun, 17 Dec 2006 20:22:04 -0700 Richard Fish wrote: On 12/17/06, David Relson [EMAIL PROTECTED] wrote: It sounds like you have a working vmware-server environment. If so, where are your copies of vmmon.ko and vmnet.ko located and are they referenced in modules.alias? Also, any additional thoughts on what I should be looking at/for to solve the modprobe issue? ~ uname -r 2.6.19-gentoo-r1 ~ find /lib/modules/ | grep -e vmmon -e vmnet /lib/modules/2.6.19-gentoo-r1/misc/vmmon.ko /lib/modules/2.6.19-gentoo-r1/misc/vmnet.ko ~ grep -e vmmon -e vmnet /lib/modules/`uname -r`/* /lib/modules/2.6.19-gentoo-r1/modules.dep:/lib/modules/2.6.19-gentoo-r1/misc/vmnet.ko: /lib/modules/2.6.19-gentoo-r1/modules.dep:/lib/modules/2.6.19-gentoo-r1/misc/vmmon.ko: /lib/modules/2.6.19-gentoo-r1/modules.symbols:alias symbol:VMX86_RegisterMonitor vmmon Try insmod'ing the drivers manually: insmod /lib/modules/`uname -r`/misc/vmmon.ko Also, the output of dmesg might hold some clue. -Richard Good info! uname and find show you and I are running the same kernel and have the modules in the same places. Running insmod for vmmon and vmnet gets them installed and output from /etc/init.d/vmware start indicated success. However running .../vmware status immediately afterwards says vmware has stopped. Looking at dmesg I suspect the following is the key: vmware-start: Bridged networking on /dev/vmnet0 failed Since .config contains # CONFIG_BRIDGE is not set I do believe I know the cause of _this_ problem. Just to be sure, my next (newbie) question is Is bridged networking the the right option to choose? Thanks. David To ask a question of ignorance, does -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware server problem
On 12/17/06, David Relson [EMAIL PROTECTED] wrote: Since .config contains # CONFIG_BRIDGE is not set I do believe I know the cause of _this_ problem. Just to be sure, my next (newbie) question is Is bridged networking the the right option to choose? I'm not sure...I don't have that set, but also I don't use bridged networking in vmware. -Richard -- gentoo-user@gentoo.org mailing list
