One of the problems I have ever met VMWare managing the farm has been unable to move or delete a virtual machine, getting the error "Could not delete the file" from the Virtual Infrastructure Client.
operations that led me to this error were:
Trying to delete the virtual machine (VM1 "for example) from the option VIClient Delete from disk. When launching this command runs successfully. However, when I reviewed the datastore for maintaining the files of the virtual hard disks (*-
flat.vmdk
) and the swap file (*. vswp flat.vmdk
).
If I try to delete files directly from the Sevice Console (
in the directory / vmfs / volumes / ) with the command rm
, this returns me the error: Device or resource busy 
Running the
" *
the directory / proc / vmware / vm
displays the following output:
-
1382/names: VMID = 1382 pid =- 1 cfgFile = "/ vmfs/volumes/48b776c0-7387a6c0-da4e-00215aee45bc/vm1 / vm1
vm1 
" 1382/userRPC: Total vmm0: vm1 vmm1: vm1
vmm2:
- vm1
- vmm3: vm1 1383/userRPC: Total vmm0: vm1
- vmm1: vm1
vm1 vmm1:
vm1 vmm2: vm1 vmm3: vm1
From this output, the information we are interested in the above output is the process ID (pid, bold). You see, the pid is set to -1 , so that the solution presents vmware not effective. The problem is that the process that locks the files in that virtual machine is not running in the COS but in the VMKernel, which we access the area of \u200b\u200bexecution of this order to get the pid of interest.
The procedure to remove the block is as follows : VMID Get the virtual machine locked. Run the command
vm-support-x Locate the associated wid VMID by command cat / proc / vmware / vm / / cpu / status I have served as a reference http://communities.vmware.com/thread/151762
http://communities.vmware.com/message/948937 # 948937 http : / / communities.vmware.com/thread/150351
0 comments:
Post a Comment