On Sun, 2004-11-14 at 16:43 +0100, oliver frommel wrote: > > o You must upgrade the kernel modules and configuration using the > > unofficial vmware-any-any-* toolkit available from: > > [5]http://platan.vc.cvut.cz/ftp/pub/vmware/ I'm not sure why you would need that with 4.5.2 8848. Does it provide something special for different configurations of the kernel, maybe? > > o After vmware-config.pl is run and the VMware modules are loaded, the > > following command creates the /sys/class/* nodes needed for udev: > > cp -rp /dev/vm* /etc/udev/devices/ > Updating /usr/bin/vmware ... Unknown version > Sorry, there is no binary patch available for your version of /usr/bin/vmware. This error message seems to indicate there is no patch available for your version of vmware. That's been my experience. Did you try running vmware-config.pl without vmware-any-any? I required no patch to build the modules for 4.5.2 8848. And, it looks like the ./runme.pl script is trying to build the modules itself and blowing apart. Are you running vmware-config.pl at all? Here, I'll build them again and paste the output... # What OS release am I on? # cat /etc/fedora-release Fedora Core release 3 (Heidelberg) # kernel # uname -r 2.6.9-1.667 # Check the VMWare version # rpm -q VMwareWorkstation VMwareWorkstation-4.5.2-8848 # Let's be sure mine isn't patched # rpm --verify VMwareWorkstation # Now we build the modules # /usr/bin/vmware-config.pl Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitor [ OK ] Bridged networking on /dev/vmnet0 [ OK ] DHCP server on /dev/vmnet8 [ OK ] NAT service on /dev/vmnet8 [ OK ] Host-only networking on /dev/vmnet8 [ OK ] Virtual ethernet [ OK ] Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware Workstation is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.9-1.667/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.9-1.667/build/include/.. SUBDIRS=$PWD SRCROOT= $PWD/. modules make[1]: Entering directory `/lib/modules/2.6.9-1.667/build' CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-config0/vmmon-only/common/task.o CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko make[1]: Leaving directory `/lib/modules/2.6.9-1.667/build' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config0/vmmon-only' The module loads perfectly in the running kernel. This program previously created the file /dev/vmmon, and was about to remove it.Somebody else apparently did it already. Extracting the sources of the vmnet module. Building the vmnet module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmnet-only' make -C /lib/modules/2.6.9-1.667/build/include/.. SUBDIRS=$PWD SRCROOT= $PWD/. modules make[1]: Entering directory `/lib/modules/2.6.9-1.667/build' CC [M] /tmp/vmware-config0/vmnet-only/driver.o CC [M] /tmp/vmware-config0/vmnet-only/hub.o CC [M] /tmp/vmware-config0/vmnet-only/userif.o CC [M] /tmp/vmware-config0/vmnet-only/netif.o CC [M] /tmp/vmware-config0/vmnet-only/bridge.o CC [M] /tmp/vmware-config0/vmnet-only/procfs.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.ko make[1]: Leaving directory `/lib/modules/2.6.9-1.667/build' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config0/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 program 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 [ OK ] Virtual ethernet [ OK ] Bridged networking on /dev/vmnet0 [ OK ] Host-only networking on /dev/vmnet8 (background) [ OK ] NAT service on /dev/vmnet8 [ OK ] The configuration of VMware Workstation 4.5.2 build-8848 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 -- David Norris http://www.webaugur.com/dave/ ICQ - 412039
Attachment:
signature.asc
Description: This is a digitally signed message part
