2,187
edits
(→Troubleshooting: Added ESX does not support virtual machine hardware version "0") |
(→Unable to Deploy Virtual Machine: Added "vCenter Lab Manager timed out trying to read the virtual machine's file on the remote host") |
||
Line 163: | Line 163: | ||
# Locate the problem network and go to '''Properties''' | # Locate the problem network and go to '''Properties''' | ||
# Update the '''Physical Network Bindings''' for the relevant ESX | # Update the '''Physical Network Bindings''' for the relevant ESX | ||
'''Unable to deploy VM ''VM'' in VirtualCenter. The session is not authenticated.'''<br> | '''Unable to deploy VM ''VM'' in VirtualCenter. The session is not authenticated.'''<br> | ||
Line 172: | Line 173: | ||
# Click on '''OK''' to re-apply the user/pass | # Click on '''OK''' to re-apply the user/pass | ||
'''''ESX'' does not support virtual machine hardware version "0"''' | |||
'''''ESX'' does not support virtual machine hardware version "0"'''<br> | |||
Caused by config data corruption, potentially from the machine's VMX file | Caused by config data corruption, potentially from the machine's VMX file | ||
# Locate the VM's config and confirm the hardware version is set correctly (eg to v7 for ESX4) | # Locate the VM's config and confirm the hardware version is set correctly (eg to v7 for ESX4) | ||
Line 181: | Line 183: | ||
#* <code> UPDATE VirtualServer SET hw_version=<correctNumber> WHERE hw_version=0 AND name='VirtualMachineName' </code> | #* <code> UPDATE VirtualServer SET hw_version=<correctNumber> WHERE hw_version=0 AND name='VirtualMachineName' </code> | ||
# The VM then needs to be cloned to template and then redeployed (clone required to prevent reoccurrance) | # The VM then needs to be cloned to template and then redeployed (clone required to prevent reoccurrance) | ||
'''vCenter Lab Manager timed out trying to read the virtual machine's file on the remote host'''<br> | |||
Caused by either of... | |||
* The ESX experiencing problems reading the files of the VM (and its parents) on VMFS storage | |||
*# Check out VMFS storage! | |||
* The VM is still partially running on an ESX (so its files are locked) | |||
*# Run the following command on the likely ESX(s) to running VM processes | |||
*#* <code> ps auxwww | grep -i vmx </code> | |||
*# Kill the relevant processes, eg | |||
*#* <code> 7135117 7179577 mks:001876-VM-Server-A /bin/vmx </code> | |||
*#* <code> 7180174 7179577 vcpu-0:001876-VM-Server-A /bin/vmx </code> | |||
*#* <code> 7180175 7179577 vcpu-1:001876-VM-Server-A1 /bin/vmx </code> | |||
*#* Run <code> kill 7179577 </code> | |||
=== Lab Manager Disconnected from ESX === | === Lab Manager Disconnected from ESX === |