Unable to Start VM in ESXi 6.5

https://communities.vmware.com/thread/567780

Comments

Post a Comment

Popular posts from this blog

ESXI REMOVE ALL SNAPSHOTS HANGS AT 99%

Image
Check and make sure that the process is actually stuck and not just taking a very long time. To do this, follow these steps: 1. Make sure SSH service is running on the ESXi host Navigate to configuration -> security profile -> services -> Click on Properties Choose the ‘SSH’ service, ‘Options’, and click ‘Start’ Once SSH is enabled, connect to the ESXi host using your favorite ssh client. 2. Run ->   vim - cmd  vmsvc / getallvms Find the vmid of the virtual machine, in this case its 20. 3. Now run ->   vim - cmd  vmsvc / get . tasklist   20 <-   this is the # of the vm from above 4. Find the removeallsnapshots task # then run: vim - cmd  vimsvc / task _ info   185720854  <- this # will be different for you If you see:   “The object has already been deleted or has not been completely created”  or similar, your snapshot removal is probably frozen, but in order to be sure, let’s loo...
Read more

BAD_ADDRESS FLOOD IN WINDOWS DHCP SERVER

Image
How a single misbehaving client can take down your network Well, not really your entire network but definitely DHCP. I came across a linux client that had issues with assigning an IP address using dhclient. The dhclient process would throw a null pointer exception during the phase in which it attempts to validate the assigned IP address. From here, dhclient sends a DHCPDECLINE message to the server. The DHCPDECLINE message tells the server that something is either wrong with the DHCP parameters or that the client discovered that the IP was in use (through gratuitous ARP or in this case, a failed attempt at sending a gratuitous ARP). cat /var/log/messages  : RFC 1541 states: “If the server receives a DHCPDECLINE message, the client has discovered through some other means that the suggested network address is already in use. The server MUST mark the network address as “not allocated” and SHOULD notify the local system administrator of a possible configuration pr...
Read more

SharesFacebookTwitterGoogle+PinterestEmailSumoMe VMware ESX – “Unable to access a file since it is locked

Image
After transferring and/or trying to restart a VM in ESX you may be presented with the error message “Unable to access a file since it is locked”. Now what you need to do is work out what is actually locking this file and then (unsurprisingly) find a way to unlock it. Generally the problem will be caused by one of three things. 1.  Process Lock:  There is a process on the ESX server that still has hold of a file(s) used by the VM.  This is one of the most common causes.  To resolve this there have been a couple of good VMware Forum postings  here  and  here  that have been consolidated to  this useful posting over  at  GabesVirtualWorld.com   (*Note: It is worth checking out the comment by Kent at the bottom of the posting).  Also, check out Tecumseh’s posting  here . 2.  Disk Naming Conflict:  Two or more disks with the same VMDK name. This can be caused by another disk with the same VMDK file name...
Read more