VMWare Workstation 10.0.1 Crash/Hang up

Similar Questions

• High resolution monitor and VMware Workstation, causing the system to hang

  I usually like VMware / WS... I used VMware / WS for many years with problems little / not serious - until recently.

  I'm under WS 6.5.1 on MS/Windows/XP/Pro/SP2 (host), and 2 guests of virtual machines: RHEL4 and MS/Windows/XP/PRO.

  Recently I bought a SAMSUNG T260 (1920 x 1200) high-resolution screen - I really like (I also used SAMSUNG monitors for many years with little / no serious problems).

  Currently, I am frequently (several times a day) see the two VMware / WS (all guests) and my XP any host COMPLETELY FREEZES up.  The only way out of this is perhaps a shutoff of the system and then restart.

  Needless to say it is (IMHO) a OFF THE CHARTS SERIOUS PROBLEM... with all fingers pointing to VMware / WS (TBD).

  Previously, I was running on a HP low resolution screen 1280 x 1024.  I can run for days/months/still without seeing the problem above.

  Also, I believe many/most/all lower resolution monitors is likely no other problems (be it).

  This is a 'system to freeze the scenario:

  1 pass to MS/Win/XP vm host RHEL (mode full-screen)

  2. press quickly on full screen non-plein screen

  3. If I do the above too fast my entire army system freezes up.

  Any body else see something like that?  Any ideas/help/suggestions will be appreciated.

  Mark

  PS/BTW - I've seen this problem originally under 6.0.3

  Are you running the latest drivers for your videocard host?  Video drivers are complex enough that they almost always end up containing pretty serious bugs and VMware video cards use is broad enough for us fires frequently these questions.  If upgrading the drivers didn't help not can you let us know:

  -What graphics card and cpu type is your host machine?

  -Don't you update of tools in two virtual machines?

  -What is your workload, particularly in the XP VM?

  -3D acceleration enabled in the XP VM is?

• Fatal error VMware Workstation: (svga) Exception 0xc0000005 (access violation) - VMware keeps crashing and our controls engineer was not able to understand, can someone help to solve?

  
  So I'm a summer at a paper factory and my boss, the engineer of controls has not been able to understand why VMware Workstation on a certain laptop hangs. I tried to create the log file I see posted the number of threads, but what I have is a compressed file which doesn't seem to have the info I've seen... or at least not in the same format. So I'm a complete newbie to VMware, and I searched the knowledge base and could not find any direct matches, at - it ready to help a newb? Really appreciate it and it would really help me as far as my training goes. TQ ahead!

  Just in case where I did maybe right I have attached two support files that I created.

  https://www.thebuddyforum.com/demonbuddy-Forum/65752-video-drivers-constantly-crashing-VMware-9.html

  I noticed that many people have the same problem with my computer when their computer/laptop has an AMD/ATI video card. Here's all I did and I got now work stations facing up and running for a week without any apparent problem

  1 back up your Virtual Machines a safe place and uninstall the workstation

  2 uninstall the AMD/ATI drivers

  3 reinstall the drivers

  4 reinstall the workstation

  5 follow the instructions below exactly to make a registry change

  a. Open regedit.exe and backup the registry, if you don't know how just google it is incredibly easy to make and the instructions are abundant so I don't post them here.

  b. open Notepad and enter the following text, make sure it is correct that the registry change can be risky, but if you enter the text exactly as it is below, you shouldn't have any problems because I have none. I take no responsibility if you have errors after this regedit so do at your own risk. Be sure and enter all the notebook INSTRUCTIONS below. DO NOT WRITE THE INSTRUCTIONS IN NOTEPAD IN YOUR NOTEPAD FILE. Everything below.

  NOTEBOOK INSTRUCTIONS

  Windows Registry Editor Version 5.00

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\DCI]

  "Timeout" = dword:00000014

  TdrDdiDelay "= dword:00000014".

  "TdrDelay" = dword:00000014

  "TdrLevel" = dword:000000

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]

  TdrDdiDelay "= dword:00000014".

  TdrDelay "= dword:00000014".

  TdrLevel "= dword:000000".

  END NOTEBOOK INSTRUCTIONS

  c. then navigate to the file and click on Save AS, when you arrive at the location you want to save the file, click the type box and change text to all documents, and then name the file regardless of your choice and add the .reg at the end. Once you have saved the file to its location and double click it to open it, windows will ask if you want to merge with the registry click Yes, windows will be also alert you on editing the registry and if you don't know that you want to try it go ahead and do it. So far, it has worked great for me.

  For more information about editing the registry, I used click here

• Fatal error of VMware Workstation

  Hello

  I have serious problems with VMware Workstation (version 9.02) and unique virtual machine to Windows 8. VMware Workstation is installed x 64 host Windows 8. This unique virtual machine crashes randomly with the following error message:

  

  I have other virtual machines also but I have no problems with them. First of all, I thought it was a physical disk error and I moved this virtual machine to another drive, but it did not help. I reinstalled VMware Tools and even created a new virtual machine and cloned this issue with Acronis Backup & Restore machine for this. This due to the machine crashes with the same error, but every time you start so things went even worse.

  Any ideas what to do with it?

  I attach a log file.

  Post edited by: Demuz

  I updated to VMware Workstation 10 and reinstalled the whole problematic virtual machine from scratch, but it still crashed at random several times a day with the same error.

  But now things look well so far.

  Yesterday, I changed a setting. I unchecked "Accelerate 3D Graphics" settings of the virtual machine (under the display settings). After that, the virtual machine crashed 0 times and I've been using a whole day! I have Nvidia display with the latest adapter drivers Win 8.1 x 64 installed on the host machine. I think drivers Nvidia has something to do with this virtual machine crashing, maybe...

  I started to suspect the display driver Nvidia after seeing this nvd3dumpx.dll appears more than once in the log file (this is VMware Workstation logfile ater the crash):

  2013-10 - 07T 18: 14:03.625 + 03:00 | vthread-14 | I120: backtrace [00] framework 0x1004ee48 IP 0x7ff8c64db9af params 0 x 1 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006da9af]

  2013-10 - 07T 18: 14:03.626 + 03:00 | vthread-14 | I120: backtrace [01] framework 0x1004eea0 IP 0x7ff8c655ee5c params 0xf2c680 0 0x116d5ee0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0075de5c]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [02] frame IP 0x7ff8c649c5f8 params 0 x 1 0x1004f6c0 0 0x7ff800000000 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069b5f8]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [03] framework 0x1004f6f0 IP 0x7ff8c649860d params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069760d]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [04] framework 0x1004f720 IP 0x7ff8c64b7f43 params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006b6f43]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [05] framework 0x1004f750 IP 0x7ff8c673c2cf params 0x7ff800000000 0 0 0 QueryOglResource + 0x1d5c2f [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b2cf]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [06] frame IP 0x7ff8c673c51a params 0 0x1004f780 0 0 0 QueryOglResource + 0x1d5e7a [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b51a]

  2013-10 - 07T 18: 14:03.630 + 03:00 | vthread-14 | I120: backtrace [07] frame IP 0x7ff8df941611 params 0 0x1004f788 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\KERNEL32. [DLL base 0x7ff8df940000 0x0001: 0 x 00000611]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: backtrace [08] frame IP 0x7ff8e08664ad params 0 0x1004f7b8 0 0 0 RtlUserThreadStart + 0x001d [C:\Windows\SYSTEM32\ntdll.dll base 0x7ff8e07f0000 0x0001: 0x000754ad]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: Msg_Post: error

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: fatal error [msg.log.error.unrecoverable] VMware Workstation: (vthread-14)

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + Exception 0xc0000005 (access violation) occurred.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.haveLog], a log file is available in "F:\VMware\Virtual Machines\vmware.log".

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + to collect data to be submitted to VMware support, choose "Collect load data" in the Help menu.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + you can also run the script 'vm-support' in the folder my computer directly.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

• VMware Workstation 11 crashes after installing VMware tools

  As the title suggests, VMware Workstation 11 crashes after installing VMware Tools with a guest Windows 7 x 64. I am running VMware on a host Windows 7 x 64. It happens every time I try to install the guest operating system. Attached to this post are all the newspapers that I could find that I thought would help solve the problem.

  
  

  Thank you

  Wila

  Hello again,

  Maybe the following post helps (where you installed Visual Studio)

  How to troubleshoot Workstation (vmui) - Access Violation Crash? How to troubleshoot Workstation Crash (vmui) - Access Violation? How to troubleshoot Workstation Crash (vmui) - Access Violation?

  --

  Wil

  As you may already know, VMware has just released a major update for 11 workstation (including VMware tools updated). Workstation now works almost perfectly. I don't have accidents since then. This means that I have was right in my post above. This is indeed nothing more than a BETA version of VMware buggy, lazy, masked as a "final". Wow, it looks like that a respectable company like this would not resort to such unethical practices. I mean that you would expect this kind of crap of a company like Electronic Arts, but VMware? Come on guys, you're better than this!

• VMware workstation, crashes when I try to create a new virtual machine

  Hello

  I never had this problem before, but I didn't create a new virtual machine in a very long time. Last time I created one was making Workstation 9 I think. Some time after the upgrade to Workstation 10 or 8.1 of Windows Update 1 it has started.

  In 10 Workstation running on Windows 8.1, I select the file > new Virtual Machine dialog coming upwards and in a few seconds crashes of VMware workstation and closes.

  So I checked the Windows event logs and find

  Warning "VMware Workstation to function properly, must be reinstalled after the upgrade to Windows."

  So, I upgraded from 10.0.2 to 10.0.3 and it uninstalled and reinstalled but I still get this warning.

  Followed by an error

  ***

  Journal name:	Application
  Source:	Application error
  Date:	15/08/2014 23:33:53
  Event ID:	1000

  Task category: (100)

  Level:	Error
  Keywords:	Classic
  User:	N/A
  Computer:	P7Win8MC

  Description:

  Name of the failing application: vmware.exe, version: 10.0.3.48389, time stamp: 0x539a4fb0

  Name of the failed module: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5

  Exception code: 0xc0000005

  Offset: 0x0003bece

  ID of the process failed: 0 x 1788

  Start time of application vulnerabilities: 0x01cfb902de541c11

  The failing application path: C:\Program Files (x 86) \VMware\VMware Workstation\vmware.exe

  Path of the failing module: C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll

  Report ID: 24d5effb-24f6-11e4-bedd-20cf30780548

  ***

  So I need help to track down what I am not sure what VMware paper to look to maybe see what is happening.

  Thank you

  Rainey

  Well, I found the problem.

  I looked in the UNK file and found a few ISO files wrongs tracks.

  I had mounted some ISO in the past and they have made the entry in this file of preferences such as "isoLocationMRUx".

  I'd change the leter this ISO file player so they could not be found as input, once I corrected the paths I can now create a new virtual machine.

  He is responsible for ion BONE the new virtual machine now.

• VMware Workstation 10.0.1 and Windows 7 VM crash on CentOS 6.5 host

  Just upgraded to 6.5 CentOS 64-bit (2.6.32 - 431.el6.x86_64). After the updates and reboot I launched VMware Workstation 10.0.1 as I normally and began my OpenVPN (Wheezy Debian) VM with all the problems. I then started my Windows 7 64-bit VM and the entire army what OS hangs and I have to reboot using the reset button.

  I was able to reproduce twice in a row. The Windows 7 VM seems to start fine and then when I type my credentials in and it starts to load the office which is when everything goes south and the host completely freezes.

  The Windows 7 VM has nothing too complicated installed in it. Some Epson software to start uTorrent and printer in network at startup. Steam does as well, but it is not auto-login or do anything really.

  I just did some testing of synthetic load and covered all 8 cores (much more than the usual load) up to 24 GB, 32 GB of RAM and 50% of CPU on the host computer and things remained stable. I thought that a second question could be RAM related because after a soft on boot the Windows 7 VM running I am to about 7 GB of RAM used on the host computer and from the WIndows 7 VM would put me over 8 GB, which resembled a number of nice where things might go wrong If it is RAM related.

  Log files:

  kdump(1): https://Paste.Fizi.ca/?f5c7c3e6945f8ce4#hPoN0VUJbPKA07hbDPWuE1D0e9FC7Ss8RNvF5Qv7yy0=

  vmware - 0.log: https://Paste.Fizi.ca/?05d42cd929bb5237#Zgbtlm7R+bZEHEOs5uSyA6Xin6FOOflWYWvNnHnxksM=

  Any ideas?

  Looks like I need to learn how to use the forum search tool.

  It is a dupe of VMware Workstation - 10.0.1 fails after the software update from RedHat-6.

• HELP me please, could not return to vm and crash of vmware workstation 7

  Help!

  I'm in deep problem with a virtual machine that does not work either... I'm disparate because I can't go to a previous snapshot.

  I have a machine t1500 dell with core i870, 16 GB of ram, nvidia quadro fx 512 mb graphics card, 500 gb hd, windows 7 pro 64-bit.

  In this machine wmware workstation 7 (latest version) is installed with autoprotect runs up to 10 daily snapshot.

  About 40 days, I converted two computers in vm... one with 32-bit vista and one with 32-bit xp.

  Every month the recent, everything works well... but yesterday all the vm was crushed because the space in my hd was full... so since the Snapshot Manager, I deleted some old snapshot.

  During the removal of a few shots, sometimes it shows me that he can't remove because the disc is always busy... but, but icon in the timeline of the Snapshot Manager went... go in the folder where I saved the files in vm, also failed in the Recycle Bin of windows.

  Once deleted, I try to turn it on again the vista 32 bit vm... aaaaahhhhhh, it does not start! and it remains pending mode... why!... If I try to take it back, all wmware workstation crash and I can only see a windows message error that vmware workstation has stopped working.

  Then I try to run the virtual machine with 32-bit xp and it work without any problem.

  Then I opened again snapshot manager and I try to use the function "go to...". "to recover a snapshot... ahhhhhh! nothing to do! It crash again!

  so I tried also to remove some files as described in this Ko... but not at all, it crash again!

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003846

  HELP ME, PLEASE! I have all my projects in this machine is very important... If I lose the...

  OK, so it looks like us (you) lost snapshot sw2 - 000010.vmdk, which was created between March 1 and March 2.

  What we need to do now is to repair the broken chain instant (because of the missing original sw2 - 000010.vmdk) and create a clone of this disc. Snapshots 000043 and 000044 contain no data and can be ignored.

  What we need to do is:

  1.) to repair the chain instant (link sw2 - 000009.vmdk to sw2 - 000006.vmdk)

  • SW2 - 000009.vmdk backup since we need to modify this file
  • Copy the sw2 - 000009.txt attached to the virtual machine file
  • Copy dsfi.exe to the virtual computers folder
  • run: 'sw2 - 000009.vmdk' dsfi.exe 512 800 'sw2 - 000009.txt.

  2.) creating a clone

  • find a drive with enough free space on the drive on which the clone will be created!
  • run: "C:\Program Files (x 86) \VMware\VMware Workstation\vmware - vdiskmanager.exe «r - t 0 \sw2clone.vmdk C:\vm\sw2\sw2-000042.vmdk»»
  • Create a new virtual machine and attach the vmdk cloned (using existing disk) instead of creating a new disc
  • Before you start the virtual machine, create a snapshot where the clone has some corrupted data and you must go back to for example to fix this virtual disk to a helper VM or open it with the disk mounter utility.
  • run the chkdsk command to check that the disc is ok

  André

• Workstation 7.1.1 crashes with a message"fatal error VMware Workstation «»

  Hardware info: Athlon Dual Core 4850e Processor, 4 GB of ram, Audigy 2Zs

  PCI, radeon HD3650 and many else if irrelevant...

  Linux hosts: Mandriva PowerPack 2010.1 x86_64.

  Until a few days ago, everything work lika a charm (what VM - linux or Windows - I used). After an upgrade alsa library (lib64alsa2 - 1.0.23 - 2.0.1), I can't use any computer virtual: whenever vmware wks hangs with error message box saying:

  < div > VMware Workstation unrecoverable
  error: unexpected signal (vcpu-0): 6. a log file is available in
  "/ home/giovanni/vmware/Mandriva Linux 64-bit 2010.0/vmware.log. Please
  ask for support and include the contents of the log file. To collect the
  Select the data to be submitted to VMware support, help & gt; Subject and click on
  "Collect data support. You can also run the script 'vm-support' the
  Record computer directly. We will respond on the basis of your
  right support. < / div >

  And I have to kill both inadmissible msgbox the zombie process vmx to try to run other virtual machines.
  

  
  

  
  

  
  

  Indeed, the newspaper attached you will find the offender: this is an error returned by a library alsa.
  

  ...
  11:36:30.472 August 27: vcpu-0 | PIIX4: PM Resuming suspended type 0 x 0.
  11:36:30.477 27 August: vcpu-0 | < span style = "make weight:" BOLD "" > ALSA lib pcm.c:870: (snd_pcm_sw_params) params - & gt; avail_min is 0: </span > 11:36:30.478 27 August: vcpu-0 | < span style = "police-weight:" BOLD "" > Caught signal 6 - tid 16052 </span > 27 August 11:36:30.478: vcpu-0 | SIGNAL: eip 0x7fae1a7ed925 esp 0x7fae190b9598 ebp 0x7fae1a8efcad
  11:36:30.478 August 27: vcpu-0 | SIGNAL: eax 0 x 0 ebx ecx edx 0xffffffffffffffff 0x7fff005c7eaf 0 x 6 esi 0x3eb4 edi 0x3ea9
  Aug
  27 11:36:30.478: vcpu-0 |         R8 r9 0x7fae190ba710
  0x65737341203a736d r10 0 x 8 r11 r12 0 x 3206 0x7fadaf6ee1b9 r13
  0x7fadaf6f73a0 r14 r15 0x7fae1a8efcad 0 x 937
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B9598: 0x1a7eef40 0x00007fae 0xaf6ee1b9 0x00007fad
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B95A8: 0x1a8f1354 0x00007fae 0x190b95d0 0x00007fae
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B95B8: 0 x 00000937 0 x 00000000 0x190b96c0 0x00007fae
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B95C8: 0x1a81e086 0x00007fae 00000018 0 x 0 x 00000030
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B95D8: 0x190b96d0 0x00007fae 0x190b95f0 0x00007fae
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B95E8: 0x1a8084e8 0x00007fae 00000030 0 x 0 x 00000030
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B95F8: 0x190b96e8 0x00007fae 0xa00159a0 0x00007fad
  11:36:30.478 August 27: vcpu-0 | SIGNAL: battery 7FAE190B9608: 0 x 00000075 0x00000000 0 x 00000075 0x00000000
  11:36:30.478 August 27: vcpu-0 | Backtrace:
  ...

  I found also some workaround solutions:

  (1) Elimination of the soundcard virtual machine configuration: the virtual machine starts OK, but no sound;

  (2) set the option "use the card his physique" in the "Edit parameters of the virtual machine - equipment - sound card" window to ' OSS: / dev/dsp ': the virtual machine starts OK, with sound.

  There is a way to have two sounds without OSS and Wks 7.1.1 emulation work?

  Hello

  I'm in charge of the ALSA library in Mandriva.

  I've updated the ALSA-lib in 2010,1 repository main/test last week. You seem to have installed this version of libalsa test and found a problem.

  Look no further, upstream validations that I took in the library contained a typo. I now took the patch followed upstream.

  I have now updated the libalsa available in main/testing 2010.1, so please update and let me know if that solves the problem.

  FWIW, if you notice a problem with the packages in the main/testing repository, you should probably first of all contact Mandriva via the bugtracker is a project upstream. The test repository is generally fine, but obviously problems pass through (in this case, I didn't test certain aspects that determine this problem for example).

  In addition, if you do want to use the main/test, it is usually best to wait the official updates are published once it has been tested by others.

  All the best, (and I hope the update fixes this problem).

  Col

• VMWare Workstation 7.01 crashes to access DVD or ISO

  Running Windows 7 64 bit. I installed VMWare Workstation 7.01 on my second drive. After installation, I tried to create a virtual machine with a *.iso or CD and it crashes. Anyone with questions? I have 8GB, active VT, Intel Core 2 Duo 3.5 Ghz. Here is a newspaper article from the debug:

  Debugging information:

  -

  ---

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

  BUGCHECK_STR: 0XD9

  Nom_processus: vmware - vmx.exe

  CURRENT_IRQL: 2

  LAST_CONTROL_TRANSFER: from fffff80002b5348d to fffff80002a7f600

  Atthached's journal

  Do you have a 'auditor/Reset"as indicated in the note to Vista users?

• VMware Workstation 7 crashes on Windows XP SP3

  Hello

  When I run VMware Workstation 7 on my pc, it freezes even if I do not run any machine.

  I can't close it, or end the task by the Task Manager (as it also crashes).

  I need to force close down using the power button.

  My pc specs are:

  Windows XP SP 3

  Intel Core 2 Quad Q9400 CPU @ 2 .66GHz

  2 GB of RAM

  Address extension physical (it freezes with and without PAE)

  I should mention that it worked in the past. It happened last week.

  Any idea?

  Dan

  Dan,

  have you installed anything new or updates (Windows update, virus scanning modes, rules of firewall,...)

  As a first step, try to disable the firewall and anti-virus. If this allows to check their records.

  André

• 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?

• Stuck ImageAssist - VMWare Workstation 12

  Hello world

  I'm having a problem where ImageAssist is blocked indefinitely at a point whenever I run it. I try to capture a Windows OEM 10 image created using VMWare Workstation 12. This post describes the exact steps I took:

  

  ImageAssist crashes and then to 32 of the stages of this process, as shown in the screenshot below:

  

  I actually left ImageAssist running overnight, and it never progressed beyond that point. The virtual hard disk is certainly big enough (60 GB) and I had no problems with the image at all. I even started from scratch and re-created the entire image to test again and ImageAssist still crashes at this exact point.

  Any help with this problem would be greatly appreciated!

  Hello

  Windows 10 does a lot of things during a "Windows Update". Running it in a virtual machine is a good idea as not getting driver updates. There are a few more things that occur that cause problems. The reason ImageAssist fails generally after an update is because the system can no longer be Sysprep. To check that you can browse manually to sysprep. C:\windows\System32\sysprep and run the executable. If sysprep fails, the AI tool will also fail. The biggest culprit is when the OS is upgraded. Windows 10 will upgrade to the latest version which won't allow sysprep run. Microsoft tells us that "Redstone" will not have this problem. You should also know that the 'Crush Saga of Candy' and 'Twitter' can install, causing sysprep to no longer work. I hope this helps... TK

• VMWare Workstation and Windows 7 64 bit

  Someone had problems with VMWare Workstation running Windows 7 64 bit? My computer hangs when creating the virtual machine guests. I also have VirtualBox running very stable with Windows 7. I was wondering if anyone has had problems? VMWare has a new version of 7 who suppose to be stable with Windows 7. I am skeptical. Your comments are welcome.

  "There is a time and place for that. The time is... Never. You can figure out the place on your own.

  I have no problem with VMware Workstation 7.0.1 build 227600 and Windows 7 Ultimate edition. It works like desingned.

• VMWare Workstation 12 and 18 of Linux Mint (Ubuntu 16.04) and vmware tools or open-vmware-tools

  I created a new virtual machine using VMWare Workstation 12.1.1 build-3770994 with a guest OS from Linux Mint 18 (which is built on top of Ubuntu 16.04). I have two monitors on my system, the two 2560 x 1440. I am unable to get this virtual machine Linux Mint 18 to cover all of my two monitors when I disable "Accelerate 3D graphics" in my vm settings, I get an error. I have another Linux Mint 17 VM running on the same VMWare Workstation 12 on the same host machine from Windows 10 and it is able to expand on my two monitors very well with "Accelerate 3D graphics" disabled, but he does not open-vmware-tools.

  I have read instructions telling me to install open-vm-Tools-Office in this guest operating system of Linux Mint 18. I did it. Then I restart the guest operating system. When starting, I can click on 'Enter full screen mode' in my menu of VMWare Workstation, and the guest OS has a monitor as expected. When I then click on "Cycle multiple monitors", I get the following error. "The virtual machine could not be changed to the selected screen layout. If you add a monitor to the host computer, you must turn off and turn on the virtual machine to use this monitor. »

  

  I can optimize my VM to automatic adjustment, only one of my two screens, but not both. I tried to uninstall and reinstall open-vm-tools, open-vm-tools-desktop and restart. I tried to use /vmware-tools-distrib/vmware-install.pl's original vmware tools and who does not work either.

  In my vmware.log, I get these two lines that occur when I get the above error.

  2016 07-12 T 15: 43:19.068 - 06:00 | MKS | I125: ToolsSetDisplayTopology: send rpcMsg = 1 DisplayTopology_Set, 0 0 2560 1440

  2016 07-12 T 15: 43:24.768 - 06:00 | MKS | I125: ToolsSetDisplayTopology: rpcMsg sending = DisplayTopology_Set 2, 0 0 2560 1440, 2560 0 2560 1440

  2016 07-12 T 15: 43:24.853 - 06:00 | vCPU-1 | I125: TOOLS of the call to DisplayTopology_Set failed.

  When I activate "Accelerate 3D graphics" with the configuration described above, I am able to use both of my monitors. Why is this the case?

  I think remember having to disable "Accelerate 3D graphics" in my Linux Mint 17 comments vm because it would crash randomly. I try to run this VM Linux Mint 18 with 3D acceleration and see if it crashes, but why is there a difference with spanning multiple monitors?

  Thank you.

  I didn't experience this problem for a few weeks. I don't have a definitive answer to my original problem.

  I installed Mate instead of cinnamon 3 to my MINT 18. Then, I created a new VM with Ubuntu Gnome 3 16.04 running as the OF. I did have problems with both approaches. I also tried using Firefox as my main browser instead of Chrome, as I read that Chrome can have problems of memory. It could be a combination of several of these changes that have allowed me to work without problems.

  Knowing what I know now, I think the move away from cinnamon 3 is what seems to have fixed my problems. I can certainly say that you use Firefox consumes less memory, as I can monitor the monitor system under Ubuntu. Chrome would eventually eat all my system memory, that I could see. The extent of the why? I'm not sure at this point.