VMwareTools 2.x インストール手順(Linux) のバックアップ(No.1)
- バックアップ一覧
- 差分 を表示
- 現在との差分 を表示
- ソース を表示
- VMwareTools 2.x インストール手順(Linux) へ行く。
- 1 (2008-10-15 (水) 01:47:05)
- 2 (2008-10-15 (水) 14:16:38)
rpm -ivh VMwareTools-2.0.0-116503.i386.rpm Preparing... ########################################### [100%]
1:VMwareTools ########################################### [100%]
The installation of VMware Tools 2.0.0 for Linux completed successfully. You can decide to remove this software from your system at any time by invoking the following command: "rpm -e VMwareTools".
Before running VMware Tools for the first time, you need to configure it for your running kernel by invoking the following command: "/usr/bin/vmware-config-tools.pl".
Enjoy,
--the VMware team
[root@hydra src]# /usr/bin/vmware-config-tools.pl
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [ OK ]
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.9-VM/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.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vmmemctl-only/backdoorGcc32.o CC [M] /tmp/vmware-config0/vmmemctl-only/os.o CC [M] /tmp/vmware-config0/vmmemctl-only/vmballoon.o LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o LD [M] /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmmemctl.ko ./../vmmemctl.o make: Leaving directory `/tmp/vmware-config0/vmmemctl-only' The vmmemctl module loads perfectly into the running kernel.
None of the pre-built vmhgfs modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmhgfs module for your system (you need to have a C compiler installed on your system)? [yes] yes
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.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vmhgfs-only/backdoor.o CC [M] /tmp/vmware-config0/vmhgfs-only/backdoorGcc32.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/hgfsEscapeLinux.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/message.o CC [M] /tmp/vmware-config0/vmhgfs-only/messageBackdoor.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/staticEscape.o CC [M] /tmp/vmware-config0/vmhgfs-only/stubs.o CC [M] /tmp/vmware-config0/vmhgfs-only/super.o LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmhgfs.ko ./../vmhgfs.o make: Leaving directory `/tmp/vmware-config0/vmhgfs-only' The vmhgfs module loads perfectly into the running kernel.
None of the pre-built vmxnet modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmxnet module for your system (you need to have a C compiler installed on your system)? [yes] yes
Extracting the sources of the vmxnet module.
Building the vmxnet module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmxnet-only' make -C /lib/modules/2.6.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vmxnet-only/vmxnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o LD [M] /tmp/vmware-config0/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmxnet.ko ./../vmxnet.o make: Leaving directory `/tmp/vmware-config0/vmxnet-only' The vmxnet module loads perfectly into the running kernel.
None of the pre-built vmblock modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmblock module for your system (you need to have a C compiler installed on your system)? [yes] yes
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.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
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 CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o LD [M] /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmblock.ko ./../vmblock.o make: Leaving directory `/tmp/vmware-config0/vmblock-only' The vmblock module loads perfectly into the running kernel.
[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that creates backups of virtual machines. Please refer to the VMware Knowledge Base for more details on this capability. Do you wish to enable this feature? [no] yes
None of the pre-built vmsync modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmsync module for your system (you need to have a C compiler installed on your system)? [yes] yes
Extracting the sources of the vmsync module.
Building the vmsync module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmsync-only' make -C /lib/modules/2.6.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vmsync-only/sync.o LD [M] /tmp/vmware-config0/vmsync-only/vmsync.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmsync-only/vmsync.mod.o LD [M] /tmp/vmware-config0/vmsync-only/vmsync.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmsync.ko ./../vmsync.o make: Leaving directory `/tmp/vmware-config0/vmsync-only' The vmsync module loads perfectly into the running kernel.
[EXPERIMENTAL] The VMware CPU Time Accounting daemon (vmware-vmdesched) can help increase the accuracy of CPU time accounting performed by the guest operating system. Please refer to the VMware Knowledge Base for more details on this capability. Do you wish to enable this feature? [no] yes
None of the pre-built vmdesched modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmdesched module for your system (you need to have a C compiler installed on your system)? [yes] yes
Extracting the sources of the vmdesched module.
Building the vmdesched module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmdesched-only' make -C /lib/modules/2.6.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vmdesched-only/kernelStubsLinux.o CC [M] /tmp/vmware-config0/vmdesched-only/os.o SHIPPED /tmp/vmware-config0/vmdesched-only/vmdesched_core.o LD [M] /tmp/vmware-config0/vmdesched-only/vmdesched.o Building modules, stage 2. MODPOST
Warning: could not find /tmp/vmware-config0/vmdesched-only/.vmdesched_core.o.cmd for /tmp/vmware-config0/vmdesched-only/vmdesched_core.o
CC /tmp/vmware-config0/vmdesched-only/vmdesched.mod.o LD [M] /tmp/vmware-config0/vmdesched-only/vmdesched.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmdesched.ko ./../vmdesched.o make: Leaving directory `/tmp/vmware-config0/vmdesched-only' The vmdesched module loads perfectly into the running kernel.
None of the pre-built vmci modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vmci module for your system (you need to have a C compiler installed on your system)? [yes] yes
Extracting the sources of the vmci module.
Building the vmci module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmci-only' make -C /lib/modules/2.6.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vmci-only/kernelStubsLinux.o CC [M] /tmp/vmware-config0/vmci-only/vmciDatagram.o CC [M] /tmp/vmware-config0/vmci-only/vmciEvent.o CC [M] /tmp/vmware-config0/vmci-only/vmciGuestDs.o CC [M] /tmp/vmware-config0/vmci-only/vmciGuestKernelIf.o CC [M] /tmp/vmware-config0/vmci-only/vmciKernelIf.o CC [M] /tmp/vmware-config0/vmci-only/vmciProcess.o CC [M] /tmp/vmware-config0/vmci-only/vmciQueuePair.o CC [M] /tmp/vmware-config0/vmci-only/vmciUtil.o CC [M] /tmp/vmware-config0/vmci-only/vmci_drv.o LD [M] /tmp/vmware-config0/vmci-only/vmci.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmci-only/vmci.mod.o LD [M] /tmp/vmware-config0/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vmci.ko ./../vmci.o make: Leaving directory `/tmp/vmware-config0/vmci-only' The vmci module loads perfectly into the running kernel.
None of the pre-built vsock modules for VMware Tools is suitable for your running kernel. Do you want this program to try to build the vsock module for your system (you need to have a C compiler installed on your system)? [yes] yes
Extracting the sources of the vsock module.
Building the vsock module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vsock-only' make -C /lib/modules/2.6.9-VM/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /tmp/vmware-config0/vsock-only/linux/af_vsock.o CC [M] /tmp/vmware-config0/vsock-only/linux/driverLog.o CC [M] /tmp/vmware-config0/vsock-only/linux/util.o CC [M] /tmp/vmware-config0/vsock-only/linux/vsockAddr.o LD [M] /tmp/vmware-config0/vsock-only/vsock.o Building modules, stage 2. MODPOST
Warning: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIEvent_Subscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIMemcpyFromQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIQueuePair_Detach" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIQueuePair_Alloc" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIEvent_Unsubscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
Warning: "VMCIMemcpyToQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined! †
CC /tmp/vmware-config0/vsock-only/vsock.mod.o LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9' cp -f vsock.ko ./../vsock.o make: Leaving directory `/tmp/vmware-config0/vsock-only' The vsock module loads perfectly into the running kernel.
Detected X.org version 6.8.
Please choose one of the following display sizes that X will start with (1 - 29):
[1] "320x200" [2] "320x240" [3] "400x300" [4] "512x384" [5] "640x400" [6] "640x480" [7] "720x480" [8] "800x480" [9] "854x480" [10] "720x576" [11] "800x600" [12] "1024x768" [13] "1280x720" [14] "1280x768" [15] "1152x864" [16] "1280x800" [17] "1366x768" [18] "1280x960" [19] "1440x900" [20] "1280x1024" [21] "1400x1050" [22] "1680x1050" [23] "1600x1200" [24] "1920x1080" [25] "1920x1200" [26] "1920x1440" [27] "2048x1536" [28] "2560x1600" [29] "2560x1920" Please enter a number between 1 and 29:
[3] 6
X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.6.9-42.0.3.ELsmp i686 [ELF] Current Operating System: Linux hydra.asabiya.net 2.6.9-VM #2 Sat Oct 11 14:19:38 JST 2008 i686 Build Date: 17 November 2007 Build Host: builder6
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present OS Kernel: Linux version 2.6.9-VM (root@hydra.asabiya.net) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-9)) #2 Sat Oct 11 14:19:38 JST 2008 PF Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/vmware-config0/XF86ConfigLog.3844", Time: Wed Oct 15 00:02:24 2008 (++) Using config file: "/tmp/vmware-config0/XF86Config.3844"
X is running fine with the new config file.
Could not init font path element unix/:7100, removing from list!
Fatal server error: could not open default font 'fixed'
Please consult the The X.Org Foundation support
at http://wiki.X.Org for help.
Please also check the log file at "/tmp/vmware-config0/XF86ConfigLog.3844" for additional information.
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [ OK ] Guest filesystem driver: [ OK ] Mounting HGFS shares: [失敗] Guest memory manager: [ OK ] Guest vmxnet fast network device: [ OK ] Loading vmdesched driver module: [ OK ] Guest descheduled time accounting daemon: [ OK ] VM communication interface: [ OK ] VM communication interface socket family: [ OK ] Blocking file system: [ OK ] File system sync driver: [ OK ] Guest operating system daemon: [ OK ]
The configuration of VMware Tools 2.0.0 build-116503 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.
You will need to either manually start /usr/bin/vmware-user or log out and log back in to this desktop session to obtain the following features: guest resolution fit, drag and drop, and file and text copy/paste. vmware-user is configured to automatically start at a graphical login, but that won't take effect until the next login.
To use the vmxnet driver, restart networking using the following commands: /etc/init.d/network stop rmmod pcnet32 rmmod vmxnet modprobe vmxnet /etc/init.d/network start
Enjoy,
- the VMware team
