Versions Compared

Version Old Version 9 New Version 10
Changes made by

JM Lopez

JM Lopez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Below is some of common symptoms VMs could experience after being recovered from underlying storage problems. 

  • Blue Screens - Older version of Windows

  • VM State is “powered on” but VMWare tool status shows “Not Running”

  • Unable to login to OS even with correct credentials

  • CPU Utilization pegs at 100%

Solution

vSphere Client

 If you are having any of these symptoms above, please try to Reset VM (not “Restart Guest”) from vSphere Client menu and see problems are resolved.

Note

"Restart Guest” Guest” may not work as it requires VMware Tools up and running.

VSS CLI

Using https://vss-cli.eis.utoronto.ca or a local VSS CLI install:

  1. Look for the VM uuid.

    Code Block
    vss-cli compute vm ls -f name =<vm-name>

  2. Submit a request to reboot (VMware Tools running required) or power cycle the VM if not responsive.

    Code Block
    vss compute vm set <uuid> state reset|reboot
Host Name: hostname (Ubuntu Linux (64-bit))
IP Address: 172.17.0.1, 192.168.2.31
Are you sure you want to change the state from "running to reset" of the above VM? [y/N]:

  3. Verify if the VM issues have been solved

VSS Portal

The VSS Portal only offers a way to power cycle the virtual machine. To do so, please do the following:

  1. Login to https://vss-portal.eis.utoronto.ca

  2. Search for the VM to change and click on the 

    Image Removed

    Image Added

     button.

  3. Toggle the "Power Status" button to OFF.

    Image Removed

    Image Added

  4. Click on Save

  5. Wait a few seconds and repeat steps 2 to 4 but this time toggle the button to ON.

  6. Verify if the VM issues are resolved.