Jump to content

Archived

This topic is now archived and is closed to further replies.

Charlelie

VMWare Tools sous système virtualisé Ubuntu

Recommended Posts

Bonjour

J'ai installer la dernière version d'Ubuntu, ainsi que ses mises à jour et j'ai installé les VMWare tools. Le problème étant qu'il a dû les recompiler, il y a eu des erreurs et je ne sais pas si ceux-ci sont bien fonctionnels. A priori, je dirais non car je n'ai pas le copié/collé avec l'hôte ni l'accélération graphique apparement, ainsi que le "décrochage automatique" du curseur si on sort de la fenêtre.

J'ai testé XP en systéme invité et tout fonctionne bien.

Ma question est donc, est-ce normal ? Toutes les fonctionnalités des additionnels de VMWare sont bien fonctionnelles sous Ubuntu ? Au moins l'accélération graphique, le décrochage et le copié collé ?

Je pense que c'est pas utile de préciser mais je suis sous VMWare Server 1.04 et XP SP2 en hôte.

Share this post


Link to post
Share on other sites

dis nous en plus sur les erreurs qu'il y a eut sans ça on peut pas faire grand chose

Share this post


Link to post
Share on other sites

J' utilise Virtualbox et j' ai rencontré un problème similaire avec le décrochage de la souris.

il faut tout simplement ne mettre aucunes souris en détection dans la configuration de la machine virtuel, et laissé le system hote gérer la souris.

Un décrochage de la souris est ensuite possible avec le racourcit clavier prédéfinit dans les options, mais ont ne doit pas indiquer de souris dans la configuration de la machine virtuel.

Et laisser le system hote gérer la souris du system + de la machine virtuel, voilà pourquoi ça risque de coincer.

Copier coller de quoi ?

capture d' image tu veux dire ?

Share this post


Link to post
Share on other sites

je pense qu'elle parle du copier/collre entre machine hote et machine invitée

Pour le decrochage de la souris elle parle du decrochage automatique c'est pratique mais faut les vmware-tools

Share this post


Link to post
Share on other sites

Exact, il faut les Vmwares tools. Et je voulais simplement savoir si les fonctionnalités (citées) que sont censé apporter les Vmware Tools marchent bien sous Ubuntu ? Car j'ai téléchargé une machine virtuelle de Ubuntu avec les Vmware tools de déjà installés (apparament, la description le disais) mais Vmware me disais qu'ils étaient pas installés et aucune des fonctionnalités des tools ne marchait.

Après, si vous voulez l'erreur, ok, accrochez vous ^^ J'ai mis tout le terminal pour que vous compreniez bien.

moi@moi-desktop:~$ cd Desktop

moi@moi-desktop:~/Desktop$ ls

VMwareTools-1.0.4-56528.i386.rpm vmwaretools_6532-56529_i386.deb

VMwareTools-5.5.1-19175.tar.gz vmware-tools-distrib

moi@moi-desktop:~/Desktop$ cd vmware-tools-distrib

moi@moi-desktop:~/Desktop/vmware-tools-distrib$ ls

bin doc etc FILES INSTALL installer lib vmware-install.pl

moi@moi-desktop:~/Desktop/vmware-tools-distrib$ sudo ./vmware-install.pl

Password:

A previous installation of VMware software has been detected.

The previous installation was made by the tar installer (version 3).

Keeping the tar3 installer database format.

Uninstalling the tar installation of VMware Tools.

Stopping VMware Tools services in the virtual machine:

Guest operating system daemon:-ne done

The removal of VMware Tools 1.0.4 build-56528 for Linux completed successfully.

Thank you for having tried this software.

Installing the content of the package.

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 installation of VMware Tools 1.0.4 build-56528 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:-ne done

Trying to find a suitable vmhgfs module for your 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]

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.20-16-generic/build/include]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.

make: entrant dans le répertoire « /tmp/vmware-config0/vmhgfs-only »

make -C /lib/modules/2.6.20-16-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.20-16-generic »

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/dev.o

CC [M] /tmp/vmware-config0/vmhgfs-only/driver.o

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsChangeFileAttributes":

/tmp/vmware-config0/vmhgfs-only/driver.c:763: erreur: «struct inode" has no member named «i_blksize"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsInitializeInode":

/tmp/vmware-config0/vmhgfs-only/driver.c:835: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsIget":

/tmp/vmware-config0/vmhgfs-only/driver.c:884: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsCreate":

/tmp/vmware-config0/vmhgfs-only/driver.c:1535: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsLookup":

/tmp/vmware-config0/vmhgfs-only/driver.c:1635: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsMkdir":

/tmp/vmware-config0/vmhgfs-only/driver.c:1727: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsDelete":

/tmp/vmware-config0/vmhgfs-only/driver.c:1854: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsRename":

/tmp/vmware-config0/vmhgfs-only/driver.c:2046: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c:2048: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsRevalidate":

/tmp/vmware-config0/vmhgfs-only/driver.c:2288: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsSetattr":

/tmp/vmware-config0/vmhgfs-only/driver.c:2425: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsOpen":

/tmp/vmware-config0/vmhgfs-only/driver.c:2801: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsDirOpen":

/tmp/vmware-config0/vmhgfs-only/driver.c:3414: erreur: «struct inode" has no member named «u"

/tmp/vmware-config0/vmhgfs-only/driver.c: In function «HgfsClearInode":

/tmp/vmware-config0/vmhgfs-only/driver.c:4105: erreur: «struct inode" has no member named «u"

make[2]: *** [/tmp/vmware-config0/vmhgfs-only/driver.o] Erreur 1

make[1]: *** [_module_/tmp/vmware-config0/vmhgfs-only] Erreur 2

make[1]: quittant le répertoire « /usr/src/linux-headers-2.6.20-16-generic »

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

make: quittant le répertoire « /tmp/vmware-config0/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.

[ Press Enter key to continue ]

pcnet32 34052 0

Unloading pcnet32 module

vmxnet 13184 0

Unloading vmxnet module

Trying to find a suitable vmxnet module for your 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]

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.

make: entrant dans le répertoire « /tmp/vmware-config1/vmxnet-only »

make -C /lib/modules/2.6.20-16-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.20-16-generic »

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

/tmp/vmware-config1/vmxnet-only/vmxnet.c: In function «vmxnet_open":

/tmp/vmware-config1/vmxnet-only/vmxnet.c:671: attention : passing argument 2 of «request_irq" from incompatible pointer type

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/vmware-config1/vmxnet-only/vmxnet.mod.o

LD [M] /tmp/vmware-config1/vmxnet-only/vmxnet.ko

make[1]: quittant le répertoire « /usr/src/linux-headers-2.6.20-16-generic »

cp -f vmxnet.ko ./../vmxnet.o

make: quittant le répertoire « /tmp/vmware-config1/vmxnet-only »

The module loads perfectly in the running kernel.

Detected X.org version 7.2.

Please choose one of the following display sizes (1 - 13):

[1] "640x480"

[2] "800x600"

[3] "1024x768"

[4] "1152x864"

[5] "1280x800"

[6] "1152x900"

[7] "1280x1024"

[8] "1376x1032"

[9] "1400x1050"

[10] "1680x1050"

[11] "1600x1200"

[12] "1920x1200"

[13] "2364x1773"

Please enter a number between 1 and 13:

[3] 3

X Window System Version 7.2.0

Release Date: 22 January 2007

X Protocol Version 11, Revision 0, Release 7.2

Build Operating System: Linux Ubuntu

Current Operating System: Linux moi-desktop 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686

Build Date: 04 April 2007

Before reporting problems, check http://wiki.x.org

to make sure that you have the latest version.

Module Loader present

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-config1/XF86ConfigLog.5637", Time: Sun Sep 23 22:35:35 2007

(++) Using config file: "/tmp/vmware-config1/XF86Config.5637"

(WW) VMWARE(0): Failed to set up write-combining range (0xf0000000,0x1000000)

(EE) AIGLX: Screen 0 is not DRI capable

The XKEYBOARD keymap compiler (xkbcomp) reports:

> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols

> Ignoring extra symbols

Errors from xkbcomp are not fatal to the X server

(EE) xf86OpenSerial: Cannot open device /dev/input/wacom

No such file or directory.

Error opening /dev/input/wacom : Success

(EE) xf86OpenSerial: Cannot open device /dev/input/wacom

No such file or directory.

Error opening /dev/input/wacom : Success

(EE) xf86OpenSerial: Cannot open device /dev/input/wacom

No such file or directory.

Error opening /dev/input/wacom : Success

Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!

Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!

X is running fine with the new config file.

FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.

Starting VMware Tools services in the virtual machine:

Switching to guest configuration:-ne done

Guest vmxnet fast network device:-ne done

DMA setup:-ne done

Guest operating system daemon:-ne done

The configuration of VMware Tools 1.0.4 build-56528 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 session.

To make use of the vmxnet driver you will need to rebooot.

Enjoy,

--the VMware team

moi@moi-desktop:~/Desktop/vmware-tools-distrib$

Share this post


Link to post
Share on other sites

×
×
  • Create New...