Similar Questions

• 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

• I have a problem starting up a Windows XP Pro Machine virtual Windows 8 host system (which has VMware Workstation 10.1).

  I am new to the virtual machines.  For several months I've been running a Windows XP Virtual Machine in an old machine of Windows 7 with VMware Workstation 7.0.  The hard drive is having some problems at times, so I thought that I could move the virtual machine on a new computer that has an OS 8.1 Windows and VMware Workstation 10.  For example, on the Windows 7 machine, I copied the directory with all the * .vm files and pasted into the machine to Windows 8. But when I tried to start VMware Workstation 10 in Windows 8 machine, I got the message "this virtual machine policies are too old to be run by this version of VMware."  I went to the knowledge base and used the solution described here: I've deleted the lines of three 'policy' of the .vmx file and added the suffix .ancien to the .vmpl file, which actually disabled.  Now, when I try to start the virtual machine, the black screen appears with the VMware logo in the Center and everything seems fine, but Windows XP starts.  And logo VMware guard churning away as in a continuous loop.  It is not easy to stop.  The only way to stop VMware is via the Task Manager or restart the machine.

  What must I do to get the Windows XP Pro VM to run in the new machine?

  VMWare technical support suggested that I have disable 3D acceleration (VM > settings > view and uncheck the box 3D graphics acceleration).  The virtual machine starts now with some minor problems, but it is usable.  But by closing accel 3D turns, in the words of the Technical Support Engineer, David, that there is "a problem with the graphics card not imitate or through its capacity to the virtual machine.  In other words do not support to the VM guest 3D acceleration. "My next step is to make sure that I have the updated driver for the Intel HD Graphics 4600 display adapter.

  Minor problems are:

  (1) the virtual machine works best in screen mode reduced.  There are a few problems speed mode full-screen.

  (2) the VM will still work after switching on of the host.  But after execution of the virtual machine, if power you the virtual machine and the release of VMware workstation, then later, start the workstation, the virtual machine will power not.

  To turn it on again you must out of VMware Workstation, disconnect the host machine and then reopen it in one.

• 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 - can't share a VM

  Hello

  I just installed VMware Workstation 8 on a Windows Server 2003 R2 64-bit (I've had beta of VMware Workstation 8 and I uninstalled it before this new facility).

  The problem is that I can't share a virtual machine more. This feature is used to work but in the beta...

  Here is the message I get when trying to share the virtual machine (Edition-> Preferences-> sharing VMs):

  VMware Workstation cannot connect to the server of workstation

  I checked VMWare Workstation Server service and it is not started. I tried to start it manually (I also tried to change the account) but without success. I'm constanthy get:

  Windows could not start VMWare Workstation Server on the Local computer. For more information, see the system event log.

  I have in the Application event log:

  Would be blocked by an access protection rule (rule is in warning mode) (Virtual Machine Protection: prevent modification of VMWare Server files and settings).

  In the system event log, I have:

  The VMware Workstation Server service stopped with error 4294967295 (0xFFFFFFFF) special service.

  Please notify.

  Kind regards

  M.R.

  MR2001 wrote:

  Thanks for the link of the Tejas article, I don't understand however why do I need to reinstall Workstation 8? Can you please explain?

  Could you try anyway?  There is always the possibility that there could be bugs in the installer that caused the service not be installed and configured properly.

  In addition, when you try to start the service, could check to see if a file pass-# .log is created in the %ALLUSERSPROFILE%\Application Data\VMware\hostd? (Since you were able to run the beta version on this system before, make sure you check the timestamps.)

• VMWare Workstation does not stop is a virtual completely on Surface Pro 3 machine

  Hello

  I use VMWare Workstation 10.0.3 on my 3 Surface Pro I7 with 8 GB of memory. Most of the time when I suspend my virtual machine image he doesn't stop the virtual machine completely. The result is that I cannot supply or not more and even can't leave VMWare Workstation, because it says that the virtual machine is always busy. When I force to restart my computer and start VMWare Workstation virtual machine once again watch as suspended. What is good.

  This happens only on my Surface Pro 3

  Can anyone help?

  Best regards

  Evert

  Please this post in the forum of the workstation, it is now displayed at the forum of the workspace

• VMWare Workstation 10 - jerky and unresponsive under load. [UPDATE: DisplayFusion cause possible] [SOLVED: DisplayFusion parameters]

  I have a problem with some VMWare Workstation customers, which case the mouse and keyboard to the virtual machine stops responding for a second or two under load. The mouse cursor stops, or jerk around the screen, and once past the load will be generally shot in another part of the screen. Similarly, the keyboard will become unresponsive, but when the load goes it will tend to double/triple type characters have been typed during the slow down.

  I use these virtual machines primarily for programming and a good example of the guest being "under load" is when I am compiling; It is a heavy load of CPU and i/o load.

  Two 64-bit Windows 8 and Windows 8.1 comments behave in this way, even if a Windows 2003 R2 plu prompt does not work.

  The virtual machines are configured with 2 GB or 4 GB, which is set to adapt to the host (who has much free). Virtual machines and disks are on one of the the two SSD drives. They are both configured to monitor several. In both cases, there is a virtual primary 60GB, preeallocated and no split disk and a virtual disk of 10 GB, allocated in advance, do not divide and define it as independent.

  I tried a number of settings, including having acceleration 3D on and out, manually replacing the CPU virtualization settings in VMWare and I tried all the following settings (together) and of which none have solved the problem:

  svga.vramSize = 134217728

  mainMem.useNamedFile = "FALSE".

  sched.mem.pshare.Enable = "FALSE".

  prefvmx.useRecommendedLockedMemSize = 'TRUE '.

  mainmem.backing = 'swap '.

  insulation. Tools.Unity.Disable = 'TRUE '.

  If I connect via RDP to these machines, rather than using the workstation console, I do not understand the problem and there is not any particularly notable slowdown in performance

  I had this behavior earlier in 9 work stations, but the upgrade to 10 did not make a difference.

  Someone at - it recommendations for investigating or fixing this problem - it renders useless VMs for software development which is their main purpose?

  Thanks in advance for any advice or help.

  My host system is as follows:

  Mobo: ASUS P8Z68-V PRO

  CPU: Intel i7 2600 K

  RAM: 16 GB

  Video: Nvidia 580 for 2 monitors, integrated Intel SandyBridge third.

  HARD drive: the hosts to the Samsung 840 Pro SSD, SSD Crucial M225 CT128, Western Digital 2 TB HARD drive

  SE host: Windows 7 x 64

  [SOLVED]

  Thanks to Keith Lammers in this thread on the site of DisplayFusion.

  It seems that the activation of the option of the processor affinity in the Fusion Advanced Setttings display makes the disappearance of the problem.

  [SOLVED]

  Thanks to Keith Lammers in this thread on the site of DisplayFusion.

  It seems that the activation of the option of the processor affinity in the Fusion Advanced Setttings display makes the disappearance of the problem.

• Move a VM from VMWare Workstation 7 to VMWare Server 2

  Hi all:

  I had to create a virtual machine in VMware Workstation 7 manually prepare and now I need to move it to VMWare Server 2, which is used to run automated tests. It is our usual working process.

  I would like to know if there is a problem with it, because the process of setting up the machine took several hours, install programs, and to configure, you know.

  Should I edit the .vmx file? I copied the machine using scp, since the destination that VMware Server is installed on a remote computer; I can access which the machine in ssh and web.

  Thanks in advance for your attention and your time and best regards,

  Luis

  If the virtual machine was powered (non-suspended) offshore before moving them to the destination, you should be able to turn on without problems. Both VMware Workstation 7.x and VMware Server 2.x can use hardware virtual version 7 (http://kb.vmware.com/kb/1003746), which is probably the most important thing.

  If you don't know, create a snapshot before you turn on the virtual machine to the remote site, in this way that the virtual disks have changed.

  If the copied virtual machine snapshots, you will not be able to come back to them on the new hardware if they were taken while the virtual machine is running.

  André

• Problema al add UN nodo adicional al Cluster Windows Server 2012 con VMware Workstation 9 en

  Hola Buenas,

  Ante todo decir este are a Québec fallo he revisado y las responses in different los don't post han well para help me, good os.

  El caso are that I have 2 servers DELL PowerEdge R420 fisicos identicos, cada uno con ellos 3 VMs sober instaladas VMware Workstation 9. The first virtual machine are an image of Kerio control, a second virtual machine to Windows Server 2012 con dominio Controladora, is the third VM con WS2012're donde quiero crear el cluster con dominio usuario. ESTOS servidores knew vez esta una cabina data via iSCSI connected.

  Add tambien when performed the tests of validation led Cluster, todo lo tengo OK. El caso are so creo el cluster con el Nodo 1 y 2 Nodo (sugar Québec cada uno fisica Máquina distinta ellos y bajo mismo Dominio) me error UN da has the el crear hora cluster. In cambio, if creo el Cluster con este nodos if any to crea, pero el fallo viene a hora of connect UN nodo adicional (ya sea o 1 Nodo Nodo 2). Este fallo viene cuando el nodo TR checks are completely funcional in el Cluster, is is "pensando" y da fallo por tiempo sold.

  He revisado problemas similar y he visto that el antivirus can be una causa e caso no lo're are only aun no he wont any AV... There comprobado red devices (utilizamos 4, 2 iSCSI, 1 red LAN y otra heart rate), he desactivado los red el protocolo IPv6 devices, he probado connect los nodos con el Kerio Offline, el desactivado firewall of Windows, exportar components del registro TCPIP6, capture las conexiones iSCSI...

  El cluster is as en Máquinas Office instalacion del WS2012 y is ha hecho manera person, no mediante VMWare del injerto.

  Una nueva prueba as hoy he ha hecho sido realize el cluster 2 maquinas office in una misma Máquina física y to ha s con exito, pero cuando intento realize el 2 nodos cluster (2 machines virtual cada una fisica diferente Máquinas) cuando me da el error. Esto deduzco raiz Quebec are a VMware o red, no lo o problema se, he probado use tan solo 1 switch (infrastructure utilizaria 2), changing IPs, pero igual sigo as can be? contacts? Alguna especifica VMware config?

  El caso're llevo several days ago that don't con este problema y no se a what can deber, agradeceria muchisimo the the comunidad ayuda.

  MUCHAS Gracias

  Buenas

  Between 2 workstation are posible realize ese tipo configs of forma limpia.

  El problema're (sniffer lo of UN pones veras TR), Los nodos assume ip-spoofing y arp spoofing cuando salen por tarjeta of Red led host.

  Para hacer eso as pides, deberias workstation pasar an esxi.

  Saludos

• Problem with keyboard Windows 8 on VMware Workstation 8 + start error!

  Hello

  I installed VMware Workstation 8 today to use Windows 8 Preview developers. But I have a problem.

  When I finished with the installation of Windows 8 I can't type anything. When I go to settings, the settings said: VMware keyboard driver is not installed on the host computer. How can I install it?

  EDIT: I had another problem. When I want to launch Windows 8 I get an error: the VMware authorization Service does not work.

  I can get 2 answers please?

  Thank you!

  Post edited by: MrMvanDoorn

  Install the keyboard on a Windows host, improved driver read page 130:

  http://www.VMware.com/PDF/WS80-using.PDF

  To start the VMware authorization Service: services.msc open with window to open the properties of privileges, select VMware authorization Service, administration and press start button.

• 15 Ubuntu won't start in VMware workstation 12 after a recent update of Ubuntu

  I'm quite new to the environment virtual system and linux. Someone could me help on my question below?

  I have a virtual system installed using VMware workstation 12. It works fine, until the upgrade of Ubuntu this morning.

  I have no idea what the update installed.

  After the required reboot, Windows VMware has always stop a black page.

  Before everything, there were some posts that I think they should be useful to target the issue here.

  

  He said:

  SMbus host controller not activated!

  No valid rapl area found within the package 0

  Thank you very much for your help!

  -Ninggang

  I found a solution!

  There is problem of ubuntu, new kernel is bad and it's a bug.

  To start again just hold SHIFT while your machine virtual machine to the menu shows ubuntu boot.

  Select Advanced, then choose more old kernel version and that's all.

  After you restart your virtual machine it always start on black screen, you need to delete newes kernel version linux-headers - 4.2.0 - 30 to begin on the old version and problem SOLVED!

  remove the kernel:

  sudo apt-get remove linux-image-4.2.0-30-generic
sudo update-grub2

  reboot.

• Update Windows 10 November (10586 aka 1511): bcdedit/set hypervisorlaunchtype off, but VMware Workstation does not start VMs with conflict of Hyper-V

  Hi all

  I upgraded from Windows 10 Windows 10 November updated this morning.

  I have the Hyper-V role is installed and use it from time to time, but bcdedit to configure the boot loader to disable Hyper-V by hypervisorlaunchtype power off.

  This technique has worked with 10 Windows and VMware Workstation and I could start and run virtual machines

  Since I did the upgrade, I can't start VM with this standard message "VMware Workstation and Hyper-V are not compatible"

  I am running VMware Workstation 10, but suspect that this problem also exists with later versions.

  Everyone knows about this problem?

  Someone at - he found a solution?

  I'm willing to fork over $150 for 12 workstations to solve this problem, but I want to know with certainty that it is circumventing my problem.

  Thanks for that.

  Uninstallation and reinstallation of the hyper-v feature, following the upgrade of Windows Windows 10 November 10 update solved the problem.

  I still need to run the following command to disable the Hyper-V technology

  bcdedit/set hypervisorlaunchtype

  Thanks to everyone for their help.

• Problems of synchronization of time in VMWare Workstation 10

  Hello

  I have VMWare Workstation 10 and I have problems with the system clock. I have Windows 7 installed (not allowed).

  The system clock is not synchronized with the clock of the host computer. I turned on time-synch, update the virtual machine but I still have this problem.

  What should I do to fix this?

  Thank you

  Hi, Overexposed731

  If you machine has been added in the field, then maybe you can't find the internet time. in such a situation, perhaps, you need to start service 'windows time' to support the synchronization of time with your domain name.

  If not in the field, you should find the internet configuration of time by following the steps.

  1. click on the time in the bottom right of your desktop

  2. click on "change data and Setup... times." "in the dialog box, then you will find 'internet Time' tab in the pop-up window

  Hopefully useful.

  Concerning

  Xisheng

• NAT with VMWare Workstation 9-Urgent problems

  
  Hello

  Try to use NAT in VMware Workstation 9 and am lost in my VM connection.

  But when I use the network bridge, it works very well.

  Is someone can you please help me solve?

  I tried reinstalling VMware workstation for all n No.. times and restored the settings of the Virtual Network Editor as well.

  Help, please!

  It seems that the client does not receive a DHCP address? Assuming that the virtual network adapter in the virtual machine settings is 'connected' (which, I guess, because you said Bridged works very well), you can check if there is a problem with the installation. Please run services. MSC (or net start from the command line) to see what VMware services are running on the host computer.

  André

• VMware Workstation 10 bug: DVD SATA drive does not start if we disable the floppy drive in the VMware BIOS

  Hello

  I use VMware Workstation 10, and I found a bug:

  With the all-new virtual machine (for example with Windows 8 x 64), if I choose a hard SATA and SATA DVD drive in VMware and I have to disable the floppy drive in the VMware BIOS, Windows 8 (or Windows 7) ISO does not start.

  If I come back in the BIOS to enable the floppy drive once again, my ISO boot.

  If I use the DVD IDE drive in VMware options, no problem if I disable the floppy drive.

  With "EFI mode", no bugs.

  Please, can you solve this problem? Thank you

  Hi freebeing,

  Thank you for reporting this issue.  We have reproduced it is internal and work on it.  Sorry for the inconvenience.

  See you soon,.

  --

  Darius