Similar Questions

• Determine the version number and compilation of VMwareTools for VMware Workstation 7.0.1 build 227600

  I installed VMware Workstation 7.0.1 build 227600 on a Windows 7 64-bit machine.  Update the VMware Tools using the compiler, one of the instructions is:

  CP /mnt/cdrom/VMwareTools-x.x.x-xxxx.tar.gz /tmp/

  How can I determine the values of x in this case? When I tried the following command:

  CP /mnt/cdrom/VMwareTools-7.0.1-227600.tar.gz /tmp/

  I received the following error message:

  CP: cannot start ' / mnt/cdrom/VMwareTools-7.0.1-227600.tar.gz':

  No such file or directory

  The GuestOS I tried to run is:

  Release of centOS 5.2 (Final)

  I always use AutoComplete with tab to get the name of the file.

  Type:

  CP/mnt/cdrom/VM, and then press your tab key. He must complete the rest automatically.

  Then complete the order with the part of tmp folder location.

  Rick Blythe

  Social media specialist

  VMware Inc.

  http://Twitter.com/vmwarecares

  http://Twitter.com/vmwarekb

• Core upgraded to 4.0 on Centos 7 VMWare Workstation 11 won't build the virtual network device

  As shown in the topic, I have manually compiled kernel 4.0 for my installation of CentOS 7. After the installation of the kernel (in rpm mode, followed the instructions here: How to compile a Kernel - The Way CentOS ) installed all 3 rpm, kernel, kernel-headers and kernel-devel and then tried to start my installation of workstation with it leads to having to re - build the components (as usual)

  It does not, when it came to the compilation of the network management module. See attached log file that it generated.

  I also tried to uninstall, downloaded VMware-Workstation-Full - 11.1.0 - 2496824.x86_64.bundle and re-installed with the same result.

  Any help would be appreciated!

  aaand..., I fixed my only problem!

  Credit:

  https://wiki.archlinux.org/index.php/VMware

  just applied the 3.19 patch and He-voila!

• Need to know how to turn an old server Novell Netware 3.12 in a virtual machine on Vmware Workstation 5.5.3

  I'm a complete newbie to this. I have an old network of Novell server a 3.12 server and a ms - dos workstation running Novell client software. The underlying operating system on butterfly os server and workstations working MS - Dos 5.0. The material is old and fails at some point.

  I need to put everything in virtual machines. The ultimate goal is to run the Novell server in a vmware player on Windows Server 2003 and run the Novell Workstation in a vmware player running on a Windows XP workstation, so that the old, unreliable material can be discarded.

  My VMware software is VMWare Workstation 5.5.3 build-34685. The operating system host, such as reported by VMWare Workstation, Windows XP Professional 5.1.2600, Service Pack 3 is.

  I have a backup of the entire drive of the Novell server in a tar archive.

  I've never done anything like this before, and I have no idea how to even start.

  I'll need a lot of help.

  What I do first. ?

  3.12 is a version really old - I'm not even sure that it will work?

  .

  In any case - first try to create a 'new' installation of Netware 3.12 - if it works you can use as a reference.

  Try to set

  guestOS = "netware4."

  in the vmx file

  ___________________________________

  Description of the vmx settings: http://sanbarrow.com/vmx.html

  VMware-liveCD: http://sanbarrow.com/moa.html

• Unable to connect to the server of VMware Workstation

  I'm running ubuntu 13.04 (I know only is not officially supported at this time), however, when I navigate my browser to the virtual server (that I configured it using the port 10250), I get the following message is displayed:

  Access to the denied Web page

  Less

  You are not allowed access to the Web page at https://server:10250 /. You may need to connect.

  Error code: 403

  Status of it running:

  Andrew@server:~$ vmware - version

  VMware Workstation 9.0.2 build-1031769

  Andrew@server:~$ sudo service start vmware-workstation-server

  From Workstation Server: fact

  Andrew@server:~$ sudo netstat - apn | grep vmware

  TCP 0 0 0.0.0.0:10250 0.0.0.0: * LISTEN 7878/vmware-pass

  TCP 0 0 127.0.0.1:8307 0.0.0.0: * LISTEN 7878/vmware-pass

  TCP 0 0 0.0.0.0:902 0.0.0.0: * LISTEN 1703/vmware-authdla

  tcp6 0 0: 10250: * LISTEN 7878/vmware-pass

  UNIX 2 [ACC] STREAM LISTENING 37086 6047/vmware-unite-h/tmp/vmware-root/unity-helper-ipc-: 1

  UNIX 2 [ACC] STREAM LISTENING 11814 1991/vmware-usbarbi/var/run/vmware/usbarbitrator-socket

  UNIX 2 [ACC] STREAM LISTENING 42569 7878/vmware-pass/var/run/vmware/proxy-Web server

  UNIX 2 [ACC] STREAM LISTENING 42580 7878/vmware-pass/var/run/vmware/root_0/1371168951002706_7878/ha-nfc-fd

  UNIX 2 [ACC] STREAM LISTENING 42587 7878/vmware-pass/var/run/vmware/root_0/1371168951002706_7878/ha-nfcssl-fd

  [of] UNIX 2 CONNECTED FLOW 37087 6047/vmware-unite-h/tmp/vmware-root/unity-helper-ipc-: 1

  [of] UNIX 3 CONNECTED STREAM 35127 5534/vmware-tray

  [of] UNIX 3 CONNECTED STREAM 6047/vmware-unite-h 35819

  [of] UNIX 3 CONNECTED STREAM 43388 7878/vmware-pass

  [of] UNIX 3 CONNECTED STREAM 42564 1991/vmware-usbarbi/var/run/vmware/usbarbitrator-socket

  I get this message, if I run it on the local host, or if I run it on another machine.

  It's the only thing I see in syslog:

  Cat/var/log/syslog | grep vmware

  June 13 to 17:04:04 server/usr/lib/vmware/bin/vmware-hostd [8970]: password accepted for user andrew 127.0.0.1

  June 13 to 17:37:04 server/usr/lib/vmware/bin/vmware-hostd [8970]: password accepted for user andrew 127.0.0.1

  June 13 to 17:54:56 Server/usr/lib/vmware/bin/vmware-hostd [8970]: password accepted for user andrew 127.0.0.1

  June 13 to 17:55:28 vmauthd Server [4593]: vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.

  June 13 to 17:55:28 vmauthd Server [4593]: vthread-3 | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.

  June 13 to 17:55:28 vmauthd Server [4593]: vthread-3 | I120: Acquired the lock to/var/run/vmware/authd_14937f64dcf6846b509ee5705e0270eb

  June 13 to 17:55:28 vmauthd Server [4593]: vthread-3 | I120: unlocked lock for/var/run/vmware/authd_14937f64dcf6846b509ee5705e0270eb

  June 13-20:13:42 Server/usr/lib/vmware/bin/vmware-hostd [2275]: password accepted for the 127.0.0.1 root user

  13 June at 20:13:48 Server/usr/lib/vmware/bin/vmware-hostd [2275]: password accepted for the 127.0.0.1 root user

  13 June at 20:13:55 Server/usr/lib/vmware/bin/vmware-hostd [2275]: password accepted for the 127.0.0.1 root user

  June 13-20:14:02 Server/usr/lib/vmware/bin/vmware-hostd [2275]: password accepted for the 127.0.0.1 root user

  June 13-20:14:06 server named [1418]: fix error (network unreachable) 'my.vmware.com.edgekey.net/A/IN': 2600:1401:2:42 #53

  13 June at 20:14:09 Server/usr/lib/vmware/bin/vmware-hostd [2275]: password accepted for the 127.0.0.1 root user

  13 June at 20:14:29 / usr/lib/vmware/bin/vmware-hostd [2275]: last message repeated 2 times

  13 June at 20:14:29 / usr/lib/vmware/bin/vmware-hostd Server [7008]: password accepted for the 127.0.0.1 root user

  13 June at 20:15:02 / usr/lib/vmware/bin/vmware-hostd [7008]: last message repeated 3 times

  13 June at 20:15:04 the server kernel: [3056.496451] vmware-gksu [7037]: Segfault at 7f353f7591aa ip 00007f3547c38156 sp 00007fff95cf93d8 error 4 to libc - 2.17.so [7f3547bb0000 + 1be000]

  13 June at 20:15:05 Server/usr/lib/vmware/bin/vmware-hostd [7008]: password accepted for the 127.0.0.1 root user

  13 June at 20:15:07 the server kernel: [3059.388927] vmware-gksu [7085 or]: segfault at 7fc4c9f331aa ip 00007fc4d253b156 sp 00007fff04d21118 error 4 to libc - 2.17.so [7fc4d24b3000 + 1be000]

  13 June at 20:15:09 the server kernel: [3060.572580] vmware-gksu [7130]: Segfault at 7f68319561aa ip 00007f6835e04156 sp 00007fff7ce94c98 error 4 to libc - 2.17.so [7f6835d7c000 + 1be000]

  13 June at 20:15:09 Server/usr/lib/vmware/bin/vmware-hostd [7008]: password accepted for the 127.0.0.1 root user

  13 June at 20:15:14 Server/usr/lib/vmware/bin/vmware-hostd [7008]: password accepted for the 127.0.0.1 root user

  13 June at 20:15:17 the server kernel: [3069.298603] vmware-gksu [7548]: Segfault at 7f4d5bdeb507 ip 00007f4d64350156 sp 00007fff78106918 error 4 to libc - 2.17.so [7f4d642c8000 + 1be000]

  So I was wondering if anyone else has similar problems, I thought maybe it was the port that he was running on, and chrome doesn't, unfortunately, I can't find a way to change the port (as running with root, does not this either).

  I was confused Workstation Server with WSX.

• VMware® Workstation 8.0.4 you will only be able to run 32-bit nested vMs

  HI people,

  I did a forum search tried a few things suggested previously, but not joy.

  I get this error message

  Virtualized intel VT - x /EPT is disabled for this machine virtual esx
  you will only be able to run 32-bit nested vMs

  =================================

  The host OS is Windows Server 2008 Enterprise Edition, 64-bit 6.0.6002 Service Pack 2

  VMware® Workstation 8.0.4 build-744019

  
  The server is an HP ml350 g5 zeon 5420 cpu quad core server

  
  history esx 5i was installed on bare metal, I formatted and installed server 2008 x 64 sp2

  
  the bios is the last

  and these bios options are set

  Intel VT enabled,
  and no. execute activated too memory.

  ==============

  I understand that when these changes are made to the host should be recycled to power...

  
  This bios like many others after record changes usually f10, the changes are made and this server restarts

  is this normal?

  don't know what means VMware by power cycle

  I have disabled you options to see if I get an error that I saw the jpeg format

  (called) when the vt is disabled in the bios

  He talks about power cycle the host,

  I have the new option that was just to see if the vmworkstation was reacting to the bios actullaly.

  It has been.

  ============================================================

  
  all this should be good as the tool VMware-comments 64check - 5.5.0 - 18463

  reports

  This host is capable of running an operating system of 64 comments

  I ran it under this vmware product.when on my host Server 2008 x 64 sp2 enterprise.

  =============================

  I installed vmware workstion 8.0.4 on windows 2008 x 64 sp2 build-744019

  then I installed esxi 5 all right

  under custom options for the CPU, I chose Intel VT - x or Amd - V
  ==================================

  
  but when I opened esxi 5

  I get the error message #.

  Virtualized intel VT - x /EPT is disabled for this machine virtual esx
  you will only be able to run 32-bit nested vMs

  
  so I tried this

  
  Add the following line to C:\ProgramData\VMware\VMware Workstation\config.ini:

  hv.assumeEnabled = 'TRUE '.

  I also put this line

  hv.assumeEnabled = 'TRUE '.

  C:\Users\Administrator\AppData\Roaming\VMware\preferences.ini

  
  but still the same question after stop downs and restarts too

  I stop the physical server and restarts too

  =======================================

  = cpuid tool shows the processor is correct to because he had esxi 5 installed on bare metal before

  Information for processors
  -------------------------------------------------------------------------

  Processor 1 ID = 0
  Number of hearts 4 (max. 4)
  Number of threads 4 (max. 4)
  Name Intel Xeon E5420
  Codename Harpertown
  Specification Intel Xeon E5420 @ 2.50 GHz CPU < < < < < < < <
  Package (platform ID) Socket 771 LGA (0x6)
  CPUID 6.7.6
  Extended CPUID 6.17
  Core Stepping C0
  The 45 nm technology
  Basic speed 2500,0 MHz
  X FSB multiplier 7.5 x 333,3 MHz
  1333,3 MHz rated Bus speed
  2500 MHz frequency stock
  Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, > > > > > > > EM64T, VT - x < < < < < < < < < < < <
  Data L1 cache 4 x 32 KB, size 8-way line set associative, 64 bytes
  L1 instruction cache 4 x 32 KB 8-way line set associative, 64 byte size
  L2 cache 2 x 6144 KB, size 24 channels line set associative, 64 bytes
  FID/VID control Yes
  Range FID 6.0 x - x 7.5
  Max VID 1.225 V

  =========================================================
  My query

  These settimgs are supposed to be done in the two files above and in brackets ""

  must they be carried out before the esxi is actually installed in the workstation 8 or after.

  
  SO IMHO workstation notice 8 is misinterpreted something on my hardware.

  The ideas people?

  I have tried several combinations but no joy...

  
  Thank you
  chessguy

  chessguy wrote:

  @all

  Hmmmm...

  so with the options checked in workstation should it work,.

  (I tried it did not work)

  I don't know if I still need the lines edited in two places during the use of this option?

  and should it be done before that Esxi is installed in the workstation 8?

  or is the line of editing out of place now?

  Line editing is not relevant for your situation, since your CPU does not have the characteristics necessary for the virtualization of hardware support virtualized.

  If this server supports Esxi 5 bare metal because it was installed when I got it...

  First option get a processor that supports the corrrectly but if Intel specs are misleading where should I start... ???

  under kernel options for this doc of quickspecs ML350 g5 Server

  There are a variety of processors. any suggestions on one. ?

  http://h18000.www1.HP.com/products/QuickSpecs/12475_na/12475_na.html#core%20Options

  ========================

  None of these processors will help.  You need at least a CPU E55xx for HV virtualized.

  Option 2) now on this bare metal Esxi 5 with this current processor can I install 64-bit clients? (guess I'll try soon) but I would like to know... all ideas welcome...

  Yes, no problem.

  should I just particularly setttings in ESXi5?

  N °

  All the options for me to set up a laboratory for vsphere upward with this as is, or with the new processor?

  IMHO if not I could use 2 of these physical servers if I can get another assumption, that he would need to be the same?

  to try they full of features of vsphere. like HA, Vmotion etc.

  No, he would not have to be identical.  No matter what CPU Intel x 64 of this vintage, or later would be compatible with EVC (well well, with the exception of Atom).  You need only an identical processor for tolerance to failures.

• 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

• Problem with configure vmware workstation 6.5 with Ubuntu 9.04 64 bit latest kernel

  for the Intel-driving problem, I installed a new kernel for Jaunty.

  Normally, if you change the kernel, need new VMWARE-Workstation, but it does not work.

  I'm getting the following answer

  vmware sudo

  Login to /tmp/vmware-root/setup-26435.log

  ModInfo: vmmon module is not found

  ModInfo: module vmnet is not found

  ModInfo: module vmblock is not found

  ModInfo: vmci module is not found

  ModInfo: vsock module is not found

  ModInfo: vmmon module is not found

  ModInfo: module vmnet is not found

  ModInfo: module vmblock is not found

  ModInfo: vmci module is not found

  ModInfo: vsock module is not found

  ModInfo: vmmon module is not found

  ModInfo: module vmnet is not found

  ModInfo: module vmblock is not found

  ModInfo: vmci module is not found

  ModInfo: vsock module is not found

  ModInfo: vmmon module is not found

  ModInfo: module vmnet is not found

  ModInfo: module vmblock is not found

  ModInfo: vmci module is not found

  ModInfo: vsock module is not found

  ModInfo: vmmon module is not found

  ModInfo: module vmnet is not found

  ModInfo: module vmblock is not found

  ModInfo: vmci module is not found

  ModInfo: vsock module is not found

  ModInfo: vmmon module is not found

  ModInfo: module vmnet is not found

  ModInfo: module vmblock is not found

  ModInfo: vmci module is not found

  ModInfo: vsock module is not found

  Stopping VMware services:

  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/vmware-root/modules/vmmon-only '.

  do /lib/modules/2.6.31-999-generic/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. modules of

  make [1]: Entering directory ' / usr/src/linux-headers-2.6.31-999-generic'

  CC /tmp/vmware-root/modules/vmmon-only/linux/driver.o

  In file included from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:31:

  /tmp/vmware-root/modules/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait '.

  include/Linux/poll.h:67: error: previous declaration of 'poll_initwait' is here

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'LinuxDriverSyncCallOnEachCPU ':

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1423: error: too many arguments to function 'smp_call_function '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'LinuxDriver_Ioctl ':

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:2007: error: too many arguments to function 'smp_call_function '.

  make [2]: * /tmp/vmware-root/modules/vmmon-only/linux/driver.o error 1

  make [1]: * error 2

  make [1]: leaving directory ' / usr/src/linux-headers-2.6.31-999-generic'

  make: * http://vmmon.ko error 2

  make: leaving directory ' / tmp/vmware-root/modules/vmmon-only '.

  and the SETUP LOG

  Juli 28 19:20:55.486: app | Journal for VMware Workstation pid = 24193 version 6.5.2 = build = build-156735 option = output

  Juli 28 19:20:55.486: app | Host codepage = UTF-8 encoding = UTF-8

  Juli 28 19:20:55.486: app | Login to /tmp/vmware-root/setup-24193.log

  Juli 28 19:20:56.550: app | Extract the sources of the vmmon module.

  Juli 28 19:20:56.600: app | Module construction with the command: / usr/bin/make

  C - / tmp/vmware-root/modules/vmmon-only self-build SUPPORT_SMP = 1

  HEADER_DIR=/lib/modules/2.6.31-999-generic/build/include

  CC = / usr/bin/gcc = GREP / usr/bin/make IS_GCC_3 = no VMCCVER = 4.3.3

  and a box with this

  Error

  Failed to build the kernel module.

  Check the log file

  Does anyone know a Solution?

  Thank you

  Greetings

  Stefan

  -

  ---

  Computer laptop D830 DELL
  V9.04 Ubuntu Jaunty 64 bit

  
  

  Latest Version of VMWare Workstation

  -

  ---

  < / div >

  If you want to use the latest kernels that you should look for patches to update - look at this forum to find the last.

  http://communities.VMware.com/thread/221724?TSTART=0

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary

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

• VMWare Workstation bug in virtual Windows 7/Windows 8 (glitches).

  I have the black seeds on my virtual office.

  Is anyone know the solution, how to fix?

  Relocation of the comments system has not helped.

  Video card drivers reinstall also did not help.

  VMWare Workstation 8.0.3 build-703057; Speed up graphics 3d - active

  Host system: Windows 7 x 64, 8 GB of RAM, video of NVIDIA GTX 580 card 2 GB (301.32 nvidia driver)

  Comments system: Windows 7 x 86, 2 GB of RAM.

  Nothing in the changelog for the release of the pilot, but nvidia 301.42 WHQL drivers coming out seems to have made this problem go away for me on my GTX 680.

• VMWare Workstation fail to restart after suspend

  I'm using VMWare Workstation 7.1.1 build 282343 on a laptop Windows 7 Ultimate x 64 (8 GB). I run my VMS machines from a disk external eSata. My VMs are all Windows Server 2008 x 64. When I finished work I suspend the virtual machine, stop VMWare Workstation, then disconnect the eSata drive. It is, whenever I just restarted the VM, I get a message that is not possible to restore and I give myself the opportunity to "get rid" or retry - retry fails, so I have to throw. It's embarrassing because it then takes a boot for a long time the virtual machine from scratch.

  Any ideas how to solve this problem?

  disable USB-support for this virtual machine and start again

• VMware worksation 7.1.2 build 301548 disconnection windows 2008R2

  VMware Workstation 7.1.2 build 301548 with Windows 2008R2 64 bit with 2Geg of RAM

  ON Windows 2008R2 16 RAM Geg VT active Dungeon server disconnect every 15 min...

  Help, please.

  [email protected] wrote:

  keep disconnecting every 15 min

  This may seem a stupid question, but I'll ask anyway if only to assert that, as specific as you where, with what product VMware, OS, host and Guest OS you use however the rest, 'keep disconnect every 15 min,' is ambiguous.

  I'll assume you are referring to network connectivity, however, explicitly and precisely what is disconnected and what steps should you take to reconnect?

• Running 32-bit only VMWARE Workstation on Windows 7 64 bit?

  Hello.

  I have installed VMWARE Workstation 7.1.1 build 282343. When I look in the Task Manager, I see that the process vmware.exe * 32 runs only in 32 bits. The program is installed unter C:\Programs (x 86).

  What's wrong? Why it doesn't in 64 bit mode"?

  Thank you

  Michael

  Hello Michael,

  The hypervisor operates in 64-bit, the process you are looking at is the UI, not the hypervisor.

  Looking for a process called vmware-vmx, it is the process that runs of your virtual machine.

  There is not really much to gain for VMware with the 64-bit user interface, the important part is the hypervisor and runs as a 64-bit process.

  Hope this helps,

  --
  Wil
  _____________________________________________________
  VI Toolkit & scripts wiki at http://www.vi-toolkit.com

  Writer to the blog www.planetvm.net

  Twitter: @wilva

• VMWare Workstation stops in the middle of the night without user interaction

  Hello

  We conduct the following problem:

  We have a Windows Server 2008 hosting two Windows XP virtual machines using VMWare Workstation 7.0.1. Every few days/weeks, we find the host that is running but VMWare Workstation closed without error message either. I checked the log of the virtual machine and here is the interesting part. What can trigger such behavior?

  03:17:02.995 12 August: vmx | VMXVmdbCbVmVmxExecState: Change of State Exec asked the State suspended without reset, hard.

  03:17:02.997 12 August: vmx | CPT current = 0, asking 1

  03:17:02.997 12 August: vcpu-0 | Fact Sync monModules (1).

  03:17:02.997 12 August: vcpu-0 | CPT: monitor build mode 1

  03:17:03.737 12 August: vmx | CPT current = 1, asking 2

  03:17:03.737 12 August: vcpu-0 | CPT: generate 2 monitor mode

  03:17:03.737 12 August: vmx | CPT current = 2, asking 3

  03:17:03.765 12 August: vcpu-0 | Fact monModules (3) CPT.

  03:17:03.765 12 August: vcpu-0 | CPT: build mode monitor 3

  03:17:03.767 12 August: vmx | Progress - 1% (msg.checkpoint.saveStatus)

  03:17:03.767 12 August: vmx | Controlled in VMware Workstation 7.0.1 build 227600, Windows host

  03:17:03.785 12 August: vmx | BusMemSample: initPercent 3 75 hit 42106 checkpoint

  03:17:03.787 12 August: vmx | MM: Renamed E:\Virtual Machines\VM-DEVGW10G\564d914f-6520-6161-6d40-f23fec40dc4c.vmem.\VM-DEVGW10G.vmem

  03:17:03.787 12 August: vmx | 0% (none)

  03:17:03.787 12 August: vmx | Progress 1% (none)

  03:17:03.790 12 August: vmx | Progress of 2% (none)

  03:17:03.790 12 August: vmx | Progress of 3% (none)

  03:17:03.790 12 August: vmx | Increased by 4% (none)

  03:17:03.792 12 August: vmx | Progress of 5% (none)

  03:17:03.792 12 August: vmx | Increased by 6% (none)

  03:17:03.792 12 August: vmx | Advance of 7% (none)

  03:17:03.792 12 August: vmx | Progress of 8% (none)

  03:17:03.795 12 August: vmx | Progress of 9% (none)

  03:17:03.795 12 August: vmx | Progress of 10% (no)

  03:17:03.795 12 August: vmx | Increased by 11% (none)

  03:17:03.797 12 August: vmx | Progress of 12% (none)

  03:17:03.797 12 August: vmx | Progress of 13% (none)

  03:17:03.797 12 August: vmx | Progress of 14% (none)

  03:17:03.800 12 August: vmx | Progress of 15% (none)

  03:17:03.800 12 August: vmx | Progress of 16% (none)

  03:17:03.800 12 August: vmx | Progress of 17% (none)

  03:17:03.802 12 August: vmx | Progress of 18% (none)

  03:17:03.802 12 August: vmx | Progress of 19% (none)

  03:17:03.802 12 August: vmx | Advance of 20% (none)

  03:17:03.805 12 August: vmx | Progress of 21% (none)

  03:17:03.805 12 August: vmx | Progress of 22% (none)

  03:17:03.805 12 August: vmx | Progress of 23% (none)

  03:17:03.807 12 August: vmx | 24% (none)

  03:17:03.807 12 August: vmx | Progress of 25% (none)

  03:17:03.807 12 August: vmx | Increased by 26% (none)

  03:17:03.810 12 August: vmx | Progress of 27% (none)

  03:17:03.810 12 August: vmx | Progress of 28% (none)

  03:17:03.810 12 August: vmx | Advance of 29% (none)

  03:17:03.812 12 August: vmx | Advance of 30% (none)

  03:17:03.812 12 August: vmx | Rise by 31% (none)

  03:17:03.815 12 August: vmx | 32% (none)

  03:17:03.815 12 August: vmx | Progress of 33% (none)

  03:17:03.817 12 August: vmx | Advance of 34% (none)

  03:17:03.817 12 August: vmx | 35% (none)

  03:17:03.820 12 August: vmx | Increased by 36% (none)

  03:17:03.820 12 August: vmx | Progress of 37% (none)

  03:17:03.822 12 August: vmx | 38% (none)

  03:17:03.822 12 August: vmx | Progress of 39% (none)

  03:17:03.825 12 August: vmx | Progress of 40% (none)

  03:17:03.825 12 August: vmx | 41% (none)

  03:17:03.825 12 August: vmx | 42% (none)

  03:17:03.827 12 August: vmx | 43% (none)

  03:17:03.827 12 August: vmx | 44% (none)

  03:17:03.827 12 August: vmx | Progress of 45% (none)

  03:17:03.830 12 August: vmx | 46% (none)

  03:17:03.830 12 August: vmx | 47% (none)

  03:17:03.832 12 August: vmx | 48% (none)

  03:17:03.832 12 August: vmx | 49% (none)

  03:17:03.832 12 August: vmx | Advance of 50% (none)

  03:17:03.835 12 August: vmx | 51% (none)

  03:17:03.835 12 August: vmx | Progress of 52% (none)

  03:17:03.837 12 August: vmx | Progress of 53% (none)

  03:17:03.837 12 August: vmx | 54% (none)

  03:17:03.837 12 August: vmx | Progress of 55% (none)

  03:17:03.840 12 August: vmx | 56% (none)

  03:17:03.840 12 August: vmx | Progress of 57% (none)

  03:17:03.842 12 August: vmx | Progress of 58% (none)

  03:17:03.842 12 August: vmx | 59% (none)

  03:17:03.842 12 August: vmx | Advance of 60% (none)

  03:17:03.845 12 August: vmx | 61% (none)

  03:17:03.845 12 August: vmx | Progress of 62% (none)

  03:17:03.847 12 August: vmx | 63% (none)

  03:17:03.847 12 August: vmx | 64% (none)

  03:17:03.850 12 August: vmx | 65% (no)

  03:17:03.850 12 August: vmx | Progress of 66% (none)

  03:17:03.850 12 August: vmx | 67% (none)

  03:17:03.852 12 August: vmx | 68% (none)

  03:17:03.852 12 August: vmx | 69% (none)

  03:17:03.855 12 August: vmx | Progress of 70% (none)

  03:17:03.855 12 August: vmx | 71% (none)

  03:17:03.857 12 August: vmx | 72% (none)

  03:17:03.857 12 August: vmx | 73% (none)

  03:17:03.857 12 August: vmx | 74% (none)

  03:17:03.860 12 August: vmx | Progress of 75% (none)

  03:17:03.860 12 August: vmx | 76% (none)

  03:17:03.862 12 August: vmx | 77% (none)

  03:17:03.862 12 August: vmx | 78% (none)

  03:17:03.862 12 August: vmx | 79% (none)

  03:17:03.865 12 August: vmx | 80% (none)

  03:17:03.865 12 August: vmx | 81% (none)

  03:17:03.865 12 August: vmx | 82% (none)

  03:17:03.867 12 August: vmx | 83% (none)

  03:17:03.867 12 August: vmx | Progress of 84% (none)

  03:17:03.867 12 August: vmx | 85% (none)

  03:17:03.870 12 August: vmx | 86% (none)

  03:17:03.870 12 August: vmx | 87% (none)

  03:17:03.870 12 August: vmx | 88% (none)

  03:17:04.085 12 August: vmx | GuestRpc: Reset of channel 0 (toolbox)

  03:17:04.085 12 August: vmx | GuestMsg: Channel 0, can't unpost because the previous post is already completed

  03:17:04.085 12 August: vmx | GuestRpc: Channel 0 reset.

  03:17:04.085 12 August: vmx | GuestRpc: Reset the 3(toolbox-dnd) channels

  03:17:04.085 12 August: vmx | GuestMsg: Channel 3, cannot unpost because the previous post is already completed

  03:17:04.085 12 August: vmx | GuestRpc: Channel reset 3.

  03:17:04.132 12 August: vmx | Progress at 89% (none)

  03:17:04.152 12 August: vmx | 90% (none)

  03:17:04.172 12 August: vmx | 91% (none)

  03:17:04.190 12 August: vmx | 92% (none)

  03:17:04.212 12 August: vmx | 93% (none)

  03:17:04.235 12 August: vmx | 94% (none)

  03:17:04.257 12 August: vmx | 95% (none)

  03:17:04.280 12 August: vmx | 96% (none)

  03:17:04.300 12 August: vmx | Progress of 97% (none)

  03:17:04.317 12 August: vmx | 98% (none)

  03:17:04.335 12 August: vmx | Progress of 99% (none)

  03:17:04.365 12 August: vmx | 100% (no)

  03:17:04.452 12 August: vmx | Progress of 101% (none)

  03:17:04.490 12 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1875, success = 1

  03:17:04.490 12 August: vmx | VIX: : VMAutomation: ignoring ReportPowerOpFinished because the VMX stops.

  03:17:04.737 12 August: vmx | Stopping VCPU threads...

  03:17:06.490 12 August: mks | End MKSRole pseudocalls, the State was 1

  03:17:06.490 12 August: mks | MKSHostOps_Exit3D: 1: 0

  03:17:06.490 12 August: mks | Fate of MKS Async thread

  03:17:06.490 12 August: vmx | VIX: [2684 mainDispatch.c:915]: VMAutomation_PowerOff: power off the power.

  03:17:06.602 12 August: vmx | Application of TOOLS received in VMX to set the 'enableDnD' option - & gt; '0'

  03:17:06.602 12 August: vmx | Application of TOOLS received in VMX to set the option "copypaste" - & gt; '0'

  03:17:06.602 12 August: vmx | Application of TOOLS received in VMX to set the option "copypaste" - & gt; '0'

  I know that this is perhaps a very obvious thing to check, but sometimes, they are the most neglected

  The server reboots after updates windows for example? or is there no idea in the windows event log to moor with vmware logs?

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful