Labels

3300 (1) 3PAR (1) Active Directory (1) ADFS (1) Admin Share (1) Auto-Sync (2) Auto-Sync locked (1) AWS (3) AzCopy (1) Azure (3) Backups (2) Broadcom (1) Call Forwarding (1) CLI (2) cmd (1) Compatibility View (1) Dameware MRC (1) Databases (1) DFS (1) DNS (1) Domain Admin (1) domain controller (1) Enterprise Mode (1) ESXi 5.0 (1) ESXi 5.1 (5) ESXi 5.5 (3) Exchange (3) Exchange 2010 (5) Extreme (1) ExtremeXOS (1) Federation (1) File Share (1) FSMO (1) GPO (1) Group Policy (1) Group Policy Client (1) Hardware Acceleration (1) Helpdesk (1) HP-UX (1) Hyper-V (2) IAM (1) IE10 (1) IE11 (1) IP conflict (1) Kayako (3) LDAP (1) Licence (1) Links (9) local groups (1) LUN lock (1) LUN number (1) MAC address (1) Microsoft Teams (1) Mitel (1) Namespaces (1) Networking (6) Nexenta (6) NMC (1) Office 365 (4) OneDrive (1) Outlook 2003 (1) Outlook 2013 (1) PC (1) Physical (1) PowerCLI (10) Powershell (10) promoted links (2) Public Folders (1) RDP (1) RDS (1) Recovery Services (1) RedShift (1) Registry (3) Reports (1) Resolve (2) Restart (1) RSA (1) Run As (1) SAML (1) SAN (1) Scavenging (1) script (10) Server 2003 (3) Server 2008 R2 (1) Server 2012 R2 (2) Servers (2) sharepoint 2013 (3) SMTP (3) Snapshot (2) SRM (1) SSH (5) SSL Certificate (2) Temporary profile (1) Terminal Server (3) Troubleshooting (5) Ubuntu (1) Update Manager (1) Useful Apps (1) VAAI (1) vCenter Server Appliance (1) VDI (1) VDP (1) Veeam Backup and Replication (2) VM (1) VM Error (1) vmdk (1) VMFS (1) vMotion (2) VMware (20) VoiP (1) vSphere 5.5 (4) vSphere 6.0 (2) vSphere 6.5 (1) vUM (1) webpart (1) Windows (3) Windows 10 (1) Windows 7 (2)

Wednesday, 19 June 2013

ESXi 5.1 VM Stuck At 95% When Restarted

When trying to open a console to a VM, I encountered the message;
Unable to connect to the MKS
I tried forcing a reset but this got stuck at 95% and I wasn't allowed to force a power off through the GUI as the reset process was still ongoing.

To get round this I followed the steps below;

1. SSH onto the host running the VM.
2. Run the command;
ps | grep "VMName" 
The name is case sensitive so make sure you type it exactly as shown in vSphere. You will get a list of  information as below;
2106831 2097959 vmx-mks:VDP01        /bin/vmx
The second number (in this case 2097959) is the process ID (PID).
3. Kill the process by running the command;
kill -9 PID
4. cd to /vmfs/volumes/DataStoreName/VMName 
5. Delete the swap file by using the command below;
rm -r swapfilename.vswp
6. In vSphere Client you should see the machine has powered off. Right click it and remove it from the inventory.
7. Browse the datastore, open the VM folder, right click the .vmx file and choose "Add to Inventory".
8. Power on the VM. You may be prompted to answer a question about whether you have moved or copied the VM so if the power on is stuck at 95%, check for a hidden popup.

No comments:

Post a comment