Connexion

Forum

Logiciels » Virtualisation et Émulation [Réglé] VMWare Player et kernel lancement de VMWare impossible selon le noyau

teutates Membre non connecté

Rang

Avatar

Inscrit le : 24/09/2011 à 01h41

Localisation : Ariège

Messages: 1305

Le 01/10/2014 à 22h36
Bonjour,



Uniquement pour ma machine virtuelle Windows 7, j'utilise VMWare Player puisque ce même Windows est incapable de bénéficier d'un réel support USB sous VirtualBox (à jour et avec les bonnes extensions VBox).



Uniquement avec Mageia (parce que j'ai testé aussi avec les autres distributions "majeures"), utiliser VMWare (le Player comme Worstation) exige systématiquement de recompiler les modules à chaque lancement. C'est chiant mais je fait avec. Cette compilation exige les sources du noyau et la création préalable d'un lien symbolique du fichier version.h des sources du noyau. Toutes ces exigences pour compiler ont toujours été satisfaites.



Sauf qu'avec le nouveau noyau, impossible de compiler ces modules. J'obtiens systématiquement le message d'erreur suivant :

Unable to start services.

See log file /tmp/vmware-root/vmware-modconfig-31300.log for details.




Voici le détail du fichier log :

Caché :
2014-10-01T21:49:38.733+01:00| vthread-3| I120: Log for VMware Workstation pid=31300 version=10.0.0 build=build-1295980 option=Release

2014-10-01T21:49:38.733+01:00| vthread-3| I120: The process is 64-bit.

2014-10-01T21:49:38.733+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8

2014-10-01T21:49:38.733+01:00| vthread-3| I120: Host is Linux 3.14.18-desktop-3.mga4 Mageia 4

2014-10-01T21:49:38.731+01:00| vthread-3| I120: Msg_Reset:

2014-10-01T21:49:38.731+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Aucun fichier ou dossier de ce type.

2014-10-01T21:49:38.731+01:00| vthread-3| I120: ----------------------------------------

2014-10-01T21:49:38.731+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2014-10-01T21:49:38.732+01:00| vthread-3| I120: Msg_Reset:

2014-10-01T21:49:38.732+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/thierry/.vmware/config": Aucun fichier ou dossier de ce type.

2014-10-01T21:49:38.732+01:00| vthread-3| I120: ----------------------------------------

2014-10-01T21:49:38.732+01:00| vthread-3| I120: PREF Optional preferences file not found at /home/thierry/.vmware/config. Using default values.

2014-10-01T21:49:38.733+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-31300.log

2014-10-01T21:49:38.739+01:00| vthread-3| I120: Obtaining info using the running kernel.

2014-10-01T21:49:38.739+01:00| vthread-3| I120: Created new pathsHash.

2014-10-01T21:49:38.739+01:00| vthread-3| I120: Setting header path for 3.14.18-desktop-3.mga4 to "/lib/modules/3.14.18-desktop-3.mga4/build/include".

2014-10-01T21:49:38.739+01:00| vthread-3| I120: Validating path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for kernel release "3.14.18-desktop-3.mga4".

2014-10-01T21:49:38.739+01:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2014-10-01T21:49:38.744+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.14.18-desktop-3.mga4".

2014-10-01T21:49:38.744+01:00| vthread-3| I120: The header path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for the kernel "3.14.18-desktop-3.mga4" is valid. Whoohoo!

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Reading in info for the vmmon module.

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Reading in info for the vmnet module.

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Reading in info for the vmblock module.

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Reading in info for the vmci module.

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Reading in info for the vsock module.

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Setting vsock to depend on vmci.

2014-10-01T21:49:38.883+01:00| vthread-3| I120: Invoking modinfo on "vmmon".

2014-10-01T21:49:38.885+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

2014-10-01T21:49:38.885+01:00| vthread-3| I120: Invoking modinfo on "vmnet".

2014-10-01T21:49:38.886+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2014-10-01T21:49:38.886+01:00| vthread-3| I120: Invoking modinfo on "vmblock".

2014-10-01T21:49:38.887+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2014-10-01T21:49:38.887+01:00| vthread-3| I120: Invoking modinfo on "vmci".

2014-10-01T21:49:38.888+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2014-10-01T21:49:38.888+01:00| vthread-3| I120: Invoking modinfo on "vsock".

2014-10-01T21:49:38.890+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

2014-10-01T21:49:38.899+01:00| vthread-3| I120: to be installed: vmnet status: 0

2014-10-01T21:49:38.899+01:00| vthread-3| I120: to be installed: vmci status: 0

2014-10-01T21:49:38.908+01:00| vthread-3| I120: Obtaining info using the running kernel.

2014-10-01T21:49:38.908+01:00| vthread-3| I120: Setting header path for 3.14.18-desktop-3.mga4 to "/lib/modules/3.14.18-desktop-3.mga4/build/include".

2014-10-01T21:49:38.908+01:00| vthread-3| I120: Validating path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for kernel release "3.14.18-desktop-3.mga4".

2014-10-01T21:49:38.908+01:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2014-10-01T21:49:38.913+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.14.18-desktop-3.mga4".

2014-10-01T21:49:38.913+01:00| vthread-3| I120: The header path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for the kernel "3.14.18-desktop-3.mga4" is valid. Whoohoo!

2014-10-01T21:49:39.044+01:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.14.18-desktop-3.mga4/build/include

2014-10-01T21:49:39.044+01:00| vthread-3| I120: Update kernel header path to /lib/modules/3.14.18-desktop-3.mga4/build/include

2014-10-01T21:49:39.044+01:00| vthread-3| I120: Validating path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for kernel release "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.044+01:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2014-10-01T21:49:39.049+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.049+01:00| vthread-3| I120: The header path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for the kernel "3.14.18-desktop-3.mga4" is valid. Whoohoo!

2014-10-01T21:49:39.050+01:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"

2014-10-01T21:49:39.052+01:00| vthread-3| I120: Got gcc version "4.8.2".

2014-10-01T21:49:39.052+01:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.

2014-10-01T21:49:39.052+01:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".

2014-10-01T21:49:39.054+01:00| vthread-3| I120: Got gcc version "4.8.2".

2014-10-01T21:49:39.054+01:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.

2014-10-01T21:49:39.057+01:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.057+01:00| vthread-3| I120: No matching PBM set was found for kernel "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.058+01:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.

2014-10-01T21:49:39.058+01:00| vthread-3| I120: Validating path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for kernel release "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.058+01:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2014-10-01T21:49:39.063+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.063+01:00| vthread-3| I120: The header path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for the kernel "3.14.18-desktop-3.mga4" is valid. Whoohoo!

2014-10-01T21:49:39.063+01:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.

2014-10-01T21:49:39.063+01:00| vthread-3| I120: Validating path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for kernel release "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.063+01:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2014-10-01T21:49:39.068+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.068+01:00| vthread-3| I120: The header path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for the kernel "3.14.18-desktop-3.mga4" is valid. Whoohoo!

2014-10-01T21:49:39.068+01:00| vthread-3| I120: Using temp dir "/tmp".

2014-10-01T21:49:39.068+01:00| vthread-3| I120: Obtaining info using the running kernel.

2014-10-01T21:49:39.069+01:00| vthread-3| I120: Setting header path for 3.14.18-desktop-3.mga4 to "/lib/modules/3.14.18-desktop-3.mga4/build/include".

2014-10-01T21:49:39.069+01:00| vthread-3| I120: Validating path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for kernel release "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.069+01:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2014-10-01T21:49:39.073+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.14.18-desktop-3.mga4".

2014-10-01T21:49:39.074+01:00| vthread-3| I120: The header path "/lib/modules/3.14.18-desktop-3.mga4/build/include" for the kernel "3.14.18-desktop-3.mga4" is valid. Whoohoo!

2014-10-01T21:49:39.203+01:00| vthread-3| I120: Invoking modinfo on "vmnet".

2014-10-01T21:49:39.205+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2014-10-01T21:49:39.205+01:00| vthread-3| I120: Invoking modinfo on "vmci".

2014-10-01T21:49:39.206+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2014-10-01T21:49:39.261+01:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.14.18-desktop-3.mga4/misc/vmnet.ko".

2014-10-01T21:49:39.262+01:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2014-10-01T21:49:39.305+01:00| vthread-3| I120: Successfully extracted the vmnet source.

2014-10-01T21:49:39.305+01:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-nnk2q3/vmnet-only auto-build HEADER_DIR=/lib/modules/3.14.18-desktop-3.mga4/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2014-10-01T21:49:44.600+01:00| vthread-3| W110: Failed to build vmnet. Failed to execute the build command.

2014-10-01T21:49:44.601+01:00| vthread-3| I120: Setting destination path for vmci to "/lib/modules/3.14.18-desktop-3.mga4/misc/vmci.ko".

2014-10-01T21:49:44.601+01:00| vthread-3| I120: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".

2014-10-01T21:49:44.651+01:00| vthread-3| I120: Successfully extracted the vmci source.

2014-10-01T21:49:44.651+01:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-nnk2q3/vmci-only auto-build HEADER_DIR=/lib/modules/3.14.18-desktop-3.mga4/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2014-10-01T21:49:45.845+01:00| vthread-3| W110: Failed to build vmci. Failed to execute the build command.




Le noyau avec lequel VMWare refuse de démarrer est 3.14.18-desktop-3.mga4. Par contre, hier soir, par curiosité (et parce que je me doutais de la suite), j'ai démarré sur l'avant dernier noyau, à savoir le 3.12.25-desktop-3.mga4, et VMWare a compilé correctement ses modules pour démarrer ensuite correctement. Entre hier soir avec le noyau 3.12.25-desktop-3.mga4 (où VMWare démarre) et ce soir avec le noyau 3.14.18-desktop-3.mga4 (où VMWare échoue), je n'ai apporté strictement aucun changement et aucune mise à jour.



Le problème vient directement et uniquement du noyau 3.14.18-desktop-3.mga4. Bug régressif ? Je poste ici mais je suis conscient que le mieux serait de poster directement dans Bugzilla mais je me vois mal poster une tel truc in english :gene5:



A moins que je sois passé à côté de quelque chose ?! :siffle:


Toco y se gausos !
Asus P8Z68-V/GEN3 + Intel Core i2700k + RAM G-Skill 4x4Go PC 12800 + Gainward Geforce GTX 560 - 2 Go + Western Digital Velociraptor 300 Go (Mageia Cauldron / Fedora / Debian / Manjaro / Windows 10) + Seagate Barracuda 7200t/mn - 2 To - Sata 3 (data) + SSD Samsung 64 Go - Sata 3 (Mageia stable)
Site web    
Adrien.D Membre non connecté

Rang

Avatar

Webmaster Admin système

Inscrit le : 30/05/2011 à 18h36

Localisation : Dijon-21-FRA

Messages: 10322

Le 02/10/2014 à 07h28
Salut,

Quelle est ta version de Vmware Player ?


Config : PC Fixe : X470 GAMING PRO- AMD Ryzen 5 2600X - 16Go RAM - Radeon RX 560 (Pilote libre) - user_bar_calculate - GNOME Desktop - Kernel 4.19 LTS
Vice président de l'association COAGUL ("Côte-d’Or - Association Générale des Utilisateurs de Logiciels libres")
Webmaster de MageiaLinuxOnline uniquement. Pas de support de ma part.
Site web    
teutates Membre non connecté

Rang

Avatar

Inscrit le : 24/09/2011 à 01h41

Localisation : Ariège

Messages: 1305

Le 02/10/2014 à 18h16
Adrien.D :
Salut,



Quelle est ta version de Vmware Player ?




VMWare Player version 6.0.1-1379776 x86_64


Toco y se gausos !
Asus P8Z68-V/GEN3 + Intel Core i2700k + RAM G-Skill 4x4Go PC 12800 + Gainward Geforce GTX 560 - 2 Go + Western Digital Velociraptor 300 Go (Mageia Cauldron / Fedora / Debian / Manjaro / Windows 10) + Seagate Barracuda 7200t/mn - 2 To - Sata 3 (data) + SSD Samsung 64 Go - Sata 3 (Mageia stable)
Site web    
Adrien.D Membre non connecté

Rang

Avatar

Webmaster Admin système

Inscrit le : 30/05/2011 à 18h36

Localisation : Dijon-21-FRA

Messages: 10322

Le 02/10/2014 à 18h27
Salut,

Depuis, on a la version 6.0.3.

https://my.vmware.com/fr/web/vmware/free#desktop_end_user_computing/vmware_player/6_0

La version 6.0.2 corrige les problèmes de compilation du module "vmnet" apparu depuis le kernel 3.13.
Là, il y a 6.0.3, je te conseille de prendre cette dernière version en date ;)


Config : PC Fixe : X470 GAMING PRO- AMD Ryzen 5 2600X - 16Go RAM - Radeon RX 560 (Pilote libre) - user_bar_calculate - GNOME Desktop - Kernel 4.19 LTS
Vice président de l'association COAGUL ("Côte-d’Or - Association Générale des Utilisateurs de Logiciels libres")
Webmaster de MageiaLinuxOnline uniquement. Pas de support de ma part.
Site web    
teutates Membre non connecté

Rang

Avatar

Inscrit le : 24/09/2011 à 01h41

Localisation : Ariège

Messages: 1305

Le 02/10/2014 à 22h22
Je viens de faire la mise à jour avec la 6.0.3 et l'application démarre désormais correctement (même si je dois à chaque redémarrage relancer la compilation des modules (procédure spéciale Mageia)). Merci pour l'info, Adrien :super: Edité par teutates Le 02/10/2014 à 23h18


Toco y se gausos !
Asus P8Z68-V/GEN3 + Intel Core i2700k + RAM G-Skill 4x4Go PC 12800 + Gainward Geforce GTX 560 - 2 Go + Western Digital Velociraptor 300 Go (Mageia Cauldron / Fedora / Debian / Manjaro / Windows 10) + Seagate Barracuda 7200t/mn - 2 To - Sata 3 (data) + SSD Samsung 64 Go - Sata 3 (Mageia stable)
Site web    
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie