いつものようにログインアカウント配下のDownloadsディレクトリにコピーして、解凍する。
あとは以下のようにコマンドをたたくだけ。
./vmware-install.pl
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.
You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version. Do you wish to continue?
(yes/no) [yes]
Uninstalling the tar installation of VMware Tools.
Stopping services for VMware Tools
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface: done
File system sync driver: done
This program previously created the file
/usr/lib/vmware-tools/lib64/libconf/etc/pango/pango.modules, and was about to
remove it. Somebody else apparently did it already.
File /etc/vmware-tools/vmware-user.desktop is backed up to
/etc/vmware-tools/vmware-user.desktop.old.0.
File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules is backed up
to /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules.old.0.
File /usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf is backed up to
/usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf.old.0.
File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders is
backed up to
/usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders.old.0.
This program previously created the file
/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gdk-pixbuf.loaders, and was about to
remove it. Somebody else apparently did it already.
This program previously created the file
/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangorc, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file
/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gtk.immodules, and was about to
remove it. Somebody else apparently did it already.
This program previously created the file
/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangox.aliases, and was about to
remove it. Somebody else apparently did it already.
This program previously created the directory
/usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0, and was about to remove it.
Since there are files in that directory that this program did not create, it
will not be removed.
This program previously created the directory
/usr/lib/vmware-tools/lib64/libconf/etc/fonts, and was about to remove it.
Since there are files in that directory that this program did not create, it
will not be removed.
This program previously created the directory
/usr/lib/vmware-tools/lib64/libconf/etc, and was about to remove it. Since
there are files in that directory that this program did not create, it will not
be removed.
This program previously created the directory
/usr/lib/vmware-tools/lib64/libconf, and was about to remove it. Since there
are files in that directory that this program did not create, it will not be
removed.
This program previously created the directory /usr/lib/vmware-tools/lib64, and
was about to remove it. Since there are files in that directory that this
program did not create, it will not be removed.
This program previously created the directory /usr/lib/vmware-tools, and was
about to remove it. Since there are files in that directory that this program
did not create, it will not be removed.
File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.0.
Kernel image: /boot/vmlinuz-3.1.0-1.2-default
Initrd image: /boot/initrd-3.1.0-1.2-default
Root device: UUID=01fb678c-d712-469e-894c-ebe8430d65a3 (/dev/sda3) (mounted on / as btrfs)
Resume device: /dev/sda2
Kernel Modules: thermal_sys thermal processor fan scsi_transport_sas mptbase mptscsih mptsas ata_generic zlib_deflate btrfs
Features: acpi block resume.userspace resume.kernel
The removal of VMware Tools 8.6.0 build-425873 for Linux completed
successfully.
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/init.d]
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]
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 8.6.0 build-425873 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]
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface: done
File system sync driver: done
[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]
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.1.0-1.2-default/build/include".
The path "/lib/modules/3.1.0-1.2-default/build/include" appears to be a valid
path to the 3.1.0-1.2-default kernel headers.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.1.0-1.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
CC [M] /tmp/vmware-root/modules/vmci-only/vmciProcess.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciNotifications.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciUtil.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmci_drv.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.1.0-1.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
CC [M] /tmp/vmware-root/modules/vmci-only/vmciProcess.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciNotifications.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestDs.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciUtil.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmci_drv.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/vmciGuestKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/kernelStubsLinux.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.1.0-1.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:105:28: fatal error: linux/smp_lock.h: No such file or directory
compilation terminated.
make[4]: *** [/tmp/vmware-root/modules/vsock-only/linux/af_vsock.o] Error 1
make[3]: *** [_module_/tmp/vmware-root/modules/vsock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
make: *** [vsock.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host. The rest of this software provided by VMware Tools is designed to work
independently of this feature. If you wish to have the VSOCK feature you can
install the driver by running vmware-config-tools.pl again after making sure
that gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution's
installation CD.
[ Press the Enter key to continue.]
The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer. Use the flag
--clobber-kernel-modules=vmxnet3 to override.
The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer. Use the flag
--clobber-kernel-modules=pvscsi to override.
The module vmmemctl has already been installed on this system by another
installer or package and will not be modified by this installer. Use the flag
--clobber-kernel-modules=vmmemctl to override.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make -C /lib/modules/3.1.0-1.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
CC [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
In file included from /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:36:0:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:186:0: warning: "alloc_netdev" redefined [enabled by default]
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:2438:0: note: this is the location of the previous definition
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:187:0: warning: "alloc_etherdev" redefined [enabled by default]
/usr/src/linux-3.1.0-1.2/include/linux/etherdevice.h:53:0: note: this is the location of the previous definition
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:208:1: error: conflicting types for ‘netif_start_queue’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:1804:20: note: previous definition of ‘netif_start_queue’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: In function ‘netif_start_queue’:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:210:21: error: ‘struct device’ has no member named ‘tbusy’
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: At top level:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:214:1: error: conflicting types for ‘netif_stop_queue’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:1869:20: note: previous definition of ‘netif_stop_queue’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: In function ‘netif_stop_queue’:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:216:19: error: ‘struct device’ has no member named ‘tbusy’
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: At top level:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:220:1: error: conflicting types for ‘netif_queue_stopped’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:1895:19: note: previous definition of ‘netif_queue_stopped’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: In function ‘netif_queue_stopped’:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:222:11: error: ‘struct device’ has no member named ‘tbusy’
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:222:11: error: ‘struct device’ has no member named ‘tbusy’
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: At top level:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:226:1: error: conflicting types for ‘netif_wake_queue’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:1838:20: note: previous definition of ‘netif_wake_queue’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: In function ‘netif_wake_queue’:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:228:21: error: ‘struct device’ has no member named ‘tbusy’
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:229:4: error: implicit declaration of function ‘mark_bh’ [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:229:12: error: ‘NET_BH’ undeclared (first use in this function)
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:229:12: note: each undeclared identifier is reported only once for each function it appears in
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: At top level:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:233:1: error: conflicting types for ‘netif_running’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:1911:19: note: previous definition of ‘netif_running’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: In function ‘netif_running’:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:235:14: error: ‘struct device’ has no member named ‘start’
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h: At top level:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:239:1: error: conflicting types for ‘netif_carrier_ok’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:2145:19: note: previous definition of ‘netif_carrier_ok’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:245:1: error: conflicting types for ‘netif_carrier_on’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:2154:13: note: previous declaration of ‘netif_carrier_on’ was here
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:250:1: error: conflicting types for ‘netif_carrier_off’
/usr/src/linux-3.1.0-1.2/include/linux/netdevice.h:2156:13: note: previous declaration of ‘netif_carrier_off’ was here
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_get_settings’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:307:4: warning: passing argument 1 of ‘netif_carrier_ok’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:239:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_get_drvinfo’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:338:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_set_tx_csum’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:424:35: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_set_tso’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:488:35: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_tx_timeout’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:817:4: warning: passing argument 1 of ‘netif_wake_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:226:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_link_check’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:843:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:849:4: warning: passing argument 1 of ‘netif_carrier_ok’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:239:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:851:10: warning: passing argument 1 of ‘netif_carrier_on’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:245:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:853:10: warning: passing argument 1 of ‘netif_carrier_off’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:250:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_probe_device’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1086:4: error: implicit declaration of function ‘alloc_etherdev’ [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1086:8: warning: assignment makes pointer from integer without a cast [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1092:9: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1106:7: error: ‘struct net_device’ has no member named ‘open’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1107:7: error: ‘struct net_device’ has no member named ‘hard_start_xmit’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1108:7: error: ‘struct net_device’ has no member named ‘stop’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1109:7: error: ‘struct net_device’ has no member named ‘get_stats’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1110:7: error: ‘struct net_device’ has no member named ‘set_multicast_list’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1115:7: error: ‘struct net_device’ has no member named ‘tx_timeout’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1118:7: error: ‘struct net_device’ has no member named ‘poll_controller’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1121:7: error: ‘struct net_device’ has no member named ‘set_mac_address’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_probe_features’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1251:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_remove_device’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1526:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_suspend_device’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1621:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_resume_device’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1666:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_init_ring’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1737:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_open’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1865:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:1902:4: warning: passing argument 1 of ‘netif_start_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:208:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘check_tx_queue’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2126:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2165:7: warning: passing argument 1 of ‘netif_queue_stopped’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:220:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2166:10: warning: passing argument 1 of ‘netif_wake_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:226:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_tx’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2197:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2245:10: warning: passing argument 1 of ‘netif_stop_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:214:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2375:10: warning: passing argument 1 of ‘netif_stop_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:214:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_rx’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2605:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_interrupt’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2735:9: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2758:4: warning: passing argument 1 of ‘netif_queue_stopped’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:220:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2759:7: warning: passing argument 1 of ‘netif_wake_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:226:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_close’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2819:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2831:4: warning: passing argument 1 of ‘netif_stop_queue’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:214:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_load_multicast’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2913:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_set_multicast_list’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2983:32: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_set_mac_address’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:3040:4: warning: passing argument 1 of ‘netif_running’ from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:233:1: note: expected ‘struct device *’ but argument is of type ‘struct net_device *’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_get_stats’:
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c:3070:25: error: ‘struct net_device’ has no member named ‘priv’
/tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘netif_queue_stopped’:
/tmp/vmware-root/modules/vmxnet-only/./shared/compat_netdevice.h:223:1: warning: control reaches end of non-void function [-Wreturn-type]
cc1: some warnings being treated as errors
make[4]: *** [/tmp/vmware-root/modules/vmxnet-only/vmxnet.o] Error 1
make[3]: *** [_module_/tmp/vmware-root/modules/vmxnet-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
make: *** [vmxnet.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,
make and the kernel sources for your running kernel are installed on your
machine. These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.1.0-1.2-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: error: unknown field ‘get_sb’ specified in initializer
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: warning: initialization makes integer from pointer without a cast [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: warning: (near initialization for ‘fsType.fs_flags’) [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: error: initializer element is not computable at load time
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: error: (near initialization for ‘fsType.fs_flags’)
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ‘Iget’:
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:339:4: error: implicit declaration of function ‘path_lookup’ [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ‘FsOpGetSb’:
/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:563:4: error: implicit declaration of function ‘get_sb_nodev’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1
make[3]: *** [_module_/tmp/vmware-root/modules/vmblock-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-3.1.0-1.2-obj/x86_64/default'
make: *** [vmblock.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
The vmblock module enables dragging or copying files from within a host and
dropping or pasting them onto your guest (host to guest drag and drop and file
copy/paste). The rest of the software provided by VMware Tools is designed to
work independently of this feature (including guest to host drag and drop and
file copy/paste).
If you would like the host to guest drag and drop and file copy/paste features,
you can install the driver by running vmware-config-tools.pl again after making
sure that gcc, binutils, make and the kernel sources for your running kernel
are installed on your machine. These packages are available on your
distribution's installation CD.
[ Press Enter key to continue ]
Disabling timer-based audio scheduling in pulseaudio.
Detected X server version 1.10.4
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Creating a new initrd boot image for the kernel.
Kernel image: /boot/vmlinuz-3.1.0-1.2-default
Initrd image: /boot/initrd-3.1.0-1.2-default
Root device: UUID=01fb678c-d712-469e-894c-ebe8430d65a3 (/dev/sda3) (mounted on / as btrfs)
Resume device: /dev/sda2
Kernel Modules: thermal_sys thermal processor fan vmxnet3 vmw_pvscsi scsi_transport_sas mptbase mptscsih mptsas ata_generic zlib_deflate btrfs
Features: acpi block resume.userspace resume.kernel
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
File system sync driver: done
Guest operating system daemon: done
The configuration of VMware Tools 8.6.0 build-425873 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 "/usr/bin/vmware-toolbox-cmd" from the
command line or by invoking "/usr/bin/vmware-toolbox" from the command line
during an X server session.
To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.
Enjoy,
--the VMware team
全部enterのみでほぼ完成です。
途中エラーが出てますが、問題ないと思います。
0 件のコメント:
コメントを投稿