Fedora-Fr

Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

[Résolu] installation Vmware-server-2.0.2.203138.i386.rpm OK F15

Reekod

Bonjour,
je viens de faire l'installation d'une Fedora15, et installé ce package vmware-server-2.0.2.203138.i386.rpm
Pourriez vous me dire ou se trouve le log d'installation car aucun message d'erreur ne s'est produit
pourtant aucune association avec le programme ne s'est effectué et aucun exectuable des dossier ne produit d'effets...
Pourriez vous m'éclairer svp ?
Cordialement

Difool

Tu as installé le paquet comment ?
Si tu as utilisé YUM (et c'est fortement recommandé), le log d'installation est dans /var/log/yum.log

Reekod

Merci : je viens de me rendre compte que je ne suis pas sur le forum appli F15 mais F14 (j'ai honte)

un logiciel graphique a pris en charge l'installation lorsque j'ai cliqué sur le *.rpm (aucune certitude que ce soit yum qui ait été utilisé)
je vais verifier les logs de suite.

voici la ligne var/log/yum.log

Jul 16 18:31:48 Installed: VMware-server-2.0.2-203138.i386

Difool

Bon en fait, j'aurais dû regarder plus tôt (et toi aussi 🙂) mais la procédure est dans la doc : http://doc.fedora-fr.org/wiki/Installation_de_VMWare_server

Reekod

la dernière modif de la procédure que tu me conseil date un peu : Dernière modification de cette page le 15 octobre 2009 à 16:44

Je bloque lors de la config à l'étape suivante :

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/kernels/2.6.38.8-35.fc15.i686/include

The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match
your running kernel (version 2.6.38.8-35.fc15.i686).  Even if the module were 
to compile successfully, it would not load into the running kernel.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]

J'avoue que je ne saurais dire ou se trouve le C header directory pour une fédora15 🙁 je pensais que c'était çà : /usr/src/kernels/2.6.38.8-35.fc15.i686/include
mais Vmware config n'en veut po 🙁

patval

Bonjour,

J'ai aussi suivi ce tuto. Il faut bien vérifier les versions des différents composants !

Mais j'avais quand même le problème et à force de chercher sur les forum j'ai trouvé ça.
_____________________________________
1) Faire des liens
[root@fedora01 linux]# pwd
/usr/src/kernels/2.6.38.8-35.fc15.i686/include/linux

config.h -> autoconf.h
utsrelease.h -> ../../../2.6.38.8-35.fc15.i686/include/generated/utsrelease.h
---------------------

Et si cela ne marche pas, mettre à jour le fichier version.h
echo '#define UTS_RELEASE "2.6.38.8-35.fc15.i686"' >>/usr/src/kernels/2.6.38.8-35.fc15.i686/include/linux/version.h

-----------------------------------------------------------------------------------------------------
A partir de là... j'ai avancé un peu plus 🙁 mais je bloque sur un autre problème.
Si qq'un à une idée je suis preneur. Voir log ci-dessous

[root@fedora01 bin]# ./vmware-config.pl
Making sure services for VMware Server are stopped.
Stopping vmware (via systemctl): [ OK ]
None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vmmon 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.38.8-35.fc15.i686/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.38.8-35.fc15.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.38.8-35.fc15.i686'
CC [M] /tmp/vmware-config2/vmmon-only/linux/driverLog.o
In file included from /tmp/vmware-config2/vmmon-only/./include/vm_assert.h:45:0,
from /tmp/vmware-config2/vmmon-only/linux/driverLog.h:33,
/tmp/vmware-config2/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined [-Wundef]
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config2/vmmon-only/./include/vcpuset.h:103:0,
from /tmp/vmware-config2/vmmon-only/./include/modulecall.h:37,
from /tmp/vmware-config2/vmmon-only/linux/driver.c:101:
/tmp/vmware-config2/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined [-Wundef]
......
......
et pour finir
/tmp/vmware-config2/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/tmp/vmware-config2/vmmon-only/linux/driver.c:1423:4: error: too many arguments to function ‘smp_call_function’
include/linux/smp.h:73:5: note: declared here
/tmp/vmware-config2/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-config2/vmmon-only/linux/driver.c:1987:18: error: ‘struct task_struct’ has no member named ‘euid’
/tmp/vmware-config2/vmmon-only/linux/driver.c:1990:11: error: ‘struct task_struct’ has no member named ‘fsgid’
/tmp/vmware-config2/vmmon-only/linux/driver.c:1990:29: error: ‘struct task_struct’ has no member named ‘gid’
/tmp/vmware-config2/vmmon-only/linux/driver.c:2007:7: error: too many arguments to function ‘smp_call_function’
include/linux/smp.h:73:5: note: declared here
make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.38.8-35.fc15.i686'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
Unable to build the vmmon module.
...
...
Execution aborted.

-------------------------------------------

Fil Rouge

GGGrrrrr utilisé les balises et outils à votre disposition, ce n'est sinon pas sympa pour les autres (qui lisent).
( quote ou code <> )

Reekod

Bon je viens de passe en 64Bits !
La même 🙁

par contre on peut regler le problème avec cette solution :

Edit /usr/bin/vmware-config.pl

Pete wrote:Locate the following lines:
if (-e $answer . '/linux/utsrelease.h') {
$uts_headers .= "#include <linux/utsrelease.h>\n";
Change them to:
if (-e $answer . '/generated/utsrelease.h') {
$uts_headers .= "#include <./generated/utsrelease.h> \n";

çà vient de cette chouette procédure je la teste de suite et la partage en directe :

Source : http://pebers.blogspot.com/2011/06/getting-vmware-server-2-running-on.html

Pete wrote:Getting vmware server 2 running on Fedora 15
If you've ever tried to get vmware server running on ubuntu, fedora, debian or any similar Linux flavour, you'll appreciate the true meaning of pain.
It's never a simple process.

Anyhow, I just spent the better part of the night getting vmware server 2.0.2 build 203138 running reliably on my fresh Fedora 15 install. Here is my experience - hopefully others will find this of value.

The fresh install is Fedora 15 (x64), with only Minimal selected in the installer.
Kernel: 2.6.38.6-27.fc15.x86_64 #1 SMP

The VMware server package used: VMware-server-2.0.2-203138.x86_64.tar.gz

1: Preparation tasks:

disable selinux (edit /etc/sysconfig/selinux)

modify grub - (edit /etc/grub.conf)
Append nmi_watchdog=0 to your kernel /vmlinuz-2.6.38.6-27.fc15.x86_64 line.
If you don't disable the nmi_watchdog, you'll probably get a bunch of strange behavour.
VMs will turn on and then off again, you'll get errors such as "bugNr=2293" and so-on.
(Ref: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=924)

download/copy VMware-server-2.0.2-203138.x86_64.tar.gz onto your machine
download a copy of Rado Cotescu's installer/wrapper: http://codebin.cotescu.com/vmware/vmware-server-2.0.x-kernel-2.6.3x-install.sh

untar the installer/wrapper
tar xvfz raducotescu-vmware-server-linux-2.6.3x-kernel-release-1.5-1-g71f8b66.tar.gz
move the vmware installer into the untar'd directory
mv VMware-server-2.0.2-203138.i386.tar.gz raducotescu-vmware-server-linux-2.6.3x-kernel-71f8b66

change to the installer/wrapper directory
cd raducotescu-vmware-server-linux-2.6.3x-kernel-71f8b66
fire up the installer/wrapper script
sudo ./vmware-server-2.0.x-kernel-2.6.3x-install.sh

Follow the instructions - the wrapper will install prerequisite packages. Its all self explanatory.

At some point the actual vmware installer (/usr/bin/vmware-config.pl) will run.
You'll be prompted for the C header files:

What is the location of the directory of C header files that match
your running kernel? [/usr/src/linux/include]

Hit ctrl+c to leave the installer.
Edit /usr/bin/vmware-config.pl

Locate the following lines:
if (-e $answer . '/linux/utsrelease.h') {
$uts_headers .= "#include <linux/utsrelease.h>\n";
Change them to:
if (-e $answer . '/generated/utsrelease.h') {
$uts_headers .= "#include <./generated/utsrelease.h> \n";

Then rerun the vmware installer:
sudo /usr/bin/vmware-config.pl

Follow the installer instructions and set any values you deem necessary
(virtual machine files path, administrator user, etc)

Now stop the vmware server:
/etc/rc.d/init.d/vmware stop

cd to /usr/lib/vmware/lib/
rename the directory ibxml2.so.2 to SKIP-libxml2.so.2
This fixed the large number of vmware-hostd crashes I was experiencing
(Ref: http://communities.vmware.com/message/1670102#1670102)

If you haven't already, edit /etc/services
Remove/comment out
ideafarm-door 902/tcp
replace with
vmware-authd 902/tcp

Reboot.
You should now find the machine comes up without selinux enabled:
dmesg |grep -i "selinux"
[ 0.002012] SELinux: Initializing.
[ 0.002184] SELinux: Starting in permissive mode
[ 0.398670] SELinux: Registering netfilter hooks
[ 36.416252] SELinux: Disabled at runtime.
[ 36.416499] SELinux: Unregistering netfilter hooks

You should also find the nmi watchdog is disabled
cat /proc/sys/kernel/nmi_watchdog
0

vmware should be running on startup too:
netstat -anp |grep -i "vmware"

We care primarily about the auth port (902) and the management ports (8222 & 8333)
tcp 0 0 0.0.0.0:8222 0.0.0.0:* LISTEN 1735/vmware-hostd
tcp 0 0 0.0.0.0:902 0.0.0.0:* LISTEN 1628/vmware-authdla
tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 1735/vmware-hostd

Assuming these are all running, you can now point your browser at http://<yourmachine>:8222
You should get the vmware management console
Handy tip: You can also use the vmware infrastructure client to connect.
Just specify <hostname:8333> in the "IP address / Name:" field of the infrastructure client when you start it.

In my next post, I'll cover some suggestions to improve virtual machine performance for vmware server 2.0.2 build 203138 on Linux.

::Edit::
Don't forget to change your firewall rules (or turn off the iptables script).
By default this is running and it will stop you from connecting!

Je croise les doigts !
@+

Reekod

Installation terminée ! ouf et Merci Radu

Reekod wrote:
Starting vmware (via systemctl): [ OK ]

The configuration of VMware Server 2.0.2 build-203138 for Linux for this
running kernel completed successfully.

On Fedora you must follow these steps in order to make VMware Server to work properly:
1. edit /etc/services and replace the entry located on TCP/902 port with vmware-authd
2. disable SELinux by editing the /etc/selinux/config file
3. reboot your system
Housekeeping...
Thank you for using the script!
Patch provided by:
Ramon de Carvalho Valle
http://risesecurity.org
updated by sirusdv (http://ubuntuforums.org/member.php?u=1289848)
Script author:
Radu Cotescu
http://radu.cotescu.com

en attendant vos validation je reboot et test çà !

Reekod

Arf au reboot :

[reekod@LinoD ~]$ su -c "/etc/rc.d/init.d/vmware start"
Mot de passe : 
Starting vmware (via systemctl):  Job failed. See system logs and 'systemctl status' for details.
                                                           [ÉCHOUÉ]

reinstall en mode update : et çà demarre

Starting vmware (via systemctl):                           [  OK  ]

The configuration of VMware Server 2.0.2 build-203138 for Linux for this 
running kernel completed successfully.

je file vérifier les fichiers modifié et surtout la section

cd to /usr/lib/vmware/lib/
rename the directory ibxml2.so.2 to SKIP-libxml2.so.2

que j'ai totalement zappée alors qu'il le précise bien le Pete ! This fixed the large number of vmware-hostd crashes I was experiencing

Et hop !

http://127.0.0.1:8222/ui/#

VMWARE 2.0.2 sous FEDORA 15

Tschuss

Reekod

Tout fonctionne sauf un truc

Lorsque que je demande http://$ipserver:8222 à partir d'une autre machine de mon réseau je n'ai aucune réponse (alors qu'en local http://localhost:8222 marche parfaitement)
J'aimerais piloter le serveur à partir de mon windows car les addins vmware remote console firefox ne fonctionne pas sur la 5 incluse dans la fedora15 (ni sous chrome)...

please help