VMware Machine Configuration

This was originally written to describe how to manually reconfigure the VMware on our lab machines.  That is no longer necessary - just use image "d:\apps\vmware\vms\linux_4".  I'm leaving the information here, though, in case it helps anyone with a personal copy of VMware.

You will need to reconfigure the VMware machine (if someone hasn't already done so on the machine you're on).

• Under no conditions should you touch the Ethernet Adapters settings.
• Start VMware and pick the usual vm configuration
• Before hitting Power On, check to see if there is a second IDE disk.  If there is, you can be reasonably confident that the system is ready to go, and can skip the rest of this step.  (Do read the bold-faced item at the bottom, though, so you'll be aware of the symptom of an incorrectly established VMware machine.)
  • Settings menu, then Configuration Editor
  • Click on IDE Drives
  • If there is something at IDE 0:1, you're done (someone else has done it already)
  • If not, click on IDE 0:1 and create a drive using the right-hand panel.
  • Choose "non-persistent"
  • Pick a random size between 200MB and 500MB
• If you like, add a little memory: Memory, then increase to 128MB
• You also have to change the default boot kernel on the existing hard drive.  To do this, temporarily change disk IDE 0:0 to "persistent" (using Settings/Configuration Editor).
• Hit "Save" to exit the configuration editor
• Power On the machine and login
• Now you need to install the new, clean bootable kernel you created with "make bzImage" above:
  • Take the bzImage you created in the previous step and copy it to /boot/bzImage-proj4 on the VMware hard drive
  • Edit /etc/lilo.conf, as in previous assignments, to make /boot/bzImage-proj4 the default boot image.
  • Run /sbin/lilo
  • "shutdown -h now"
• Power Off the machine.  You'll be asked if you want to save the contents of the file corresponding to the main VMware machine disk (something like Linux_2.dsk).  Say yes.
• Select the Settings/Configuration Editor menu, select IDE 0:0, and put it back to "non-persistent".  Hit "Save".
• That's it.  (This all needs to be done only once for each installation of VMware.)
• NOTE: You will get many "unresolved symbol" errors when you try the insmod command below if the kernel booted by the VMware machine is not a new kernel compiled on the same machine as the one you've used to compile the file system module (i.e., to make cse451fs.o).