Difference between revisions of "Virtual Centre"

Jump to navigation Jump to search
(→‎Update Manager: Added "Import Offline Bundle")
(→‎Troubleshooting: Added "Orphaned VM")
Line 356: Line 356:
#* Should return something like <code> unregister(/path/to/My_VM.vmx) = 1 </code>
#* Should return something like <code> unregister(/path/to/My_VM.vmx) = 1 </code>
# VM can now be unregistered from the VC
# VM can now be unregistered from the VC
=== Orphaned VM ===
VM's appear orphaned if they're in the vCentre database, but are no longer being reported by the ESX to vCentre.  Its likely that its still running (or has been restarted by HA).
# Locate the VM (if there's been an HA failover its probably not where vCentre believes)
#* Connect a VI Client direct to each ESX, if the VM isn't shown, locate as follows
#*# SSH to an ESX, and cd to the VM's folder
#*# Run the following command
#*#* <code> vmkfstools -D *.vmx </code>
#*# The owning ESX's MAC address is shown in the end of the owner field in the following part of the return data
#*#* <code> gen 443, mode 1, owner 4d0f65e4-d55ab729-0ea0-'''d48564638518''' mtime 8831379] </code>
#*# Run the following command on each ESX to find the server with that MAC address
#*#* <code> esxcfg-nics -l </code>
# If the VM is shown on the ESX's VI Client, restart the ESX's management agent.
# If the VM is not shown on the ESX's VI Client, browse the datastore and register the VM


=== VI Client Slow on Windows 7 ===
=== VI Client Slow on Windows 7 ===