We know that VMware doesn't (yet?) support SuSE 9.0, but we had no problem running VMware Workstation 4.0 in 9.0--until the latest 192 kernel. In the past, we used to able to update the vmware kernel modules after updating each kernel (and sources), and they would load fine. We did this by shutting down vmware and then going into the /usr/src/linux-2.4.xxx directory, run make cloneconfig and then make depp && make clean. (We already installed the km_vmware package). Next, we'd rebuild the vmware modules from the /usr/src/kernel-modules/vmware directory by rnning make -f Makefile.module and then running make -f Makefile.module install. But when we go to restart the vmware services, everything now fails to load. Any ideas? Thanks! Mark -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
Same problem here. I haven't had the time to dig deeper into it at this point, though, and suspect that there will be a work-around for it somehow. If someone has found a solution already, I'd of course appreciate hearing about it, too. Cheers, Alex. On Mon, 23 Feb 2004, L. Mark Stone wrote:
We know that VMware doesn't (yet?) support SuSE 9.0, but we had no problem running VMware Workstation 4.0 in 9.0--until the latest 192 kernel.
In the past, we used to able to update the vmware kernel modules after updating each kernel (and sources), and they would load fine.
We did this by shutting down vmware and then going into the /usr/src/linux-2.4.xxx directory, run make cloneconfig and then make depp && make clean. (We already installed the km_vmware package). Next, we'd rebuild the vmware modules from the /usr/src/kernel-modules/vmware directory by rnning make -f Makefile.module and then running make -f Makefile.module install.
But when we go to restart the vmware services, everything now fails to load.
Any ideas? Thanks! Mark
-- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107
Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Mon, 2004-02-23 at 11:33, Alex Angerhofer wrote:
Same problem here. I haven't had the time to dig deeper into it at this point, though, and suspect that there will be a work-around for it somehow. If someone has found a solution already, I'd of course appreciate hearing about it, too.
Cheers, Alex.
On Mon, 23 Feb 2004, L. Mark Stone wrote:
I am currently running the 166 kernel version with the modules supplied with the 144 kernel. Haven't installed 192 yet to see if the same works there. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Mon, 2004-02-23 at 12:07, Kenneth Schneider wrote:
I am currently running the 166 kernel version with the modules supplied with the 144 kernel. Haven't installed 192 yet to see if the same works there.
I wouldn't upgrade your kernel just yet Ken... -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
On Monday 23 February 2004 17:18, L. Mark Stone wrote:
On Mon, 2004-02-23 at 12:07, Kenneth Schneider wrote:
I am currently running the 166 kernel version with the modules supplied with the 144 kernel. Haven't installed 192 yet to see if the same works there.
I wouldn't upgrade your kernel just yet Ken...
This has been talked about before, follow the link below, there is a description of the VMware any any patch that fixes the VMware kernel module compilation to work with virtually any recent kernel version. Don't be put off by the fact it says it's for the 2.6 kernel just ignore the nvidia information at the start of the page and scroll down a bit. http://kerneltrap.org/node/view/1804 Just make sure you have the latest kernel sources installed and run "make cloneconfig" and "make dep" before you run the patch script. I have installed this on 3 machines running the latest kernel updates for SuSE 9.0, both for AMD and Intel processors, including a dual PIII machine. I also passed the details to a colleague this morning, who within minutes emailed me back to say it had worked on his SuSE 9.0 machine. -- David Bottrill Registered Linux user number 330730 www.bottrill.org
Hi Mark and everybody else who may be concerned about this. The problem is solved. vmware is now running fine on the latest suse 9.0 patch kernel, 2.4.21-192. The guilty party is the vmnet.o module. You don't want to use the one that is being supplied by the km_vmware package! Use the one that is being generated by running vmware-config.pl. However, you do want to use the vmmon.o that comes from km_vmware. I am also using vmppuser.o derived from km_vmware (I don't think it actually matters as it doesn't seem to get transplanted by the config script). That's all. Good luck, Alex. On Mon, 23 Feb 2004, Alex Angerhofer wrote:
Same problem here. I haven't had the time to dig deeper into it at this point, though, and suspect that there will be a work-around for it somehow. If someone has found a solution already, I'd of course appreciate hearing about it, too.
Cheers, Alex.
On Mon, 23 Feb 2004, L. Mark Stone wrote:
We know that VMware doesn't (yet?) support SuSE 9.0, but we had no problem running VMware Workstation 4.0 in 9.0--until the latest 192 kernel.
In the past, we used to able to update the vmware kernel modules after updating each kernel (and sources), and they would load fine.
We did this by shutting down vmware and then going into the /usr/src/linux-2.4.xxx directory, run make cloneconfig and then make depp && make clean. (We already installed the km_vmware package). Next, we'd rebuild the vmware modules from the /usr/src/kernel-modules/vmware directory by rnning make -f Makefile.module and then running make -f Makefile.module install.
But when we go to restart the vmware services, everything now fails to load.
Any ideas? Thanks! Mark
-- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107
Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Mon, 2004-02-23 at 21:08, Alex Angerhofer wrote:
Hi Mark and everybody else who may be concerned about this. The problem is solved. vmware is now running fine on the latest suse 9.0 patch kernel, 2.4.21-192. The guilty party is the vmnet.o module. You don't want to use the one that is being supplied by the km_vmware package! Use the one that is being generated by running vmware-config.pl. However, you do want to use the vmmon.o that comes from km_vmware. I am also using vmppuser.o derived from km_vmware (I don't think it actually matters as it doesn't seem to get transplanted by the config script). That's all. Good luck, Alex.
Hey Alex, You certainly got down deeper than I did! I took David Bottrill's advice and got the latest any-any patch from the VMware Patch Maintainer site at http://ftp.cvut.cz/vmware/. The -50 version I had did not work, but a -51 version was released a few days ago, and that did work. There are no instructions with the any-any update patch, but basically all I did was (not sure if all steps are truly necessary, but...): 1. Install the new kernel and kernel sources. 2. Using YaST, disable vmware services 3. Reboot. 4. As root, run: 4a. cd /usr/src/linux 4b. make cloneconfig 4c. make dep && make clean 5. Unpack the vmware-any-any-update51.tar.gz patch 6. Run as root the runme.pl script from the any-any patch. 6a. Allow the runme.pl script to overwrite the modules. 6b. Ignore any errors. 6c. Allow the runme.pl script to launch vmware-config.pl. 7. Allow vmware-config.pl to build the modules. 8. Re-enable vmware services in YaST 9. Launch VMware. Looks like going forward before I update a kernel I'm going to wait a few days to see if a new any-any update gets released first. Thanks! Mark -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com
On Tuesday 24 February 2004 12:15 pm, L. Mark Stone wrote:
Looks like going forward before I update a kernel I'm going to wait a few days to see if a new any-any update gets released first.
Thanks! Mark
Thanks David & L. Mark. Using the any-any update fixed it for me. Alex's method wouldn't work here. Stan
In message <200402241353.44190.srglasoe@comcast.net>, S.R.Glasoe
On Tuesday 24 February 2004 12:15 pm, L. Mark Stone wrote:
Looks like going forward before I update a kernel I'm going to wait a few days to see if a new any-any update gets released first.
Thanks! Mark
Thanks David & L. Mark. Using the any-any update fixed it for me. Alex's method wouldn't work here.
Stan
I used the km_vmware modules here but had to manually cd to each of the module directories under the km_vmware directory and do a make "clean ; make" before the two .o files would rebuild. If I didn't do this the vmmon.o module before executing the two "make - Makefile.module" commands vmmon.o would load but vmnet.o would fail would unresolved symbols. -- Dave Addison
participants (6)
-
Alex Angerhofer -
Dave Addison -
David Bottrill -
Kenneth Schneider -
L. Mark Stone -
S.R.Glasoe