Fedora 8 on VMware Fusion

Fedora8_BW122 Along with Ubuntu and Mandriva I recently installed a Fedora 8 virtual machine under VMware Fusion. I’m installing Fedora 8 on VMware Fusion 1.1 which is running on my 13″ MacBook.

The VMware Wizard runs just as it did for Ubuntu and Mandriva so you can see the screen shots in those posts. The only difference was in the choice of guest OS. I picked Redhat as the Linux to install since Fedora itself wasn’t a choice.

Once the Fedora 8 ISO image I was using booted the Fedora install kicked off. Unlike my previous installs I chose to install all the available options, which were: Office & Productivity, Software Development, and Web Server. The screen shots from the Fedora install are below. Click the thumbnail for the full size image.

FedoraInstall-1 FedoraInstall-2 FedoraInstall-3 FedoraInstall-4 FedoraInstall-5 FedoraInstall-6 FedoraInstall-7 FedoraInstall-8 FedoraInstall-8a FedoraInstall-9 FedoraInstall-10 FedoraInstall-11 FedoraInstall-12 FedoraInstall-13 FedoraInstall-14 FedoraInstall-15 FedoraInstall-16

Then I installed the VMware tools from the RPM package which generated a security warning,

FedoraInstall-17 FedoraInstall-18

After installing the software from the RPM package it’s necessary to configure the VMware Tools by running vmware-config-tools.pl as root. Like Mandriva, the configuration didn’t recognize the kernel. But this time when I said I wanted to build the kernel it let me. No doubt because I had installed the software development tools. When answering the questions in the script I accepted all the defaults and didn’t have a problem. At the end of the config script there are instructions on how to restart networking. The following commands need to be run from terminal before the network could be used:

/etc/init.d/network stop

rmmod pcnet32

rmmod vmxnet

modprobe vmxnet

/etc/init.d/network start

After this everything worked fine and the VMware tools could be invoked with the command /usr/bin/vmware-toolbox from terminal. Some options, such as shrinking a disk are only available when run a root.

This entry was posted in Linux and tagged , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

5 Comments

  1. ianf
    Posted January 4, 2008 at 5:30 pm | Permalink

    Many thanks,all works on my MacBook with your help,though the rmmod pcnet32

    rmmod vmxnet

    modprobe vmxnet
    did not work?

  2. ianf
    Posted January 4, 2008 at 5:51 pm | Permalink

    I chose ‘Other Linux’ Kernel 2.6 xx 64 bit’

  3. robrob
    Posted April 17, 2008 at 4:51 am | Permalink

    I followed your instructions but I can’t seem to get screen autofit/resize to work. Drag and drop also does not work.

    Does autofit/resize and drag-and-drop work for you?

  4. ray
    Posted April 17, 2008 at 8:09 pm | Permalink

    @robrob
    Autofit doesn’t work if I drag the vmware window itself to be larger or smaller. If I go into Fedora settings and change the resolution then the vmware window resizes itself. Prior to VMware tools the vmware window would stay the same size and add scroll bars or a black border.

    Not exactly sure where you mean for drag/drop. It works fine within Fedora for me. If I create a shared folder (I usually don’t use them with Linux) I could also drag from it to a Fedora directory from within Fedora. The permissions it mounts with by default don’t let me write to it even though I told vmware not to make it read-only. No drag/drop between OS X and Fedora but I didn’t expect that to work.

  5. Posted November 24, 2008 at 9:52 pm | Permalink

    The reason the auto-resize and drag and drop functions do not work very well is because vmware is mainly configured around virtualizing Windows… at least the version for the macintosh is.

    Parallels is the same way. For some reason, Windows seems to be the main os that emulators wrap them selves around best.

    I hope that helps explain it a little.

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*