#1 Le 29/05/2015, à 20:44
- centralo
Virtual machine monitor [failed] vmware workstation ubuntu 12
Bonsoir, je me trouve actuellement devant un problème qui chez beaucoup d'autre dans le même cas se sont vite résolus mais pas pour moi, je m'explique. j'ai installé la derniere version de vmware workstation sur ubuntu 12, mis à jour le kernel et les modules. tout fonctionne jusqu'à ce que je lance la machine virtuelle à ce moment j'ai les 2 erreurs suivantes
http://oi61.tinypic.com/o7249j.jpg
http://s28.postimg.org/ib53ceh5p/image.png
alors j'ai fais quelques recherches sur google et sur un forum il etait proposer de lancer en ligne de commande vmware-modconfig --console --install-all
ce que j'ai fais, mais voila le probleme: Virtual machine monitor failed
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using kernel build system.
make: Entering directory `/tmp/modconfig-U0gczv/vmmon-only'
/usr/bin/make -C /lib/modules/3.2.0-37-virtual/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-37-virtual'
CC [M] /tmp/modconfig-U0gczv/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/linux/hostif.o
/tmp/modconfig-U0gczv/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/modconfig-U0gczv/vmmon-only/linux/driver.c:2054:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/task.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-U0gczv/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-U0gczv/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-U0gczv/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-U0gczv/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-37-virtual'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-U0gczv/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-U0gczv/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-U0gczv/vmmon-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-U0gczv/vmnet-only'
/usr/bin/make -C /lib/modules/3.2.0-37-virtual/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-37-virtual'
CC [M] /tmp/modconfig-U0gczv/vmnet-only/driver.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/hub.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/userif.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/netif.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/bridge.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/procfs.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/smac.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-U0gczv/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-U0gczv/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-U0gczv/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-U0gczv/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-37-virtual'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-U0gczv/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-U0gczv/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-U0gczv/vmnet-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-U0gczv/vmci-only'
/usr/bin/make -C /lib/modules/3.2.0-37-virtual/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-37-virtual'
CC [M] /tmp/modconfig-U0gczv/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-U0gczv/vmci-only/driverLog.o
LD [M] /tmp/modconfig-U0gczv/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-U0gczv/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-U0gczv/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-37-virtual'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-U0gczv/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-U0gczv/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-U0gczv/vmci-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-U0gczv/vsock-only'
/usr/bin/make -C /lib/modules/3.2.0-37-virtual/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-37-virtual'
CC [M] /tmp/modconfig-U0gczv/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-U0gczv/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-U0gczv/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-U0gczv/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-U0gczv/vsock-only/linux/util.o
CC [M] /tmp/modconfig-U0gczv/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-U0gczv/vsock-only/driverLog.o
LD [M] /tmp/modconfig-U0gczv/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-U0gczv/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-U0gczv/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-37-virtual'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-U0gczv/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-U0gczv/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-U0gczv/vsock-only'
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface done
VM communication interface socket family done
Blocking file system done
Virtual ethernet done
VMware Authentication Daemon done
j'ai demandé sur 1 autre forum avec un membre du forum qui m'a proposé d'utiliser virtualbox à la place mais là aussi j'ai un probleme au lancement qui se bloque au debut du chargement.
la seule application qui fonctionne c'est virtual machine manager... et encore cela fonctionne pas toujours car j'ai essayé d'installer windows 7 et au moment du redémarrage de l'ordinateur après l'installation j'ai le droit à un écran bleu.
bref si vous pouvez m'aider car j'ai plus de solution.
merci.
Modération : merci à l'avenir d'utiliser les balises code (explications ici).
Merci de respecter les règles du forum, la taille des images est limitée.
Dernière modification par HAL (Le 29/05/2015, à 21:05)
Hors ligne