VMware Cloud Community
sfont3n
Enthusiast
Enthusiast

VM wont boot

Host are 3.0.2. after i upgrade vc to 2.5 if i power off a vm then try to power it back on i get an error saving "The request refers to an object that no longer exist or has nerver existed"

has anyone seen this

Reply
0 Kudos
12 Replies
Chamon
Commander
Commander

Sounds like you may have to re import the vm.

Goto configuration tab of host => storage => brows the LUN where the vm is located and open it directory, find the .vmx file right click it and add it back to the inventory. Is the host in the inventory? You may have to readd the host as well.

Reply
0 Kudos
sfont3n
Enthusiast
Enthusiast

its in a cluster. i removed the host from the cluster and was able to power on the vm. not sure what it is

Reply
0 Kudos
Chamon
Commander
Commander

Now ad the host back to the cluster.

Reply
0 Kudos
sfont3n
Enthusiast
Enthusiast

yes i know i need to add it back to cluster. i bet it happes to all vms on different hosts

Reply
0 Kudos
steven_catania
Contributor
Contributor

Crazy as this sounds....when the Vm is off do you have an option after right clicking on it to upgrade virtual hardware? Try that, then turn it on.

Reply
0 Kudos
sfont3n
Enthusiast
Enthusiast

still having this issue. if i take the host out of clster vm will power on. i tried to register it again and it still would mnot boot

Reply
0 Kudos
Chamon
Commander
Commander

Check your HA settings. Are you going over your resource availability limit? You can try to change the HA setting to allow constraint violations and then try to power it up. If it powers it up then that would be the problem.

Are you still getting the same error as above?

Reply
0 Kudos
sfont3n
Enthusiast
Enthusiast

yes

i created a new cluster move host into a there and vm booted. i restarted the vc service readded host to cluster with issue and vm booted

Reply
0 Kudos
Chamon
Commander
Commander

Strange! Well glad that you got it worked out.

Reply
0 Kudos
sfont3n
Enthusiast
Enthusiast

i will post the results if there is a fix

Reply
0 Kudos
leeabner
Contributor
Contributor

Thanks for the tips. Had the same problem, restarted the Virtual Center service and then it let me start the machines.

Reply
0 Kudos
lalonghorn
Contributor
Contributor

Had the same issue with a Win2k3 system after an upgrade to VCS 2.5. The solution was to take note of the location of the VM on the SAN, remove the VM from inventory, and then add the VM back via browsing the datastore. The support engineer I worked with also mentioned that ESX 3.02 + VCS 2.5 is likely to behave awkwardly (paraphrasing here) and recommended upgrading ESX to 3.5.

Reply
0 Kudos