VMware workstation player cannot use the suspend button when the software upgrade to version 15
Error message
Error while suspending: The virtual machine cannot be suspended until
VMware Tools finishes running the script.
Try to expand the play and pause icon and select the suspend option.
(Tente expandir o ícone de play e pause e selecione a opção suspender.)
Looks like the Power controls are not available in VMware Workstation Player. To chage this setting you will need to manually edit the .vmx file for the VM as follows:
Ensure that the VM is shutdown and VMware Workstation Player is not running.
Open the .vmx file for the VM in your preferred text editor. (Notepad.exe will work.)
If there is already an entry in the .vmx file of powerType.Suspend = "soft" change it to powerType.Suspend = "hard".
If the entry does not exist add it.
Save the changes to the .vmx file and close it.
Run the VM and see if Suspend now works.
Reference
Related
I am configuring a virtual machine on VMware EXCi 7, using the web interface for accessing to the screen of the VM.
I need to use the Print Screen key for the OS configuration, but is not working.
I´m using my laptop keyboard (IS NOT A PROBLEM WITH THE FN KEY), and right now I do not another keyboard to try with it.
There is something necessary to use this key on VMware ESXi?
I solved this issue installing VMRC on my computer, and launching this remote console.
I installed VM ware recently now whenever i try to power on VMware it shows the below message:
"Not enough physical memory is available to power on this virtual machine with its configured settings.
To fix this problem, adjust the additional memory settings to allow more virtual machine memory to be swapped.
If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines."
I am not able to change the memory setting .It just shows an option to resume the virtual machine, All other options are disabled. I have by mistake increased the VM ware memory in run time .Could any one help?
For anyone who encountered this problem recently, please visit this link:
http://blogs.vmware.com/workstation/2014/10/workstation-10-issue-recent-microsoft-windows-8-1-update.html
Go to Control Panel -> Programs -> Programs and Features,then uninstall the Windows 8.1 Update KB2995388 may help
--* Edit *--
The Optional Update for Windows 8.1 for x64-based Systems (KB2995388) published on 10/13/2014 may causes issues when running VMware Workstation on a Windows 8.1 host with it installed.
And a message saying "not enough physical memory" will be reported.
Because the VMware team hasn't fix the issue, you can follow steps below to uninstall the update to boot your virtual machine:
1.Go to Control Panel -> Programs -> Programs and Features, then select View installed updates at the top left corner.
2.Scroll down the list and locate Update for Microsoft Windows (KB2995388), select it and click on the Uninstall button.
3.Follow the steps to finish the uninstallation.
In the comment list, someone also reported a fix from VMware communities:
Open the config.ini file located at C:\ProgramData\VMware\VMware Workstation.
Add this line:
vmmon.disableHostParameters = "TRUE"
Save & reboot your PC
It sounds like your VM machine is in a suspended state. What you need to do is follow the steps outlined here in this help ticket. Do these steps while vmware is not running. And once you do this, start vmware again and then you should be able to edit your memory settings.
Run it in Administrator mode in Windows 8.1. Probably a Windows Update... Deleting the suspended state didn't work for me.
Before proceeding with any alternative solutions/workarounds, please always double ensure you have updated to the latest version of VMWare Player.
My machine was running VMWare Player, Version 6.0.*, and this issue was occurring (my local machine's Operating System is Windows 8.1). The relevant error(s) were resolved after updating to the latest build currently available, VMWare Player, Version 7.0 (Please note: I did not have to remove/uninstall any Windows Updates/Features)
Just spent a few hours trying to get my VMware to boot. Power flickered off enough to shut down the computer while the VMware was in suspension and recieved this message.
Make sure the update isn't installed. Make sure to follow the accepted answer. What made it work for me was:
Right click on your development name tab
Click on "Manage" and then "Clean up disk"
It worked for me. I'm not sure why it worked, but it was able to fix my issue. Didn't need to restart.
Follow these steps:
Close the VMware.
Select VMware icon.
Run VMware as Administrator.
On a Mac in VMware Fusion when the vm is starting and the loading bar is displayed, how can you access the the boot order as if it were a stand alone windows machine?
I've tried "f8" "delete" with no luck.
Don't know VMware on Mac, but on Windows, I'd use in Menu VM->Power->Power on to BIOS.
While startup of the VM, BIOS setup is launched with F2, boot order menu with F12.
Is there a way to detect whether I'm in VirtualBox's seamless mode from a guest machine? Or is there any command line option from VBoxControl.exe to detect this that I'm not seeing?
If that can't happen, can I programatically detect if a guest is in seamless mode from the host?
There are several ways;
check what API access you have to the information reported by the device manager; if you are on a VBox guest, you'll find a couple of unusual devices (VBOX CD-ROM, VirtualBox Graphics Adapter, VBOX HARDDISK, VirtualBox system device). Already the PC's hostname is "VIRTUALBOX".
Another, quite similar source of information is the systeminfo command. Also there, several specific parameters would contain names or values defined by VBox
You could also check if VBox additions are installed; they leave trace in the program directory, in the registry reg:\HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\VirtualBox Guest Additions and as a running task in the task manager.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I've got a virtual machine running on a server that I can't stop or reboot - I can't log onto it anymore and I can't stop it using the VMware server console. There are other VM's running so rebooting the host is out of the question. Is there any other way of forcing one machine to stop?
If you're on linux then you can grab the guest processes with
ps axuw | grep vmware-vmx
As #Dubas pointed out, you should be able to pick out the errant process by the path name to the VMD
If you are using Windows, the virtual machine should have it's own process that is visible in task manager. Use sysinternals Process Explorer to find the right one and then kill it from there.
In some cases you may not be able to suspend, or for that matter take any of the "Power" actions on the VM. You may also already have multiple VMs up and running. Use this process to identify the correct PID to kill.
On Windows 7 - Open Task Manager - Look for processes with the name, "vmware-vmx.exe", note the PIDs.
Switch to the Performance tab and start the "Resource Monitor". Expand the "Disk Activity" panel. Sort the "File" column. Look for the appropriate vmdk file for the VM you want to kill. The "Image" column will have the "vmware-vmx" process listed. Note the PID.
Switch back to the "Processes" tab and kill the PID.
Here's what I did based on
a) #Espo 's comments and
b) the fact that I only had Windows Task Manager to play with....
I logged onto the host machine, opened Task Manager and used the view menu to add the PID column to the Processes tab.
I wrote down (yes, with paper and a pen) the PID's for each and every instance of the vmware-wmx.exe process that was running on the box.
Using the VMWare console, I suspended the errant virtual machine.
When I resumed it, I could then identify the vmware-vmx process that corresponded to my machine and could kill it.
There doesn't seem to have been any ill effects so far.
Similar, but using WMIC command line to obtain the process ID and path:
WMIC /OUTPUT:C:\ProcessList.txt PROCESS get Caption,Commandline,Processid
This will create a text file with each process and its parameters. You can search in the file for your VM File Path, and get the correct Process ID to end task with.
Thanks to http://windowsxp.mvps.org/listproc.htm for the correct command line parameters.
For ESXi 5, you'll first want to enable ssh via the vSphere console and then login and use the following command to find the process ID
ps -c | grep -i "machine name"
You can then find the process ID and end the process using kill
see the following from VMware's webpage
Powering off a virtual machine on an ESXi host (1014165)
Symptoms
You are experiencing these issues:
You cannot power off an ESXi hosted virtual machine.
A virtual machine is not responsive and cannot be stopped or killed.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165
"Using the ESXi 5.x esxcli command to power off a virtual machine
The esxcli command can be used locally or remotely to power off a virtual machine running on ESXi 5.x. For more information, see the esxcli vm Commands section of the vSphere Command-Line Interface Reference.
Open a console session where the esxcli tool is available, either in the ESXi Shell, the vSphere Management Assistant (vMA), or the location where the vSphere Command-Line Interface (vCLI) is installed.
Get a list of running virtual machines, identified by World ID, UUID, Display Name, and path to the .vmx configuration file, using this command:
esxcli vm process list
Power off one of the virtual machines from the list using this command:
esxcli vm process kill --type=[soft,hard,force] --world-id=WorldNumber
Notes:
Three power-off methods are available. Soft is the most graceful, hard performs an immediate shutdown, and force should be used as a last resort.
Alternate power off command syntax is: esxcli vm process kill -t [soft,hard,force] -w WorldNumber
Repeat Step 2 and validate that the virtual machine is no longer running.
For ESXi 4.1:
Get a list of running virtual machines, identified by World ID, UUID, Display Name, and path to the .vmx configuration file, using this command:
esxcli vms vm list
Power off one of the virtual machines from the list using this command:
esxcli vms vm kill --type=[soft,hard,force] --world-id=WorldNumber"
For VmWare fusion, hold the alt key while you click 'restart virtual machine'
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006215