Impossible to run virtual machines (could not open/dev/vmmon)

Similar Questions

• VMware Workstation 9: could not open/dev/vmmon: no such file or directory

  I'll have a plethora of problems installing and get VMware Workstation 9 (9.0.2 build-1031769) to work on Ubuntu 13.04 (kernel 3.8.0 - 26-generic).

  I experienced exactly the same process on my laptop and it works perfectly, while on the desktop, it seems that everything breaks. Could someone give me some kind of help / advice on how I can do to get this working. I tried full uninstall / reinstall of the software, headers of the kernel, kernel images, different kernels, patches here on fresh installs of everything I can think of. Here are the issues I encounter in the order of importance (or so I think):

  (1) whenever I try to open my new (and virtual) machine, I get the error sequence of:

  "Could not open/dev/vmmon: no such file or directory. " Please make sure that the "vmmon" kernel module is loaded. '--> 'Failed to initialize the device monitor. "->" cannot change the power state of VM: could not find a valid peer to connect to '

  
  

  (2) every time I try to run the following command to configure the modules on a completely fresh setting (reinstalled kernel, vmware) I get the following output:

  sudo modconfig vmware - console - install-all

  Stopping VMware services:

  Demon of authentication makes VMware

  VM communication interface socket family is

  Virtual machine communication interface is

  Virtual machine monitor makes

  File system is blocking

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmmon-only '.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driverLog.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/hostif.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/apic.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/comport.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/cpuid.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/hashFunc.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/memtrack.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/phystrack.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/task.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/vmx86.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/vmcore/moduleloop.o

  LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmmon-only/vmmon.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  CP f vmmon.ko. /... vmmon.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  Using 2.6.x kernel build system.

  make: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only»

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/hub.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/userif.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/netif.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/bridge.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/filter.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/procfs.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac_compat.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetEvent.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetUserListener.o

  LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmnet-only/vmnet.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  CP f vmnet.ko. /... vmnet.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmblock-only.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/block.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/control.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/file.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/filesystem.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/inode.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/stubs.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/module.o

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:285: warning: assignment of incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:296: warning: passing argument 1 of the "putname" incompatible pointer type

  include/Linux/FS.h:2052: Note: expected ' struct filename *' but argument is of type ' char *'

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/super.o

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/inode.c:49: warning: initialization from incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:38: warning: initialization from incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a cast

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'

  LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  Warning: "putname" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmblock-only/vmblock.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  CP f vmblock.ko. /... vmblock.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmci-only.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/vmciKernelIf.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciContext.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDatagram.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDoorbell.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDriver.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciHashtable.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciEvent.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQPair.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQueuePair.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciResource.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciRoute.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/driverLog.o

  LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmci-only/vmci.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmci-only/vmci.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmci-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.

  CP f vmci.ko. /... VMCI.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vsock-only '.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/af_vsock.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notify.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notifyQState.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/stats.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/util.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/vsockAddr.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/driverLog.o

  LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vsock-only/vsock.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vsock-only/vsock.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  CP f vsock.ko. /... vsock.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  Starting VMware services:

  Virtual machine monitor failed

  Virtual machine communication interface failed

  Family of VM communication interface socket failed

  File system is blocking

  Virtual Ethernet failed

  Demon of authentication makes VMware

  Cannot start the services

  (3) I often get the Ubuntu "this program has planted" messages on "/ usr/lib/vmware-installer/2.1.0/vmis-launcher" "' (this message of crash always occurs when you run the"vmware-modconfig"above command on a new installation.

  (4) at different times during Assembly and have VMware workstation on my system I get Ubuntu hangs on "/ usr/lib/vmware/bin/appLoader" and even "/ bin/su" (especially when you are trying to install - su NEVER blocks anywhere else).

  Thoughts / ideas on what is happening on earth / what could have caused this all go so downhill / how to go about fixing?

  Thank you

  Solved.

  The problem is that for another program I used gcc - 4. 4 instead of later. Restore the (by update-alternatives - config ) for gcc, g ++ and CPC - bin.

  Not a very graceful exit to have a version not valid I would say, maybe some sort of basic check could be added to ensure that the correct versions are present?

• "Could not open/dev/vmmon: no such file or directory." Please make sure that the "vmmon" kernel module is loaded. »

  I installed vmware Player on a linux Open Suse (32-bit), the supplied file .bundle machine. It worked very well, and I could load my file of virtual machine very well. Then, my machine had a random failure. When it restarts, I could no longer use my virtual machine, always get the error:

  "Could not open/dev/vmmon: no such file or directory."

  Please make sure that the "vmmon" kernel module is loaded. »

  I look in / dev, and of course, there is no vmmon. I see a lot of archived messages stating that you must run the script ' vmware - config.pl '... (more specifically the following link: ) http://blog.solutionperspectivemedia.co.UK/?p=6 )

  but I do not have it. It seems that maybe it was a part of the installation (no-bundle) more old?

  What should I do? Is this a known problem, as indicated in this Web site? Or random failure caused something? I'm quite confused.

  Have you tried to uninstall as root? Otherwise I think it won't work.

  With respect to your original problem, I got it, too, and that's what I did:

  sudo mv/usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

  vmware-modconfig--console--install-all--appname sudo = 'VMware Player' - icon = 'vmware-player '.

• Error when you try to run vmplayer 7.1.2 on CentOS 7-"could not open/dev/vmmon: no such file or directory."

  I am looking for working on CentOS 7 vmplayer.  I ran the .bundle as root and then when I try to create a VM it fails on with the error "cannot open/dev/vmmon: no such file or directory."

  CentOS 7 is not supported?

  In my research, I did not see any fix.  I think he just doesn't...

  vmplayer 7.1.2 works for me on CentOS 7.

  The problem was the secure boot must be disabled in the BIOS.

• VMWare Fusion 6.0.5: Could not open/dev/vmmon: no such file or directory.

  I've been running VMWare Fusion 6 on my MacBook Pro with the Mavericks for quite awhile.  I just got a Mac Mini with Yosemite and I want to copy one of my virtual machines of the MBP to the Mini.

  I tried to just copy the vmware.vm of the MBP to the Mini but when I open it and try to start it I get the following errors:

  • Unable to open/dev/vmmon: no such file or directory.

  Please ensure that the "vmmon" kernel module is loaded.

  • Could not initialize the surveillance apparatus.
  • Internal error

  I also tried to import the vmware.wm file, but it is always grayed out.

  How can I copy a virtual machine from one Mac to another?

  Hi atj777,

  Are you absolutely certain that this is Fusion 6.0.5, you're there?  Fusion 6.0.4 and earlier would fail on Yosemite the way you describe.  There are many other possible causes of the same error message, but it would be the first thing I would check a second time.  (My apologies if you have already verified!)

  What version of Yosemite are you running?  10.10.2?

  It can also be useful to restart your Mac to see if that helps... sometimes he does.

  To answer your question directly: simply copy the ".vmwarevm" package on the whole should be enough.  The message you see is a generic merge error and has nothing to do with the copy process.

  See you soon,.

  --

  Darius

• Get ' could not open/dev/vmmon: no such file or directory.' error

  Im trying to open VMware Fusion Pro 5.0.5 on my Mac, and it continues to give me the following errors in the order:

  1.

  2.

  3.

  I would be extremely grateful if anyone knows how I can solve this problem and access my fusion I need emergency to use some software it contains.

  I did a "collect information of technical support" (attached), but unfortunately this means absolutely nothing to me. Post edited by: Carla15

  Hi Carla15and welcome to the VMware communities!

  Your Mac has been upgraded to Yosemite (OS X 10.10), but 5 merger is too old to be compatible with Yosemite.  You must upgrade to 6.0.5 Fusion or Fusion 7 for compatibility with Yosemite.

  See you soon,.

  --

  Darius

• How this problem fixed?  Virtual machine could not be loaded: it could be missing, corrupted, or inaccessible

  Can anyone help. ?  whenever I run the .vmx file. the following message appears.

  "Virtual Machine could not be loaded: it could be missing, corrupted, or inaccessible" it was working fine... its vmx of windows 2003 server. all of sudden this message began to appear. There were a few changes to group policy by the admins of LAN.  What is the reason. I always run this through administrator. the password also changed as a result of the Group Policy update... pls tell me its urgent to run .i have re-change the password of admin to the older one, but for the same msg again again...

  some details are

  Welcome the OS is Windows XP

  Player version == VMware-player - 1.0.3 - 34682

  Guest operating system you want to load?  Is Windows 2003

  The guest was able to run successfully before == YES

  I've attached the VMX file also.

  Please it damn importatnt and urgent... .all my quote UAT is there... and no where else...

  The output of vmware.log using perl vmxRecover.pl etungscript is attached.

  I quickly looked on it and looks like it should work for me :)

  --

  Wil

  _____________________________________________________

  Visit the new VMware developers at http://www.vi-toolkit.com wiki

• In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

  Hello

  Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

  I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke"»

  I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

  FYI: we have changed the domain 3 months ago, but it has never be a problem.

  I have google and search several Forum. So far, I tried to:

  -restart the service vmware-auth as an administrator

  -launch vmware.exe administrator

  stop/start the vmx86 service

  -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

  -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

  -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)
  

  -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

  -Open the virtual machine using the drive == > does not work either.

  This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

  Even a newly created WM (boneless), unbootable! :-(

  *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

  I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

  Of after what I saw (and what little I understand), it's as if the CPU is not detected?

  The two newspapers have this line:

  FeatureCompat: EVC masks:

  but the non-working goes - we with

  Module CPUID initialization failed.

  While working it display information on CPU (hostCPUID name / family / type... etc...)

  Any idea is welcome.

  I'll answer me to my problem!

  A lot of research to this knowledge.

  In summary: don't mess with the processor affinity... or keep it in mind!

  Response to distinguish:

  I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

  This is the reason of *my* question. Perhaps it might help someone else?

  TIPS:

  For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

  Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

  ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

  15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

  LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

  Post edited by: cbiero (LSB and MSB...)

• The specified file is not a virtual disk: could not open the vmdk

  I am running vmware player 5.0.1 for windows 7 x 64. I rebooted the host after the suspension of my VM, and when I try to play the virtual machine after the reboot, I get the error message in the topic. I have attached a screencap of the error, my vmware.log and the it refers to a vmdk file. I did some research on the knowledge base and he speaks using virtual disk (vmware-vdiskmanager) Manager to regenerate the vmdk file, but I don't seem to have this program. -What for vmware server/workstation? Can I download it somewhere? Is there an easy fix? My drive is stored in several files that I have to rebuild all of them?

  Thanks in advance for anyone who can help...

  The "EVANS - WHS 2011-0.vmdk" file is a virtual hard disk of metadata, which is a pointer to a physical hard disk and you are not supposed to suspend, snapshot, a Virtual Machine that uses a raw disk such as this and the physical drive could trash making!

  The only thing I can say without further information is to delete and add back.

• Virtual machines will not open

  So far I'm not having a good time with the merger. I created two virtual machines. In one, I imported my Parallels VM XP. In the other, I installed Windows 7 Pro, and then installed my genealogy software and copied into the database. Yesterday, I had both open, comparing the two databases to make sure that I had copied later. I had to stop, so I suspended the two virtual machines and leave the merger.

  Today, when I came back, I took the W7 machine. He refused to come and basically crashed. I started again. He came, seemingly OK initially. I went to a different record in the data, and that seemed to work. But I had a problem with my wireless keyboard, so I plugged in a USB keyboard.

  At this point, the W7 machine responds more completely, the keyboard or mouse. Shortly, it crashed. And when I try to restart it, it comes up saying "internal error." Initially, there was some message not to seek a process to connect to, but now I get the message "Internal error" (after several attempts). The evidence of what can happen? What toast VM and I have to start?

  Either way, the XP VM will be no more back from suspension. It causes the Fusion go out of order, and I have to force it to quit.

  So, for the moment, nothing works. I am impressed! Can anyone offer help? I'm about to abandon my trial and return to Parallels.

  allenwatson wrote:

  So, for the moment, nothing works. I am impressed! Can anyone offer help? I'm about to abandon my trial and return to Parallels.

  It might be useful to take a step back and cringe before sprint with Fusion.  You might be an expert, but we do not know what kind of Mac you have (speed, carrots, RAM), the amounts assigned to the virtual machines.  All this can affect the interaction with the machine runs especially 2 or several virtual machines at the same time.

  First of all, good Center seems, I suggest a reboot for the update of Mac OS X in the level of play.  Set a virtual computer at a time.  From XP, if the virtual machine is suspended you can remove suspended RAM State (or the saved state) then restart the virtual machine, it will go through the normal boot process and not repeated from the suspended state.  For this, I recommend to locate the beam of the XP VM as on the collection of information for VMware Fusion and remove the .vmss file.  To do this, before launching VMware Fusion.  If so do it separately for the VM and Win 7 as well.  Then start VMware Fusion and exercise your XP VM.  Once you think it doesn't, stop the XP VM.  Then, start the VM 7 Win and see if it still gives you an error.  If so, see details here indicated such in the Backgrounder Gathering.  If this isn't the case, exercise the VM Win7 run alone to see if it is stable.

  Once the two virtual machines are independently stable, read choose the right virtual computer settings to make sure that each virtual machine settings are tuned to your needs.  If you intend to run 2 or more virtual machines, special attention to the sum total of the use of the RAM compared to what is the surplus for OS X and its applications.

  Hope this helps,

  Richard

• Virtual machines will not work after missing 6.5 upgrade, / dev/vmmon

  I recently updated my build-126130 VMware Desktop 6.0.5 to 6.5.1 and now none of my virtual machines are running.  When I try to start them, I get the following error:

  "Could not open/dev/vmmon: no such file or directory."

  Please make sure that the "vmmon" kernel module is loaded. »

  When I looked in the directory/dev, there is no listed vmmon device.

  From everything I've read, upgrade worked very well.  The application starts without any apparent problems.  I suspect since all my virtual machines worked really well until I restarted the laptop, there is a problem loading the kernel module.

  I'm under openSUSE 11.0.

  I liked all the ideas that everyone has.

  Kind regards

  Jim

  Hello

  It is sometimes a problem with the new GUI to create modules from the kernel, which is most likely what you're hitting right now.

  Have a look here:

  http://www.VI-Toolkit.com/wiki/index.php/Build_host_vmware_kernel_modules

  This might help a little, the notes are not yet specific SUSE. If the script Christmas help and you had to do something different on SUSE then I would appreciate it if you add a note to this topic.

  Thank you

  --

  Wil

  _____________________________________________________

  Visit the new VMware developers at http://www.vi-toolkit.com wiki

• How to solve the problem of VMWare Workstation 8 - unable to open/dev/vmmon

  Initially, I had this problem in March 2011 after installing VMWare Workstation 7 on a lab machine 5.7 RHEL and attempt to boot an image I know was good and should work. .  Someone else fixed the problem for me - I think they had to install a new/different libraries (vmmon.o and vmnet.o for vmware).  However, I find no information detailing what has been done to solve the problem.

  I see the same error on the same machine after upgrading to VMWare Workstation 7.0 for VMWare Workstation 8.0.

  1 here are the mistakes I see:

  a. "Could not open/dev/vmmon.

  b. "failed to initialize the surveillance apparatus.
  c. "cannot change the power state of VM: cannot find a valid peers to connect to.

  Also, when I run the stop etc/init.d/vmware, then run /etc/init.d/vmware start, I see that the State of "Virtual Machine Monitor" is DOWN.

  
  2 here is the information on VMWare Workstation:

  VMWare Workstation 8.0.1 build 528992

  3 here is the RHEL uname - information for the host:

  2.6.18 - 274.7.1.el5xen Linux #1 SMP xxx.xxx.xxx kills Oct 17 12:06:22 EDT 2011 x86_64 x86_64 GNU/Linux
  Release of RedHat Enterprise Linux Server 5.7 (Tikanga)

  The problem could be that the version of vmmon.o and vmnet.o that comes by default with vmware does not work with linux kernel version I have on my system.  I think I need to build a new vmmon.o and vmnet.o on my particular 5.7 RHEL.

  I found that to build a new version of vmmon.o you Executive vmware - config.pl.  I have not just on my machine, and I was not able to find on the internet.

  Here is the version of vmmon.o (for RHEL 5) that I have installed on my machine:
  /usr/lib/VMware/modules/binary/BLD-2.6.18-8.EL5-x86_64smp-RHEL5/objects/vmmon.o

  Here is the version of rhel5 I use:
  2.6.18 - 274.12.1.el5xen
  It is possible that the vmmon.o using bld - 2.6.18 - 8.el5 - x86_64smp-RHEL5 is not compatible with the kernel 2.6.18 - I 274.12.1.el5xen.

  Please help me find vmware - config.pl so I can build my own vmmon.o and vmnet.o

  do not use a kernel XEN enabled when you install Workstation

• Virtual machine does not start after restoring from Time Machine to the new Imac

  I got my IMac replaced by Apple, after that they could not fix the old one.  They did a full restore from a Time Machine backup.  The virtual machine does not open now.   When I navigate to the file to try to open the virtual machine at the VMware logo in the bottom right of the icon displayed with large yellow exclamation appears on the icon?  Anyone encountered this problem before.  I'll take the Imac in Saturday if I can not solve.  The machine has the same size as before.  There are a few aspects of sharing with the Mac application miss me?

  According to the MacVirt.vmdk folder, you have the right number of segments of shared disk so you should be able to create a new VM by pointing to the disc in the new VM Wizard by pointing to the MacVirt.vmdk file.

  Note: After you create the new Virtual Machine, I would not suggest the Virtual Machine to stop, pause and close merge and then move all *.vmdk files in the package of the virtual machine, and then manually change the computer configuration files virtual .vmx and change the path to a little to view the MacVirt.vmdk file.  In this way, everything is in one package and is easier to maintain.

• Impossible to turn on the virtual machine with the following error: could not open the disk ' / path/to/vmdk-0001.vmdk ' or one of the Flash disk it depends on. Reason: Broken pipe.

  After the movement of virtual machines in VmWare Server 2 for ESX 4i, I get this error when you try to start the virtual machine:

  Impossible to turn on the virtual machine with the following error: could not open the disc

  "/ path/to/vmdk-0001.vmdk" or one of the Flash disk it depends on.

  Reason: Broken pipe.

  Anyone's idea what is the problem here?

  How did you move virtual machines?

  Did you use the converter (https://www.vmware.com/tryvmware/?p=converter)

  Otherwise try converter

• Could not open the virtual machine

  I used the customer convertor to create this virtual machine from one which works well on ESxi.  When I try to open on Win7-64 machines running vmplayer 3.1.4 I get the following error:

  Could not open the virtual machine: file "D:\Data\VM Machines\WW S2008_32\WW S2008_32.vmx 10_1 10_1" line 1: syntax error.

  Any ideas?

  "" "WW 10_1 S2008_32.vmx.zip" attached file contains the "WW 10_1 S2008_32.vmx" file created under VMware Player 3.1.4 and was then modified to reflect the values of parameter that you might want to stay the same as uuid etc.  Start VMware Player and then check the settings before running the virtual machine.