|
|
Ubuntu 64-bit Full install on VMware-fusion on Mac-OSX LeopardFrom $1Table of contentsNo headersFollow the instructions given at this location Briefly: 1) Obtain a 64bit Ubuntu iso file from the ubuntu site. Make sure you get the 64 bit Desktop version for "64bit AMD and Intel computers". The iso image is called ubuntu-8.04.1.amd64.iso ( or whatever the latest version of ubuntu is at that moment). The x86-64 platform for 64 bit computing is called AMD64 or Intel -64 , and it will work on all x86 -64 cpus 2) Install the iso from the VMware fusion site 3) Install build essentials like gcc gfortran etc sudo apt-get install build-essential 4) Now to get things like copy and paste from hopst-leopard OS to guest-Vmware-ubuntu OS to play well, you need to install VMware tools. As noted here , the menu item Virtual Machine-Install VMware tools does not work so follow these instructions:
If the configure informs you of missing packages . Please install them . For eg"configure: error: uriparser library not found or is too old. Please configure without Unity (using --disable-unity) or install the liburiparser devel package." In my case I installed the OpenVMtools with the --disable-unity and the --without-icu options ./configure --disable-unity --without-icu make
Here is a screendump of the vmware tools installation process hari@hari-virbuntu:~/Desktop/vmware-tools-distrib$ sudo ./vmware-install.pl [sudo] password for hari: A previous installation of VMware Tools has been detected. The previous installation was made by the tar installer (version 4). Keeping the tar4 installer database format. Uninstalling the tar installation of VMware Tools. Stopping VMware Tools services in the virtual machine: Guest operating system daemon: done File /etc/X11/xorg.conf is backed up to /etc/X11/xorg.conf.old.1. The removal of VMware Tools 7.6.3 build-94249 for Linux completed successfully. Thank you for having tried this software. Installing VMware Tools. In which directory do you want to install the binary files? [/usr/bin] What is the directory that contains the init directories (rc0.d/ to rc6.d/)? [/etc] What is the directory that contains the init scripts? [/etc/init.d] In which directory do you want to install the daemon files? [/usr/sbin] In which directory do you want to install the library files? [/usr/lib/vmware-tools] The path "/usr/lib/vmware-tools" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? [yes] In which directory do you want to install the documentation files? [/usr/share/doc/vmware-tools] The path "/usr/share/doc/vmware-tools" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? [yes] The installation of VMware Tools 7.6.3 build-94249 for Linux completed successfully. You can decide to remove this software from your system at any time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl". Before running VMware Tools for the first time, you need to configure it by invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want this program to invoke the command for you now? [yes] Stopping VMware Tools services in the virtual machine: Guest operating system daemon: done Trying to find a suitable vmmemctl module for your running kernel. None of the pre-built vmmemctl modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmmemctl 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.27-9-generic/build/include] Extracting the sources of the vmmemctl module. Building the vmmemctl module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmemctl-only' make -C /lib/modules/2.6.27-9-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.27-9-generic' CC [M] /tmp/vmware-config0/vmmemctl-only/backdoorGcc64.o CC [M] /tmp/vmware-config0/vmmemctl-only/os.o CC [M] /tmp/vmware-config0/vmmemctl-only/vmballoon.o CC [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-9-generic' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/tmp/vmware-config0/vmmemctl-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-config0/vmmemctl-only' cp -f vmmemctl.ko ./../vmmemctl.o make: Leaving directory `/tmp/vmware-config0/vmmemctl-only' The module loads perfectly in the running kernel. Extracting the sources of the vmhgfs module. Building the vmhgfs module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmhgfs-only' make -C /lib/modules/2.6.27-9-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.27-9-generic' CC [M] /tmp/vmware-config0/vmhgfs-only/backdoor.o CC [M] /tmp/vmware-config0/vmhgfs-only/backdoorGcc64.o CC [M] /tmp/vmware-config0/vmhgfs-only/bdhandler.o CC [M] /tmp/vmware-config0/vmhgfs-only/cpName.o CC [M] /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o CC [M] /tmp/vmware-config0/vmhgfs-only/cpNameLite.o CC [M] /tmp/vmware-config0/vmhgfs-only/dentry.o CC [M] /tmp/vmware-config0/vmhgfs-only/dir.o CC [M] /tmp/vmware-config0/vmhgfs-only/file.o CC [M] /tmp/vmware-config0/vmhgfs-only/filesystem.o CC [M] /tmp/vmware-config0/vmhgfs-only/fsutil.o CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsBd.o CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsEscape.o CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o CC [M] /tmp/vmware-config0/vmhgfs-only/inode.o CC [M] /tmp/vmware-config0/vmhgfs-only/kernelStubsLinux.o CC [M] /tmp/vmware-config0/vmhgfs-only/link.o CC [M] /tmp/vmware-config0/vmhgfs-only/messageBackdoor.o CC [M] /tmp/vmware-config0/vmhgfs-only/message.o CC [M] /tmp/vmware-config0/vmhgfs-only/module.o CC [M] /tmp/vmware-config0/vmhgfs-only/page.o CC [M] /tmp/vmware-config0/vmhgfs-only/request.o CC [M] /tmp/vmware-config0/vmhgfs-only/rpcout.o CC [M] /tmp/vmware-config0/vmhgfs-only/stubs.o CC [M] /tmp/vmware-config0/vmhgfs-only/super.o CC [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-9-generic' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/tmp/vmware-config0/vmhgfs-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-config0/vmhgfs-only' cp -f vmhgfs.ko ./../vmhgfs.o make: Leaving directory `/tmp/vmware-config0/vmhgfs-only' The module loads perfectly in the running kernel. Extracting the sources of the vmblock module. Building the vmblock module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmblock-only' make -C /lib/modules/2.6.27-9-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.27-9-generic' CC [M] /tmp/vmware-config0/vmblock-only/linux/block.o CC [M] /tmp/vmware-config0/vmblock-only/linux/control.o CC [M] /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o CC [M] /tmp/vmware-config0/vmblock-only/linux/dentry.o CC [M] /tmp/vmware-config0/vmblock-only/linux/file.o CC [M] /tmp/vmware-config0/vmblock-only/linux/filesystem.o CC [M] /tmp/vmware-config0/vmblock-only/linux/inode.o CC [M] /tmp/vmware-config0/vmblock-only/linux/module.o CC [M] /tmp/vmware-config0/vmblock-only/linux/stubs.o CC [M] /tmp/vmware-config0/vmblock-only/linux/super.o LD [M] /tmp/vmware-config0/vmblock-only/vmblock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o LD [M] /tmp/vmware-config0/vmblock-only/vmblock.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-9-generic' make -C $PWD SRCROOT=$PWD/. postbuild make[1]: Entering directory `/tmp/vmware-config0/vmblock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-config0/vmblock-only' cp -f vmblock.ko ./../vmblock.o make: Leaving directory `/tmp/vmware-config0/vmblock-only' The module loads perfectly in the running kernel. [EXPERIMENTAL] The Virtual Machine Communication Interface (VMCI) service provides a new communication capability with the Host, primarily for development at the moment. Would you like to enable this feature? [no] Detected X.org version X.Org X Server 1.5.2 Release Date: 10 October 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-16-server x86_64 Ubuntu Current Operating System: Linux hari-virbuntu 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 Build Date: 24 October 2008 09:06:49AM xorg-server 2:1.5.2-2ubuntu3 (buildd@crested.buildd) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present . No drivers for X.org version: X.Org X Server 1.5.2 Release Date: 10 October 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-16-server x86_64 Ubuntu Current Operating System: Linux hari-virbuntu 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 Build Date: 24 October 2008 09:06:49AM xorg-server 2:1.5.2-2ubuntu3 (buildd@crested.buildd) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present . Do you want to change the display size that X starts with? (yes/no) [no] Starting VMware Tools services in the virtual machine: Switching to guest configuration: done Guest filesystem driver: done Mounting HGFS shares: done Guest memory manager: done Blocking file system: done DMA setup: done Guest operating system daemon: done The configuration of VMware Tools 7.6.3 build-94249 for Linux for this running kernel completed successfully. You must restart your X session before any mouse or graphics changes take effect. You can now run VMware Tools by invoking the following command: "/usr/bin/vmware-toolbox" during an X server session. To make use of the virtual printer, you will need to restart the CUPS service If you wish to configure any experimental features, please run the following command: "vmware-config-tools.pl --experimental". Enjoy, --the VMware team
Tags:
|