![]() After looking around for a while I noticed that the VM was showing ‘Data unavailable’ for the network adapter instead of the mapped port group, which you can see on the screenshot on the right. This error was showing up after the svmotion task was nearly finished. Try power back on the VM and it will ask you if you want to create a new UUID, say yes. When I tried to storage vmotion the VM I got every time the error ‘Invalid configuration for device 12’. ![]() ![]() ![]() Whenyou save the file, remove the VM from inventory, browse the datastore, make sure you refresh the whole directory structure with all VM dirs twice, and then re-add the vm to the inventory by right clicking on thevmx file for thatvm with the problem. Just open another ssh window and do a cat of a vmx file of another VM which you know is working fine.Ĭhange the path to the scsi0:0.filename parameter, parameter and change eventually any other parameter which shows the wrong path.Īlso I changed the uuid.location to whatever the other good VM was showing. You need to go to the ESX server/host console (login via sshwith root) and then go into the subdirectory under the vmfs/volumes dir which contains the vmx file named as the VM which you are trying to repair. After 3 hours working on this, I finally found a way out without having to rec reate the VM.īasically the Virtual Client GUI just WON'T let you get out of this situation.
0 Comments
Leave a Reply. |