Funtoo VmWare How To – 02 – Kernel & VM Tool

Print Friendly, PDF & Email


Funtoo VmWare How To – 02 – Kernel & VM Tool

 

1      Note.2

2      Documentation.2

3      Kernel – Manuel3

3.1       Liste du hardware.3

3.2       Aide pour configuration.4

3.3       Configuration du menu Kernel – activation des drivers.5

3.3.1     Intel Corporation 440BX/ZX/DX – 82443BX/ZX/DX Host bridge agpgart.5

3.3.2     Intel Corporation 82371AB/EB/MB PIIX4 IDE ata_piix.6

3.3.3     Intel Corporation 82371AB/EB/MB PIIX4 ACPI i2c-piix47

3.3.4     VMware SVGA II Adapter vmware7

3.3.5     LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI mptspi8

3.3.6     Intel Corporation 82371AB/EB/MB PIIX4 USB usb-uhci,uhci-hcd8

3.3.7     Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] pcnet328

3.3.8     VMware USB2 EHCI Controller9

3.4       Réinstallation des modules externes après recompilation du noyau..10

3.5       Compilation du noyau_ 11

4      VM Ware Tool.12

4.1       Documentation_ 12

4.2       Trouver les tool VM Ware.12

4.3       installation_ 13

5      Open-vm-tools.18

5.1       Documentation_ 18

5.2       Installation.18

5.3       Vérification.18

5.3.1     Drivers.18

5.3.2     Vérification modules VM.18

5.4       Configuration share.19

5.5       Drag’n’Drop_ 19

5.6       Disk Shrink_ 20

 

1         Note.

Ce manuel concerne la configuration d’une machine VMware qui servira pour le développement sur Funtoo (java, c#, etc).

La machine a été fabriquée sans problèmes en suivant le procédure standard et en utilisant le GenKernel.

Maintenant, je vais rajouter :

·        Le Kernel Manuel : càd compilé avec les paramètres voulu.

·        Rajouter X

·        Rajouter XFCE4

2         Documentation.

Pour VMWare :

Pour le Kernel :

Pour le desktop :

Divers install :

 

3         Kernel – Manuel

3.1      Liste du hardware.

Lspci –n et copier coller vers  → http://kmuto.jp/debian/hcl/

00:00.0 0600: 8086:7190 (rev 01)

00:01.0 0604: 8086:7191 (rev 01)

00:07.0 0601: 8086:7110 (rev 08)

00:07.1 0101: 8086:7111 (rev 01)

00:07.3 0680: 8086:7113 (rev 08)

00:07.7 0880: 15ad:0740 (rev 10)

00:0f.0 0300: 15ad:0405

00:10.0 0100: 1000:0030 (rev 01)

02:00.0 0c03: 8086:7112

02:01.0 0200: 1022:2000 (rev 10)

02:02.0 0c03: 15ad:0770

Ce qui donne →

80867190      Yes     Intel Corporation       440BX/ZX/DX – 82443BX/ZX/DX Host bridge   agpgart

80867191      Yes     Intel Corporation       440BX/ZX/DX – 82443BX/ZX/DX AGP bridge   agpgart

80867110      Yes     Intel Corporation       82371AB/EB/MB PIIX4 ISA           ignore

80867111      Yes     Intel Corporation       82371AB/EB/MB PIIX4 IDE           ata_piix          v2.6.25-

80867113      Yes     Intel Corporation       82371AB/EB/MB PIIX4 ACPI        i2c-piix4         v2.6.25-

15ad0740                 VMware         Virtual Machine Communication Interface

15ad0405      Yes     VMware         SVGA II Adapter       vmware

10000030      Yes     LSI Logic / Symbios Logic  53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI            mptspi            v2.6.25-

15ad0790                 VMware         PCI bridge

80867112      Yes     Intel Corporation       82371AB/EB/MB PIIX4 USB         usb-uhci,uhci-hcd

10222000      Yes     Advanced Micro Devices [AMD]   79c970 [PCnet32 LANCE] pcnet32          v2.6.25-

15ad0770                 VMware         USB2 EHCI Controller

 

3.2      Aide pour configuration.

La procédure est toujours la même et se passe en trois étapes :

  • Etape 1 : Recherche de la chaîne de caractères du drivers détecter par la commande lspci. Par exemple : ata_piix.

find /usr/src/linux/ -name Makefile | xargs grep -i ata_piix

Ce qui donne →

/usr/src/linux/drivers/ata/Makefile:obj-$(CONFIG_ATA_PIIX)              += ata_p     iix.o

  • Etape 2 : recherche du menu « CONFIG_ATA_PIIX » dans menu config :

cd /usr/src/linux → make menuconfig → taper « / » qui est la fonction de recherche → coller le texte →

Ce qui donne le PATH →

Dans ce cas si, on peut voir que tout est déjà activé et donc, qu’il ne faut rien faire.

  • Etape 3 : quitter la fonction de recherche et activer les paramètres comme demandés à l’étape 2.

 

3.3      Configuration du menu Kernel – activation des drivers.

3.3.1      Intel Corporation 440BX/ZX/DX – 82443BX/ZX/DX Host bridge        agpgart.

find /usr/src/linux/ -name Makefile | xargs grep -i agpgart

Ce qui donne →

/usr/src/linux/drivers/char/agp/Makefile:agpgart-y := backend.o frontend.o generic.o isoch.o

/usr/src/linux/drivers/char/agp/Makefile:agpgart-$(CONFIG_COMPAT)       += compat_ioctl.o

/usr/src/linux/drivers/char/agp/Makefile:obj-$(CONFIG_AGP)              += agpgart.o

Ce qui donne →

Comme cela fonctionne déjà en module, je ne change rien.

Par contre, je supprime tout les module non nécessaire  →

 

3.3.2      Intel Corporation 82371AB/EB/MB PIIX4 IDE       ata_piix.

find /usr/src/linux/ -name Makefile | xargs grep -i ata_piix

Ce qui donne →

/usr/src/linux/drivers/ata/Makefile:obj-$(CONFIG_ATA_PIIX)              += ata_piix.o

Donc, rien a changer.

 

3.3.3      Intel Corporation 82371AB/EB/MB PIIX4 ACPI    i2c-piix4

find /usr/src/linux/ -name Makefile | xargs grep -i i2c-piix4

Ce qui donne →

/usr/src/linux/drivers/i2c/busses/Makefile:obj-$(CONFIG_I2C_PIIX4)              += i2c-piix4.o

3.3.4      VMware      SVGA II Adapter   vmware

find /usr/src/linux/ -name Makefile | xargs grep -i vmware

Ce qui donne →

/usr/src/linux/drivers/scsi/Makefile:obj-$(CONFIG_VMWARE_PVSCSI)        += vmw_pvscsi.o

/usr/src/linux/drivers/misc/Makefile:obj-$(CONFIG_VMWARE_BALLOON)       += vmw_balloon.o

/usr/src/linux/drivers/net/vmxnet3/Makefile:# Linux driver for VMware’s vmxnet3 ethernet NIC.

Ce qui suit, je ne sais pas ce que c’est, donc je le laisse désactivé →

 

3.3.5      LSI Logic / Symbios Logic      53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI   mptspi

find /usr/src/linux/ -name Makefile | xargs grep -i mptspi

Ce qui donne →

/usr/src/linux/drivers/message/fusion/Makefile:obj-$(CONFIG_FUSION_SPI) += mptbase.o mptscsih.o mptspi.o

3.3.6      Intel Corporation 82371AB/EB/MB PIIX4 USB     usb-uhci,uhci-hcd

find /usr/src/linux/ -name Makefile | xargs grep -i uhci-hcd

Ce qui donne →

/usr/src/linux/drivers/usb/host/Makefile:obj-$(CONFIG_USB_UHCI_HCD)     += uhci-hcd.o

find /usr/src/linux/ -name Makefile | xargs grep -i usb-uhci

Ce qui donne → rien

3.3.7      Advanced Micro Devices [AMD]       79c970 [PCnet32 LANCE]       pcnet32

find /usr/src/linux/ -name Makefile | xargs grep -i pcnet32

Ce qui donne →

/usr/src/linux/drivers/net/ethernet/amd/Makefile:obj-$(CONFIG_PCNET32) += pcnet32.o

3.3.8      VMware      USB2 EHCI Controller

find /usr/src/linux/ -name Makefile | xargs grep -i EHCI

Ce qui donne →

/usr/src/linux/drivers/usb/host/Makefile:obj-$(CONFIG_USB_EHCI_HCD)     += ehci-hcd.o

 

3.4      Réinstallation des modules externes après recompilation du noyau..

Une fois le kernel refait, il faut (re)installer les modules extérieurs →

  • make modules_prepare
  • emerge –ask –oneshot @module-rebuild

Ceci permet de réinstaller les modules VM → le module hgfs n’est plus actif :

modprobe -l | grep vm

kernel/arch/x86/kvm/kvm.ko

kernel/arch/x86/kvm/kvm-intel.ko

kernel/arch/x86/kvm/kvm-amd.ko

kernel/drivers/usb/serial/navman.ko

On fait un → cd /usr/src/linux & make modules_prepare

make[1]: Nothing to be done for `all’.

make[1]: Nothing to be done for `relocs’.

  CHK     include/linux/version.h

  CHK     include/generated/utsrelease.h

  CALL    scripts/checksyscalls.sh

Ensuite, on réinstalle → emerge –ask –oneshot @module-rebuild

[ebuild   R   ~] app-emulation/open-vm-tools-kmod-2012.05.21.724730

Maintenant, la liste est complète → modprobe -l | grep vm

kernel/arch/x86/kvm/kvm.ko

kernel/arch/x86/kvm/kvm-intel.ko

kernel/arch/x86/kvm/kvm-amd.ko

kernel/drivers/usb/serial/navman.ko

net/vmxnet.ko

openvmtools/vmblock.ko

openvmtools/vmci.ko

openvmtools/vmhgfs.ko

openvmtools/vmsync.ko

openvmtools/vsock.ko

 

3.5      Compilation du noyau

make && make modules_install

make install

boot-update –V

Pour activer les modules externe :

cd /usr/src/linux & make modules_prepare

emerge –oneshot @module-rebuild

funtoo-dev linux # boot-update -V

boot-update 1.6.4 /

 * Generating config for grub…

 * Validating config file /boot/grub/grub.cfg

 * Backing up original config file to /boot/grub/grub.cfg.old

 * Writing new config file to /boot/grub/grub.cfg

 * Done.

 DEFAULT > Funtoo Linux – vmlinuz-3.3.8-gentoo

           Funtoo Linux genkernel – kernel-genkernel-x86-3.3.8-gentoo

 * Configuration file /boot/grub/grub.cfg generated – 35 lines.

 * Completed successfully.

Vérfifions la configuration de boot : Cela me semble OK → reboot

 

4         VM Ware Tool.

Je n’ai jamais réussi à installer les outils officiels de VMWare sur Funtoo.

J’ai bien trouvé des astuces pour faire tourner le script, mais les modules ne compilent pas pour le noyau 3.xx. Il faut donc voir le chapitre suivant : Open-vm-tool.

J’ai quand même laissé les instructions concernant VMware tool pour informations.

4.1      Documentation

4.2      Trouver les tool VM Ware.

Normalement, il suffit de cliquer sur install VMWare tool : VMWare → Dans la tool bar → VM → install VM Tool.

Mais, dans mon cas, cela ne fonctionne pas, donc il faut trouver une alternative.

Voici comment faire : il faudra monter le CDROM et en copier l’archive.

Les tools se trouve sur la machine host (XP) : C:\Program Files\VMware\VMware Workstation\pkg\

  • Tools.cab contient l’image iso de linux tool →

  • Copie du fichier linux.ISO.xxx et renommer en linux.iso.
  • Dans VMWare, il suffit de monter le CDROM avec cette image →

  • Montage du CDROM dans funtoo →

mount /dev/sr0 /mnt/cdrom

mount: block device /dev/sr0 is write-protected, mounting read-only

 

  • Une fois le CDROM monté, on peut copier l’archive VMwareTools-7.8.5-156735.tar.gz et la décompresser : tar xzfv VMwareTools-7.8.5-156735.tar.gz

Autres possibilité pour récupérer les TOOL VMWare :

Aller sur le site http://softwareupdate.vmware.com/cds/vmw-desktop/ws/ → choisir la version de workstation et copier le fichier tool-linux* (par exemple pour WS 9 : http://softwareupdate.vmware.com/cds/vmw-desktop/ws/9.0.0/812388/windows/packages/tools-linux-9.2.0.exe.tar )

Autre possibilité : monter l’ISO en XP et copie de l’archive via mon réseau → pour cela, je monte un share →  mount //192.168.1.20/nas02-files /mnt/nas02 -o username=esa01

4.3      installation

  • Suivre les instructions spécifique ici : http://en.gentoo-wiki.com/wiki/VMware_Guest#Installing_VMware_Tools
  • mkdir /etc/rc{0..6}.d
  • ln -s /usr/src/linux/include/generated/utsrelease.h /usr/src/linux/include/linux/utsrelease.h
  • ln -s /usr/src/linux/include/generated/autoconf.h /usr/src/linux/include/linux/autoconf.h
  • lancer l’installation : cd vmware-tools-distrib  → ./vmware-install.pl

Creating a new VMware Tools installer database using the tar4 format.

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.8.5 build-156735 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]

It looks like you are trying to run this program in a remote session. This

program will temporarily shut down your network connection, so you should only

run it from a local console session. Are you SURE you want to continue?

 

Ensuite, le module vmmemctl n’a pas été installé :

Stopping VMware Tools services in the virtual machine:

   Guest operating system daemon:                                      done

   Virtual Printing daemon:                                            done

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/3.3.8-gentoo/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/3.3.8-gentoo/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-3.3.8-gentoo’

  CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o

In file included from /tmp/vmware-config0/vmmemctl-only/os.c:51:0:

/tmp/vmware-config0/vmmemctl-only/compat_wait.h:78:13: error: conflicting types for âpoll_initwaitâ

include/linux/poll.h:72:13: note: previous declaration of âpoll_initwaitâ was here

/tmp/vmware-config0/vmmemctl-only/os.c:68:28: fatal error: linux/smp_lock.h: No such file or directory

compilation terminated.

make[2]: *** [/tmp/vmware-config0/vmmemctl-only/os.o] Error 1

make[1]: *** [_module_/tmp/vmware-config0/vmmemctl-only] Error 2

make[1]: Leaving directory `/usr/src/linux-3.3.8-gentoo’

make: *** [vmmemctl.ko] Error 2

make: Leaving directory `/tmp/vmware-config0/vmmemctl-only’

Unable to build the vmmemctl module.

 

The memory manager driver (vmmemctl module) is used by VMware host software to

efficiently reclaim memory from a virtual machine.

If the driver is not available, VMware host software may instead need to swap

guest memory to disk, which may reduce performance.

The rest of the software provided by VMware Tools is designed to work

independently of this feature.

If you want the memory management 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.

 

Idem pour vmhgfs :

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]

 

Extracting the sources of the vmhgfs module.

 

Building the vmhgfs module.

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config1/vmhgfs-only’

make -C /lib/modules/3.3.8-gentoo/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-3.3.8-gentoo’

  CC [M]  /tmp/vmware-config1/vmhgfs-only/message.o

In file included from /tmp/vmware-config1/vmhgfs-only/kernelStubs.h:35:0,

                 from /tmp/vmware-config1/vmhgfs-only/message.c:45:

/tmp/vmware-config1/vmhgfs-only/vm_basic_types.h:108:7: warning: “__FreeBSD__” is not defined [-Wundef]

  CC [M]  /tmp/vmware-config1/vmhgfs-only/dir.o

In file included from /tmp/vmware-config1/vmhgfs-only/cpName.h:47:0,

                 from /tmp/vmware-config1/vmhgfs-only/dir.c:34:

/tmp/vmware-config1/vmhgfs-only/vm_basic_types.h:108:7: warning: “__FreeBSD__” is not defined [-Wundef]

In file included from /tmp/vmware-config1/vmhgfs-only/request.h:35:0,

                 from /tmp/vmware-config1/vmhgfs-only/dir.c:39:

/tmp/vmware-config1/vmhgfs-only/compat_wait.h:78:13: error: conflicting types for âpoll_initwaitâ

include/linux/poll.h:72:13: note: previous declaration of âpoll_initwaitâ was here

make[2]: *** [/tmp/vmware-config1/vmhgfs-only/dir.o] Error 1

make[1]: *** [_module_/tmp/vmware-config1/vmhgfs-only] Error 2

make[1]: Leaving directory `/usr/src/linux-3.3.8-gentoo’

make: *** [vmhgfs.ko] Error 2

make: Leaving directory `/tmp/vmware-config1/vmhgfs-only’

Unable to build the vmhgfs module.

 

The filesystem driver (vmhgfs module) is used only for the shared folder

feature. The rest of the software provided by VMware Tools is designed to work

independently of this feature.

 

If you wish to have the shared folders 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.

 

Idem pour vmxnet :

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]

 

Extracting the sources of the vmxnet module.

 

Building the vmxnet module.

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config2/vmxnet-only’

make -C /lib/modules/3.3.8-gentoo/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-3.3.8-gentoo’

  CC [M]  /tmp/vmware-config2/vmxnet-only/vmxnet.o

In file included from /tmp/vmware-config2/vmxnet-only/vmxnet.c:48:0:

/tmp/vmware-config2/vmxnet-only/vm_basic_types.h:108:7: warning: “__FreeBSD__” is not defined [-Wundef]

/tmp/vmware-config2/vmxnet-only/vmxnet.c:2545:46: error: âstruct net_deviceâ has no member named âprivâ

make[2]: *** [/tmp/vmware-config2/vmxnet-only/vmxnet.o] Error 1

make[1]: *** [_module_/tmp/vmware-config2/vmxnet-only] Error 2

make[1]: Leaving directory `/usr/src/linux-3.3.8-gentoo’

make: *** [vmxnet.ko] Error 2

make: Leaving directory `/tmp/vmware-config2/vmxnet-only’

Unable to build the vmxnet module.

 

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.

Idem pour VMBlock :

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]

 

Extracting the sources of the vmblock module.

 

Building the vmblock module.

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config3/vmblock-only’

make -C /lib/modules/3.3.8-gentoo/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-3.3.8-gentoo’

  CC [M]  /tmp/vmware-config3/vmblock-only/linux/dbllnklst.o

In file included from /tmp/vmware-config3/vmblock-only/./include/vmware.h:38:0,

                 from /tmp/vmware-config3/vmblock-only/linux/dbllnklst.c:19:

/tmp/vmware-config3/vmblock-only/./include/vm_basic_types.h:108:7: warning: “__FreeBSD__” is not defined [-Wundef]

  CC [M]  /tmp/vmware-config3/vmblock-only/linux/stubs.o

In file included from /tmp/vmware-config3/vmblock-only/linux/os.h:35:0,

                 from /tmp/vmware-config3/vmblock-only/linux/stubs.c:26:

/tmp/vmware-config3/vmblock-only/./include/compat_wait.h:78:13: error: conflicting types for âpoll_initwaitâ

include/linux/poll.h:72:13: note: previous declaration of âpoll_initwaitâ was here

make[2]: *** [/tmp/vmware-config3/vmblock-only/linux/stubs.o] Error 1

make[1]: *** [_module_/tmp/vmware-config3/vmblock-only] Error 2

make[1]: Leaving directory `/usr/src/linux-3.3.8-gentoo’

make: *** [vmblock.ko] Error 2

make: Leaving directory `/tmp/vmware-config3/vmblock-only’

Unable to build the vmblock module.

 

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.

 

Idem pour vmci :

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]

 

Extracting the sources of the vmci module.

 

Building the vmci module.

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config4/vmci-only’

make -C /lib/modules/3.3.8-gentoo/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-3.3.8-gentoo’

  CC [M]  /tmp/vmware-config4/vmci-only/vmciUtil.o

In file included from /tmp/vmware-config4/vmci-only/vmciUtil.c:35:0:

/tmp/vmware-config4/vmci-only/compat_wait.h:78:13: error: conflicting types for âpoll_initwaitâ

include/linux/poll.h:72:13: note: previous declaration of âpoll_initwaitâ was here

In file included from /tmp/vmware-config4/vmci-only/vmware.h:38:0,

                 from /tmp/vmware-config4/vmci-only/vmciUtil.c:52:

/tmp/vmware-config4/vmci-only/vm_basic_types.h:108:7: warning: “__FreeBSD__” is not defined [-Wundef]

In file included from /tmp/vmware-config4/vmci-only/vmciUtil.c:53:0:

/tmp/vmware-config4/vmci-only/vm_atomic.h:329:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:333:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:401:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:407:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Andâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:506:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Orâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:595:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Xorâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:684:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Addâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:773:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:775:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Subâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:860:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:862:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Incâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:945:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:947:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: In function âAtomic_Decâ:

/tmp/vmware-config4/vmci-only/vm_atomic.h:1028:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:1030:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h: At top level:

/tmp/vmware-config4/vmci-only/vm_atomic.h:1223:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:1227:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:1536:7: warning: “_MSC_VER” is not defined [-Wundef]

/tmp/vmware-config4/vmci-only/vm_atomic.h:1663:7: warning: “_MSC_VER” is not defined [-Wundef]

make[2]: *** [/tmp/vmware-config4/vmci-only/vmciUtil.o] Error 1

make[1]: *** [_module_/tmp/vmware-config4/vmci-only] Error 2

make[1]: Leaving directory `/usr/src/linux-3.3.8-gentoo’

make: *** [vmci.ko] Error 2

make: Leaving directory `/tmp/vmware-config4/vmci-only’

Unable to build the vmci module.

 

The communication service is used in addition to the standard communication

between the guest and the host.  The rest of the software provided by VMware

Tools is designed to work independently of this feature.

If you wish to have the VMCI 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 Enter key to continue ]

You can now run VMware Tools by invoking the following command:

“/usr/bin/vmware-toolbox” 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.

 

5         Open-vm-tools.

Les Open-vm-tools sont très facile à installer et fonctionnent.

Voici les fonctionnalités testées :

  • Copy-paste de Windows vers Funtoo et inversement : OK
  • Share folder entre le host et le ghest                                : OK
  • Déblocage automatique de la souris → ne fonctionne pas. Il faut déverrouiller manuellement avec les touches « hot keys » de VMWare.

5.1      Documentation

5.2      Installation.

emerge -av app-emulation/open-vm-tools

 [ebuild  N     ] sys-fs/fuse-2.8.6  USE=”-static-libs”

[ebuild  N     ] sys-apps/ethtool-3.0

[ebuild  N     ] virtual/linux-sources-2.6  USE=”-hardened”

[ebuild  N    ~] app-emulation/open-vm-tools-kmod-2012.05.21.724730

[ebuild  N     ] dev-libs/libdnet-1.11-r2  USE=”python -static-libs”

[ebuild  N    ~] app-emulation/open-vm-tools-2012.05.21.724730  USE=”fuse pic -X -doc -icu -xinerama”

5.3      Vérification.

5.3.1      Drivers.

qlist -IC x11-drivers

x11-drivers/xf86-input-evdev

x11-drivers/xf86-video-vmware

5.3.2      Vérification modules VM.

modprobe -l | grep vm

kernel/arch/x86/kvm/kvm.ko

kernel/arch/x86/kvm/kvm-intel.ko

kernel/arch/x86/kvm/kvm-amd.ko

kernel/drivers/usb/serial/navman.ko

net/vmxnet.ko

openvmtools/vmblock.ko

openvmtools/vmci.ko

openvmtools/vmhgfs.ko

openvmtools/vmsync.ko

openvmtools/vsock.ko

 

ps aux | grep vm

 

5.4      Configuration share.

Configurer le share dans VMWare Workstation :

Créer un répertoire /mnt/hgfs

Monter le share :       mount -t vmhgfs .host:/ /mnt/hgfs

Ou dans fstab :         .host:/                 /mnt/hgfs       vmhgfs          defaults,ttl=5  0 0

5.5      Drag’n’Drop

Messages for package app-emulation/open-vm-tools-2012.05.21.724730:

 * To be able to use the drag’n’drop feature of VMware for file

 * exchange, please add the users to the ‘vmware’ group.

 * Add ‘vmware-tools’ service to the default runlevel.

>>> Auto-cleaning packages…

  • usermod -aG vmware root
  • rc-update add vmware-tools default

 

5.6      Disk Shrink

Il faut le lancer dans un terminal : vmware-toolbox-cmd disk list pour connaître les partitions possibles.

Ensuite il faut lancer la commande suivante pour préparer la partition: vmware-toolbox-cmd disk shrink /home

Progress: 100 [===========>]

A la fin du proces, VMWare workstation va automatiquement faire un shrink du disque →

Vérification : de 10 GB, on passe à :

Avant :

Après :