Use of TCP Port when adding sensors to virtual machines

Similar Questions

• Serial Port is configured for a virtual machine...

  Dear team,

  I found the serial port is configured on one of the virtual machine, which follows is the blink of an eye the same.

  

  Just want, serial port is required for the devices on which?

  Usually, you see the serial port after a P2V and not detached from the VM.

  Why is it necessary?  Nowadays it probably isn't, but there are days where we still used modems on (among other things) serial ports.  Introducing a serial port to the virtual machine, you can go through the device that was attached to the serial port of the server host directly on the virtual computer.

  Today it is not really useful and you can probably just close the virtual machine and remove it.

  Matt

  http://www.thelowercasew.com

• Can I force it to use more vMemory and less vCPU in a virtual machine?

  Hello guys,.

  I have a virtual machine that uses vCPU more than a vMemory, when I select the Task Manager, I noticed that the memory is less than 5% and the cpu is greater than 50% when no application is running when the application run the vcpu go high and the vmem remains low. If there is any way to force it to use more vmemory and less vcpu in a virtual machine? can I use the list of resources for this?

  Thank you

  No, you can not force the VM to use more memory and less CPU. In fact you can force the VM to use less CPU by limiting the use of the processor, but it will affect performance. The only thing you can do with forcing more use - is to guarantee the physical resources for VM (reserve), but if the virtual machine has no more physical memory or CPU it don't use them.

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• Maximum amount of disks that can be added to a virtual machine?

  Hello

  We are DPM configuration and we need a huge pool of disks and our EVA system allows us only to created a maximum of 2 TB LUN.

  Now, we are at the point were we only had SCSI ID 0:15 left to add a disk.

  What is the limitation of adding disks of virtual machines?

  Thank you

  Erik

  60 is the maximum: 4 * 15 devices SCSI

  SCSI controllers per virtual machine 4

  Devices per SCSI 15 controller

  Devices per virtual machine (Windows) 60

  Devices per virtual machine (Linux) 60

  http://www.VMware.com/PDF/vi3_35/esx_3/r35u2/vi3_35_25_u2_config_max.PDF

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!

• How to download and use my Win 7 Pro prior in a Virtual Machine in VMWARE PLAYER?

  before 3 years, I bought a win 7 pro PC - recently, I fee install 8.1... How to download and use my prior Win 7 Pro in a Virtual Machine in VMWARE PLAYER?

  Unfortunately, you must have prepared a recovery disk in advance or use the one provided with your computer.

  For 5 years, Microsoft made it fairly easy for users of the Windows 7 operating system to get reinstall media. If you have lost your support disc or installation retail collection; either it has been damaged or defective; You can download a copy of the edition that you have licensed from a membership site called Digital River. More recently, Microsoft ended the availability to reinstall media that you can download as a. File ISO in Digital River, which is a digital reproduction of an optical disc.

  It was particularly convenient for people who could not easily get the manufacturer's recovery media, did not want to pay the fees required to get or preferred a clean configuration without the software packaged manufacturers or even a recovery partition does not work. It's easy to use, all you had to do was reinstall and reactivate using the product key located on the certificate of authenticity and download all the drivers on the manufacturers website.

  Given that this option is no longer available, what are your options? See the article for more details:

  How to: What are my options for Windows 7 reinstall media?

• How to use an iso of media store in a virtual machine?

  I know this is a stupid question, but I can't understand how to use an iso of media store in a virtual machine in a laboratory Manager configuration. I copied on an ISO in my store of media NFS and its all synced to the top and available to use. But what I want to know is, is there a way we can map the iso in a virtual machine in the config of lab manager and make it look like cd?

  Pls advice.

  just a couple first checks:

  1. the ISO standard appear in the media section of the organization who needs to use it.

  2. the NFS store is accessible by all esx hosts used in this organization

  3. go to the page of the console for the virtual machine that needs to use it.

  4 right-click the VM name to get the full menu

  5. Insert the CD

  6. choose the ISO from the menu drop down.

  All this is in the user manual.

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• How I pre-allocate disk and persist when creating a new virtual machine in 7.1?

  Maybe I'm missing something, but I strive to pre-allocate and persist a hard disk for a windows XP Pro VM. It doesn't seem to be the option most to do so during the installation, even in the custom/Advanced menu. Did I miss something in 7.1? Can someone point me in the right direction?

  When you create the virtual machine, choose to create a virtual custom computer, and one of the pages of the wizard has a checkbox "Allocate all disk space now".  Once the virtual machine is created, you can go to the settings of the virtual machine, select the drive, click on the Advanced button and make a persistent independent drive.

• When you access the virtual machine, getting the error "encountered an error when you try to use one of its virtual hard disks". Help?

  I received the "low disk space error" on a hard drive of the virtual machine dynamic expanding. I have increased my space of virtual hard disk using "My Computer" > manage > storage > "Disk management" and choose "Attach VHD" then resizing to max available (64 GB), and now I can not start the virtual machine. It gives the error: encountered an error when you try to use one of its virtual hard disks. Help?

  Hi NatalieFoster,

  The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums to get help:

  Windows 7 Virtual PC and XP Mode TechNet Forums

• Using vmrun to obtain an IP address when you run the virtual machine mode headless fails customers

  Operating system: OS X Yosemite 10.10.5

  VMware Fusion: Professional Version 8.1.1 (3771013)

  When you run a VM guest in headless mode I can't use vmrun to get IP clients. If I eventually bring to the top/start the merger GUI, the command returns the IP address as planned. It is always reproducible.

  $ vmrun -T fusion start "path/to/MyVMs.vmx" nogui
  2016-06-12T10:55:46.626| ServiceImpl_Opener: PID 11515
  
  ... wait for VM to come up. If the VM has a static IP address I can now ssh into the instance.
  
  $ vmrun -T fusion getGuestIPAddress "path/to/MyVMs.vmx"
  Error: The VMware Tools are not running in the virtual machine: "path/to/MyVMs.vmx"
  
  $ vmrun -T fusion checkToolsState "path/to/MyVMs.vmx"
  installed
  
  ... Start the VMware GUI and ensure the VM's console window is open
  
  $ vmrun -T fusion getGuestIPAddress "path/to/MyVMs.vmx"
  192.168.100.23
  

  I tested with open-vm-tools and tools VMware packaged with the merger and the behavior is the same. I also spoke with others on the channel of freenode #vmware who have confirmed that the problem exists for users of workstation as well.

  Hi danandham,

  Welcome in the vmware community. Iyou s really a problem, we try to fix it.

  After a command, you can use as a workaround:

  vmrun t fusion getGuestIPAddress "path/to/MyVMs.vmx" - wait

  See you soon

• Using VMWare Studio 2.6.0 to manage virtual machines on a host ESXi 4.1.0

  Hi all

  I'm having a problem connecting to our 4.1.0 ESXi host using VMWare Studio 2.6.0 (and it is quite possible that the problem is that I'm badly understand what VMWare Studio is supposed to provide). What I would do is create/configure/manage the virtual machines on our ESXi server from within Eclipse, similar to what I can do with vSphere client. However, when I open the Explorer of VMware Studio and try to set up the connection, I still get the error message "Connection to xxx.xxx.xxx failed. Difficulty of connection settings and try again or cancel. "I use the default port of 5480 number and the same references that I use in the vSphere client.

  So, my questions are: I use the incorrect port number? I am using a configuration that is known not only not for work (ESXi 4.1.0 + VMWare Studio 2.6.0)? Or am I completely misunderstanding what VMWare Studio and is not?

  Please specify!

  I think you misunderstand what did the Studio. It's simply a VM construction kit. Once created, the OVF Studio is out of the picture. He does, eventually, put some components in the virtual machine to manage addresses network, proxies, updates, etc. but above all, he was only VMs.

  The Eclipse of Studio plugin is simply another user interface in the Studio build system and will work only if it points to a Studio running. It will not serve the goal of the vSphere client.

• wget timesout when you create a virtual machine

  Hello

  I'm building a Virtual Appliance using Vmware Studio. It's basically a device of Tomcat, so I provide a JDK and Tomcat package in the Build Studio process.

  When the Studio generates the VM, it tries to download the JDK and Tomcat and install both on the virtual machine. The download and install tomcat works very well, but JDK package timeout on the wget due to the size of the package. The error I get in the errorlog file-

  Connection to [address] | : [Port]... connected.
  Application of proxy sent, awaiting response... Error (Connection timed) out of reading in the headers.
  Abandon.

  How can I configure studio to allow of largest wget wait times during the construction of the machine Virtuelle/Virtual Appliance.

  Thank you.

  Most of the calls in perl code Studio wget use a 'constant' in /opt/vmware/lib/build/VADK/Constants.pm called WGET_TIMEOUT:

  void WGET_TIMEOUT {return ' - timeout 60 - tent = 1' ;}}

  You can change the timeout value in this function.

• "Unable to connect to MKS" when connecting to the virtual machine shared

  Hello

  I have a handful of Shared VMs Im trying to access remotely with VMware Workstation Pro 12 (same version on the client and the host - two Windows 10 machines). I am able to connect to the host that shares virtual machines, I can see all the virtual machines shared, open the virtual machine (as in it opens in a tab within the workstation) and virtually no action on the virtual machine including all power options, instant, change settings, etc.. The problem is that if I turn on a virtual computer (or connect to an existing virtual machine under tension, I get the following error and Im not able to access the actual console since it remains as a black screen.

  Unable to connect to the MKS: (name of user and password) Login incorrect.

  I also noticed that on the client Windows Event Viewer is to launch the following warning events at the same time that the error in the Workstation has been lifted - Im not seeing any on the host are thrown.

  

  

  I've seen a lot of posts here with users who run the question and he usually ended up being a network problem. I turned off the Windows Firewall on both machines, checked ports 443 and 902 listening on the host and Im in telnet from the client to the host on port 902. I also saw another suggestion for updating the client Windows hosts file to include [host name] [IP address] and [FQDN of the host name] [ip address], but this subject seems not helped either.

  Suggestions in this regard does not happen what keeps or where to find more information about the cause?

  Thank you!

  Post edited by: Tim Graffam

  Thank you for using the workstation. I think that this will solve your problem.

  Unable to connect to the MKS: (name of user and password) Login incorrect

• How to make a virtual computer to connect to a CD player with an ISO mounted when you start the virtual machine?

  I am the creation of virtual machines using PowerCLI 5.5 on vSphere 5.0; and while the virtual machine is turned off, I am able to mount an ISO on a CD player and change the boot order to boot from the CD-ROM (for another post).  I have the flag startConnected set to true, but am not having much luck getting the virtual machine to connect to the CDDrive

  $cdObj = $Vm | New-CDDrive - IsoPath $isoPathName - StartConnected: $true

  If ($cdObj - no $null)
  {
  #Power off VM if it is on
  $VmState = $Vm.PowerState
  
  If ($VmState - eq "Receptor")
  {
  $Vm | Stop-Vm-confirm: $false - ea 0
  }

  $BootHardDiskName = 'disk 1 '.
  $VmView = get - VM $VmName - Server $serverObj.Name | Get-View
  $HardDiskDeviceKey = ($VmView.Config.Hardware.Device |) Where-Object {$_.} DeviceInfo.Label - eq $BootHardDiskName}). Key

  $BootableHardDisk = new-Object - TypeName VMware.Vim.VirtualMachineBootOptionsBootableDiskDevice - property @{'DeviceKey' = $HardDiskDeviceKey}
  $BootableCDRom = new-Object-Type VMware.Vim.VirtualMachineBootOptionsBootableCdromDevice
  
  #Set for CDRom boot order
  $BootIso = new-Object VMware.Vim .VirtualMachineConfigSpec - property @ {}
  "BootOptions' = New-Object VMware.Vim.VirtualMachineBootOptions - property @ {}
  BootOrder = $BootableCDRom
  }
  }
  
  #Set VM from the start settings at the start of the first CD and forces the display to update (sometimes delayed)
  $VmView.ReconfigVM_Task ($BootIso) | out-null
  $VmView.UpdateViewData ("Config.BootOptions.BootOrder")
  
  #Power on VM
  $Vm | Start-VM-confirm: $false - ea - global 0EV: vmOpsError | out-null

  When I start the VM, it does start the ISO.

  If I go to vCenter, the CD is pointing to the ISO file, but the 'Connected' to change settings option is not checked;  I can restart the VM of vCenter and then the VM restarts the ISO, but not in the script.

  I even put code to add a lead time of 5 to 10 seconds; I restart the virtual machine twice in the script and I can't CD to connect to start the virtual computer.

  Appreciate any suggestions.

  Maureen

  Have you tried to do a

  Game-CDDrive - CD $cdObj - connected - confirm: $false

  immediately after the start-VM?

• Simultaneous use of the vmscript call on the same virtual machine.

  I'm trying to call vmscript allows you to execute commands on a virtual machine. Several applications can come to the computer virtual target (where the script is executed) from different sources. When I make a call at the same time, it works very well.

  However, when I make simultaneous calls to invoke vmscript to run a command on a remote computer, only one runs and others fail with the following error.

  23/12/2013-14:52:21 Invoke-VMScript operation is not allowed in the current state.

  23/12/2013-14:52:21 Invoke-VMScript error occurred while running script on the guest in "v7012-s1-arr1" VM operating system Cannot find script interpreter "Bat" in one of the spaces provided.

  You probably don't have enough permissions to execute the command in the comments.

  Even if the error mentions privileges, I'm sure that it is not only the privilege as it works if I run commans an establishment at the time.

  Assuming that invoke vmscript supports concurrency - y at - it target configurations I need to put on the virtual machine to allow the operation?

  As far as I know, the mechanism that uses Invoke-VMScript cmdlet, does not have parallel calls.

  As a bypass, you could use a try - construction of wrestling to synchronize different calls.

• black screen, when you open the virtual machine console

  Hi guys need help in answering the following questions:
  When you open the console of the virtual machine, the connection process is fine, but it stops at a black screen

  

  That's what I use:
  (1) Windows 7 x 32
  VMRC 2) 5.1.0.20447
  (3) Mozilla Firefox 18.0.1
  (4) VMware vSphere Client 5.1
  (5) Vcloud 5.1.0.810718

  Here is my log:

  13/01/29 10:15:42.100 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:15:42.101 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
  {{2013-01-29 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, VMRC_EVENT_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}"ID - 2 modes - message mode has 2-3
  29-01-2013 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
  29-01-2013 10:15:42.103 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
  29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
  29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
  {2013-01-29 10:15:42.832 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C]}
  29-01-2013 10:15:42.833 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
  29-01-2013 10:15:42.845 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379] 10:15:43.901: control of the VM has not been created
  29-01-2013 10:15:43.902 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 10:15:43.909 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.909: control of the VM has not been created
  29-01-2013 10:15:43.923 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.923: control of the VM has not been created
  29-01-2013 10:15:43.925 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.925: control of the VM has not been created
  29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:15:44.275 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
  {{2013-01-29 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, VMRC_EVENT_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}"ID - 2 modes - message mode has 2-3
  29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
  29-01-2013 10:15:44.276 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
  29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
  29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
  {2013-01-29 10:15:44.958 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD]}
  29-01-2013 10:15:44.959 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
  29-01-2013 10:15:44.970 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
  29-01-2013 10:15:46.770 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:15:46.770 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
  {{2013-01-29 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, VMRC_EVENT_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance ID 'vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}' - mode 4 - message mode has 2-3
  29-01-2013 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
  29-01-2013 10:15:46.772 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
  29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/ScriptableObject.cc:321]: ID of property not found: onMessage
  29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/VmrcPlugin.cc:2548]: onMessage Manager call failed
  29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
  29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
  {2013-01-29 10:15:47.380 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996]}
  29-01-2013 10:15:47.381 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
  29-01-2013 10:15:47.388 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
  29-01-2013 10:17:20.197 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
  29-01-2013 10:59:13.788 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
  29-01-2013 10:59:13.792 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
  29-01-2013 10:59:15.303 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 10:59:15.308 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 10:59:15.324 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.324: control of the VM has not been created
  29-01-2013 10:59:15.326 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.326: control of the VM has not been created
  29-01-2013 10:59:33.283 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
  29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:33.284: control of the VM has not been created
  29-01-2013 10:59:33.540 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
  29-01-2013 10:59:33.540 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3

  Windows 7 x 32

  That's kinda our old friend is back.

  Two checklists

  1. check the version of the VM VGA driver, if that's the case, you must update the WDDM driver display driver.

  2. make sure that you use HW 7 and more.

  More info here