So I put a powered off VM on local drive after I cloned it as something I could go back to if I needed it. After I cloned it, it appears that DRS moved it - but did not move the drive VMDK file.
Has anyone had this happen? The VM was rendered useless without the disk. When I then went into the VM inventory, there was a default 4 GB drive - but not the 28 GB drive I used to have. On the original host, the file was not there, so I could not point the VM to that disk.
Here are some relevant entries from the VPX_EVENT table:
vim.event.TaskEvent 30:05.6 info 193 SERVER1 130 ESX-1.company.net
vim.event.VmBeingRelocatedEvent 30:06.6 info 193 SERVER1 130 ESX-1.company.net
vim.event.VmRelocatedEvent 30:31.1 info 193 SERVER1 128 ESX-2.company.net
vim.event.VmStartingEvent 30:33.3 info 193 SERVER1 128 ESX-2.company.net
vim.event.VmFailedToPowerOnEvent 30:49.2 error 193 SERVER1 128 ESX-2.company.net
These events were not envoked by me, but by DRS. The message in the VIC for the 'vmFailedToPowerOnEvent' was "A file was not found". I think DRS is playing battleship with me!!!!! Can anyone confirm or enlighten?
Has anyone had this happen? The VM was rendered useless without the disk. When I then went into the VM inventory, there was a default 4 GB drive - but not the 28 GB drive I used to have. On the original host, the file was not there, so I could not point the VM to that disk.
Here are some relevant entries from the VPX_EVENT table:
vim.event.TaskEvent 30:05.6 info 193 SERVER1 130 ESX-1.company.net
vim.event.VmBeingRelocatedEvent 30:06.6 info 193 SERVER1 130 ESX-1.company.net
vim.event.VmRelocatedEvent 30:31.1 info 193 SERVER1 128 ESX-2.company.net
vim.event.VmStartingEvent 30:33.3 info 193 SERVER1 128 ESX-2.company.net
vim.event.VmFailedToPowerOnEvent 30:49.2 error 193 SERVER1 128 ESX-2.company.net
These events were not envoked by me, but by DRS. The message in the VIC for the 'vmFailedToPowerOnEvent' was "A file was not found". I think DRS is playing battleship with me!!!!! Can anyone confirm or enlighten?
