asked on Error: Unable to power on Virtual Machine
I am unable to power on a VM on a production environment and the error received is:
"No Host is compatible with the virtual Machine"
I migrated the VM to another Host in the cluster and then received the following error:
An error was received from the ESX host while powering on VM host xxxx.
We are using vSphere 5.1.
Event Details:
Type ID: Info
Target Object Type: ClusterComputeResource
DataCenter Object Type: Datacenter
Host Object Type: HostSytem
Host Build: 838463
VM Object Type: Virtual Machine
ChainID: 3341944
Any idea how to fix this please.
"No Host is compatible with the virtual Machine"
I migrated the VM to another Host in the cluster and then received the following error:
An error was received from the ESX host while powering on VM host xxxx.
We are using vSphere 5.1.
Event Details:
Type ID: Info
Target Object Type: ClusterComputeResource
DataCenter Object Type: Datacenter
Host Object Type: HostSytem
Host Build: 838463
VM Object Type: Virtual Machine
ChainID: 3341944
Any idea how to fix this please.
VMware
Last Comment
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
does it only occur with this VM or other VMs ?
have you changed anything on this VM, e.g. memory or CPUs ?
have you changed anything on this VM, e.g. memory or CPUs ?
ASKER
This is the status:
1. There is no additional space in SAN
2. Unable to create a new VM and point it to the drives since Consolidation for this VM is going on to make some space
3. No changes have been made to CPU or memory
4. It is happening only to this VM
1. There is no additional space in SAN
2. Unable to create a new VM and point it to the drives since Consolidation for this VM is going on to make some space
3. No changes have been made to CPU or memory
4. It is happening only to this VM
can you screenshot the spec....
what is the OS ?
ASKER
Windows 2008 R2
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
1. When I try to turn on the VM from Host - The power option is greyed out
2. When I try to turn on the VM from vCenter Server getting message: "No host is compatible with the virtual machine"
2. When I try to turn on the VM from vCenter Server getting message: "No host is compatible with the virtual machine"
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
can you screenshot the VM folder.
the VM is not currently running but hung ?
the VM is not currently running but hung ?
ASKER
Could you delete the 2 attachments please after you view it OR can you tell me how to remove it please.
what is the storage free space on the LUN ?
is all the VM folder data?
did you know you have many snapshots on the VM ?
is all the VM folder data?
did you know you have many snapshots on the VM ?
ASKER
1. Yes there were snapshot so we consolidated it.
2. When the consolidated took place it hung at 99%
3. In the LUN - Capacity 1.46 TB and Free 128 GB (Type VMFS 5)
4. Yes the VM Folder is Data.
5. Also, one favor:
Please delete the Data which I posted:
cgeorgeisaac
Your Comment 2015-07-29 at 12:16:44ID: 40904613
Thank you
2. When the consolidated took place it hung at 99%
3. In the LUN - Capacity 1.46 TB and Free 128 GB (Type VMFS 5)
4. Yes the VM Folder is Data.
5. Also, one favor:
Please delete the Data which I posted:
cgeorgeisaac
Your Comment 2015-07-29 at 12:16:44ID: 40904613
Thank you
Yes, okay this could be the issue with the Snapshots, they have not been consolidated....
and it's possible they still are consolidating...
what did you do, when it was at 99%
did you do anything?
you could have a hung VM, or Hung state ?
and it's possible they still are consolidating...
what did you do, when it was at 99%
did you do anything?
you could have a hung VM, or Hung state ?
ASKER
It is hung for the last 24 hours.
Did not do anything at 99 (except moved to another Host). I guess I will wait for another day and see what happens. I did read your Snap Shot article "Be Patient".
Did not do anything at 99 (except moved to another Host). I guess I will wait for another day and see what happens. I did read your Snap Shot article "Be Patient".
Something is very odd here, you would not have been able to move it to another host if a task was present!
can you check the disk properties, is it still on a snapshot ?
can you check the disk properties, is it still on a snapshot ?
ASKER
Good question:
Originally the Disk was Thin Provisioned
and now it is Thick Provision Eager Zeroed - just do not know how it happened.
Originally the Disk was Thin Provisioned
and now it is Thick Provision Eager Zeroed - just do not know how it happened.
snapshot ?
ASKER
Yes could be. Just do not know if it will automatically get fixed after few hours or it will remain stuck at 99%
Tried to power on now: Message: Another Task is already in progress. An error was received from the host.
Will keep you posted.
Tried to power on now: Message: Another Task is already in progress. An error was received from the host.
Will keep you posted.
I need you to show me evidence, not guesswork...
screenshot of the disk properties within the VM, and then I can advise you...
Okay, another task in progress,,, is
1. Snapshot continues.
2. It's crashed and burned!
Please upload screenshot, and I also need a complete list of files in the folder. to check snapshot size...
free space on the LUN is what ?
screenshot of the disk properties within the VM, and then I can advise you...
Okay, another task in progress,,, is
1. Snapshot continues.
2. It's crashed and burned!
Please upload screenshot, and I also need a complete list of files in the folder. to check snapshot size...
free space on the LUN is what ?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Great advice. I will revert back after attempting to do as per your advice. Thanks again.
ASKER
Meanwhile a quick question:
How come I do not see in the screenshot, the FLAT File when the SnapShot is created and running?
Also, is the -000001.vmdk the Delta File?
How come I do not see in the screenshot, the FLAT File when the SnapShot is created and running?
Also, is the -000001.vmdk the Delta File?
-000001.vmdk the Delta File - yes that's the delta snapshot!
Because the screenshots were created by the storage API direct calls, by your backup application, they were not created manually by the GUI....
so, I can let you know how to proceed....(it's going to be a lot of hand holding..)
Because the screenshots were created by the storage API direct calls, by your backup application, they were not created manually by the GUI....
so, I can let you know how to proceed....(it's going to be a lot of hand holding..)
ASKER
I have confirmed that there is no backup. Could you advise the next steps.
We can try this a quick way....
Is it still stuck at 99%, or task in progress ?
before we do anything we need to clear this issue.
Is it still stuck at 99%, or task in progress ?
before we do anything we need to clear this issue.
ASKER
Wow, I refreshed it and now able to power on the machine.
Not too sure what may have happened. I guess all the SnapShot Files has been removed automatically.
However, could you advise what needed to be done if the issue had persisted?
Not too sure what may have happened. I guess all the SnapShot Files has been removed automatically.
However, could you advise what needed to be done if the issue had persisted?
Please check the virtual disks, if they are writing to a snapshot ?
snapshots needs to be dealt with?
snapshots needs to be dealt with?
ASKER
Positive. Only one .vmdk file all the 000001.xxx files (delta files) have disappeared. Thanks.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
If problems persist, create a new VM and point it to the drives for the problem machine.