VMware On SuSE 9.1
Special note: I am reorganizing/re-writing these pages. If you have found useful information here, or think that something could be expanded, please drop me an e-mail and tell me about it. It seems the most popular items are the latest SuSE's and VMware. I can't afford to purchase the new versions of VMware so I will always have the info on how to run version 3.2 on SuSE ... if it will. I will probably quit updating my versions of SuSE when my 3.2 VMware no longer works.
VMware 3.2 vs. SuSE 9.1
This is possibly my only note concerning VMware 3.2 on SuSE 9.1. From what I have seen on the Web, others are using this version of VMware on the new kernel.
Quote from a message on the Internet:
Well ... I Lied!!
When I tried to fire up VMware, even with the above "fix", it complained about not being set up correctly for the running Kernel. Makes sense. I had to configure it for all the others. I believe that I saw the kernel source getting installed during the SuSE update. So let's see what we can discover.
I also think that I forgot to mention irq_vectors.h not found error. I am only bringing this up cause I had the error when trying to install VMware in my new 9.2 version of SuSE. When I got the error I vaugely remembered having it before. Check VMware On 9.2 for ruther info.
First off, we have switched from version 2.4.21 to version 2.6.5-7.95. VMware has to have code matched to the version of Linux that it is running on. It needs vmmon and vmnet. Both of these are supplied by VMware. The sources for vmmon and vmnet are in: /usr/lib/vmware/modules/source. The sources for the Kernel are in: /usr/src/linux. So let's run the VMware config first.
dusty-tr:/usr/bin # vmware-config.pl Making sure VMware Workstation's services are stopped. Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet1 done DHCP server on /dev/vmnet8 done NAT networking on /dev/vmnet8 done Host-only networking on /dev/vmnet8 done Virtual ethernet done grep: /proc/ksyms: No such file or directory grep: /proc/ksyms: No such file or directory grep: /proc/ksyms: No such file or directory Trying to find a suitable vmmon module for your running kernel. None of VMware Workstation's pre-built vmmon modules is suitable for your running kernel. Do you want this script to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes]
Hmmmmm... a problem with /proc/ksyms. Reason?? This has been changed to
/proc/kallsyms (Refer: http://thomer.com/linux/migrate-to-2.6.html). So we need to replace all
occurrences of ``/proc/ksyms'' with ``/proc/kallsyms'' in /usr/bin/vmware-config.pl. I did and tried
Using compiler "/usr/bin/gcc". Use environment variable CC to override. Argument "gcc (GCC) 3" isn't numeric in numeric ge (>=) at /usr/bin/vmware-config.pl line 1493,Hmmmmm... it thinks I have broken sources. Interesting.
From notes on the Web, steps to build the kernel:
cd /usr/src/linux make cloneconfig make bzImage make modulesSince it is ony complaining about the .config file I am only going to do the first part, make cloneconfig. Don't belive that a full compile is neccessary.
After doing the cloneconfig executed vmware-config.pl again:
Building the vmmon module. Building for VMware Workstation 3.2.1. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config4/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make: Entering directory `/usr/src/linux-2.6.5-7.95' WARNING: Symbol version dump /usr/src/linux-2.6.5-7.95/Module.symvers is missing, modules will have CONFIG_MODVERSIONS disabled. CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o /bin/sh: line 1: scripts/genksyms/genksyms: No such file or directory make: *** [/tmp/vmware-config4/vmmon-only/linux/driver.o] Error 1 make: *** [_module_/tmp/vmware-config4/vmmon-only] Error 2 make: Leaving directory `/usr/src/linux-2.6.5-7.95' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config4/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html". Execution aborted.
Welllll... we got rid of the configuation errors only to go on to module and script errors. I believe that the last step in the compile was to make some modules. However, more reading on the Web (http://www.vmware.com/community/thread.jspa?threadID=6034&tstart=60) pointed out make prepare. I did that and ... executed vmware-config.pl again:
Building the vmmon module. Building for VMware Workstation 3.2.1. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config5/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make: Entering directory `/usr/src/linux-2.6.5-7.95' WARNING: Symbol version dump /usr/src/linux-2.6.5-7.95/Module.symvers is missing, modules will have CONFIG_MODVERSIONS disabled. CC [M] /tmp/vmware-config5/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config5/vmmon-only/linux/hostif.o CC [M] /tmp/vmware-config5/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-config5/vmmon-only/common/hash.o CC [M] /tmp/vmware-config5/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-config5/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-config5/vmmon-only/common/task.o CC [M] /tmp/vmware-config5/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-config5/vmmon-only/vmcore/compat.o CC [M] /tmp/vmware-config5/vmmon-only/vmcore/compilercheck.o CC [M] /tmp/vmware-config5/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-config5/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config5/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config5/vmmon-only/vmmon.ko make: Leaving directory `/usr/src/linux-2.6.5-7.95' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config5/vmmon-only' The module loads perfectly in the running kernel. Trying to find a suitable vmnet module for your running kernel. None of VMware Workstation's pre-built vmnet modules is suitable for your running kernel. Do you want this script to try to build the vmnet module for your system (you need to have a C compiler installed on your system)? [yes] Extracting the sources of the vmnet module. Building the vmnet module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config5/vmnet-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make: Entering directory `/usr/src/linux-2.6.5-7.95' WARNING: Symbol version dump /usr/src/linux-2.6.5-7.95/Module.symvers is missing, modules will have CONFIG_MODVERSIONS disabled. CC [M] /tmp/vmware-config5/vmnet-only/driver.o CC [M] /tmp/vmware-config5/vmnet-only/hub.o CC [M] /tmp/vmware-config5/vmnet-only/userif.o CC [M] /tmp/vmware-config5/vmnet-only/netif.o CC [M] /tmp/vmware-config5/vmnet-only/bridge.o CC [M] /tmp/vmware-config5/vmnet-only/procfs.o LD [M] /tmp/vmware-config5/vmnet-only/vmnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config5/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config5/vmnet-only/vmnet.ko make: Leaving directory `/usr/src/linux-2.6.5-7.95' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config5/vmnet-only' The module loads perfectly in the running kernel. You have already setup networking. Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes] Do you want this script to automatically configure your system to allow your Virtual Machines to access the host's filesystem? (yes/no/help) [no] Starting VMware services: Virtual machine monitor done Virtual ethernet done Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT networking on /dev/vmnet8 done The configuration of VMware Workstation 3.2.1 build-2242 for Linux for this running kernel completed successfully. You can now run VMware Workstation by invoking the following command: "/usr/bin/vmware". Enjoy, --the VMware team
Ok, I now have a working VMware without CONFIG_MODVERSIONS. Ok let's do the make modules... which takes a long time. Then execute vmware-config.pl again. Alllrighty. I got the same verbage as the last time, only this time without the "Module.symvers is missing" message. So, it appears that I will now be able to use the VMware that I had used in SuSE 9.0... hopefully. I haven't tried it yet. However, according to ps, vmnet is in operation.
root 23060 1 0 11:41 pts/3 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 23083 1 0 11:41 ? 00:00:00 /usr/bin/vmnet-natd -d /var/run/vmnet-natd-8.pid -m /var/run/vmnet-natd-8.mac -c /etc/vmware/vmnet8/nat/nat.conf root 23347 1 0 11:41 pts/3 00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1 root 23368 1 0 11:41 pts/3 00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8 root 23397 1 0 11:41 ? 00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8 root 23398 1 0 11:41 ? 00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1
Hmmmmm... even after all of the above I still can not start VMware as I used to. Perhaps I need to .. cough, choke .. re-boot? Arrggg..! Well, let's try it.
Ok now. After the reboot I am seeing all the VMware vmnets running via the ps
command. So, I am going to once again try to start it... nope! It won't go. I don't get any error messages
or any crashes ... just nothing. Hmmmmm... Ok this VMware that I have loaded was setup under SuSE 9.0
which was running Linux Kernel 2.4.21. Now, I was able to get vmnet and vmmon to install so they have
the interface or interaction to kernel 2.6. So, now let's back track and try the first item at the beginning
of this page.
This version of the Linux kernel is newer than the newest series with which VMware Workstation is supported. It may or may not work. Would you like to continue?but it works. At least it appears ok so far. I even changed the LD_ASSUME_KERNEL to 2.4.21 and it still complained. So I'll just wait and see.
One of the reasons that I want VMware is to be able to use HomeSite in editing
my WebPages. Well, the permissions did not get properly transfered in this update. I try to access my
public_html through Homesite and I am told that it is not accessible and access is denied! Arrgg!!
\\\\Dusty-tr\\pubht is not accessible.
Hmmmmmm... ok let's do something different. Think. Where is public_html? It is in my /home/ctaylor Linux directory and I have it as one of my Network Places, pubht. Two others are windrvd and windrve, which are FAT32 partions in my WinXP area representing Drive D and Drive E. So, this now appears to possibly be a Samba problem.?.?
Well, not necessarily. Using Windows Explorer I can access and log-on to all
three. In fact using Win Explorer and going to the public_html directory, I can right click on one of
my html files, select 'open with', select Homesite and it will complain about the permissions BUT it will
still open up in Homesite!! And I can modify the file and then re-save it. BUT I can not open Homesite
first and then open the file. Inside Homesite I can not even look inside the public_html directory, nor
can I look inside either WinXP drive. Hmmmm... this is getting interesting. Further checks show that I
am able to open these files from inside Dreamweaver, MS Word, GTEdit and others but not Homesite!! Arrgg!
The one I am most interested in doesn't work correctly!! Why only one application and the one I want??
Ok now, I normally fire up VMware, bring up Win Exp and log-on to pubht, windrvd and windrve. That way I am all set. This time I decided to not log-in. After VMware and Win2k came up I fired up Homesite. Since I have it set to come up in the last working folder, it tried to access pubht. The log-on dialog box was displayed and I logged on. Then it promptley said that access was denied to pubht!! Arrgg, Darn!! I changed the permissions on the public_html folder and all below it to 777 and still no dice. This is very perplexing. Now as a wild act, I gave 777 to home and ctaylor. No dice!! As another wild act I closed down everything and re-booted. Still No dice!. BUT ... see below.
Changes - In Work Habits
This portion is being written in Dreamweaver. Previous portions of this page were written using BlueFish HTML editor in Linux. Since I can't get Homesite to read the files, I guess I am going to have to change. Dreamweaver will now be my default... least till I figure out the problem with Homesite..
I spoke to soon above. Yes I was able to open and modify this WebPage with Dreamweaver but I could not save it. Access was denied. Guess I am going to be more of a Linux user than I was anticipating. .
More on Permissions...
Alrighty now... frustration is peaking. But, I remembered that Dreamweaver almost worked, at least better than Homesite, on this permission issue. So, I tried it with the 777 scenario from above. It worked and I was able to save the file ... this file with these last notes! Well, almost the last cause I can't leave my home area wide open. But, at least I know there is hope.
This is entirely frustrating and perplexing. I was concentrating on getting Homesite to work and ignoring Dreamweaver for the most part. Now I evidently have all the correct conditions to allow Dreamweaver to work and I am not sure how I got there. Just hate it when that happens!!
Now then, there is still the situation where all the dirs and files below public_html have 777. ALSO... my smb.conf got changed when I put public_html back to 755. I was using the name pubht and it put it to PUBLIC_HTML. I put it back to pubht and it worked with my VMware/Win2k... without restarting.
Oooooopppss... crossed up here. Somehow in the above two actions this file got owner and group changed to nobody and nobody. Not sure how that happend but I couldn't save the file. The permissions were also changed to 744. I renamed it and brought it up here in Bluefish and did a save-as the proper name. The default permissions came up 644.
Now with public_html at 755 and this file, VMwareOn91.html at 644 I am in Dreamweaver trying to edit and do a save... I could not. Copied this text over to Bluefish and then did the save. I then went back to Dreamweaver and opened NewSuSE-9-1.htm which has 777 perms on it. Made a change and tried to save it... no dice!! Changed public_html to 775... Nope! Changed public_html to 775... Nope! Arrrggg! Ok there is one other place, Local Net Sharing. This also changes the smb.conf file.
Conclusions .. for now. 26 Jul 04
In order to use Dreamweaver, I must have 'Shared - writeable for others' in the permissions for public_html. However, the 'regular' perms can be 755. The dirs and files under it can be 755 and do not have to have 'Shared - writeable'.
And then we have the two Windows drives. Without making any changes to them I can edit and save files in the copy of public_html that I have over there on Drive E. It does NOT have the 'Shareable - writeable for others' set.
After all this I still can not use Homesite. For some reason the permissions are not read correctly when using this application. For that matter this whole mess of permissioning is a mess! But it will have to do till I get time to figure out what went wrong and/or what is so different in this new version of SuSE 9.1.
29 July 2004 - Arrgg!! Double!!
See: NewSuSE9-1 for the first part.
24 August 2004
Well, wouldn't you know it. On August 17th I shutdown my system and left the next day for Ohio. My son was getting married. So my 'puter sat for 6 days off. I fired it up this morning and VMware won't come up!! The complaint is that "it has not been (correctly) configured for your running kernel.". Now I haven't been here to change a thing and neither has anyone else. So how does it change??? The only answer is that I was doing something before I left that changed my setup(s). BUT... what was I doing??? Wellll, I guess I start at the beginning of this file and see what I did to get it to work in the first place.
Ok, I don't want to, but for lack of anything else at the moment, I am going to execute vmware-config.pl again. I looked at the last log file for Aug 17th and there is nothing funny in it. It just records the startup and shutdown procedures. It all looked ok.
Well, vmware-config.pl failed. No .config for Linux. Made the config...Made the prepare... Made the modules. In essence the same steps I took originally...ANNNDDD... VMware now works again. Soooo... now then, am I going to have all those other problems I had?? Like with Homesite not working?? We'll see ... welst, whilst I were typing this I had VMware/Win2k comming up in the background. I heard the Windows melody at startup. That's encouraging. I was prompted for the password for the two itmes that I have mounted. My NTfiles and the Zip drive. Then the Win2k desktop appeared and it looked the same.
Alrighty now. I am in Homesite - Win2k... was using Bluefish - Linux for the above
from the last date heading to here. So we are back in business. I think. Got abslolutly no idea what went
wrong. The last that I remember doing was setting up everything for music. I got one that works in Linux
and one that works in Windows. Perhaps my configurations got changed when I made changes to use
them. Have to keep our eyes peeled.