VMware Cloud Community
bsteffey01
Contributor
Contributor
Jump to solution

ESX Host error - Virtual Machine Creation may fail

Anyone ever see this error Virtual Machine Creation may fail because agent is unable to reteive Virtual Machine creation options from the Host

Reply
0 Kudos
1 Solution

Accepted Solutions
kjb007
Immortal
Immortal
Jump to solution

Don't forget to leave points for helpful/correct posts.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB

View solution in original post

Reply
0 Kudos
9 Replies
kjb007
Immortal
Immortal
Jump to solution

Did your host go into disconnected mode while you were creating the vm? Did this error occur before/after, during a wizard, or some other process?

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
bsteffey01
Contributor
Contributor
Jump to solution

ESX server was upgraded from 3.0.2 to 3.5 Update 4, It had been disconnected in VC when upgrade was being done, after upgrade was complete and host showed up as connected agai in VC is when I noticed that error, it is still in maintenance mode.

Reply
0 Kudos
kjb007
Immortal
Immortal
Jump to solution

So, if you take host out of maintenance mode, does it allow you to create a vm?

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
bsteffey01
Contributor
Contributor
Jump to solution

I just tried exiting maintenance mode and I got an error The session is not authenticated. Is there a way to reauthenticate the host using some sort of esx command?

Reply
0 Kudos
kjb007
Immortal
Immortal
Jump to solution

Remove the server from vCenter. Log into the ESX host. Remove the vpxuser. Make sure your hostname is correct on the ESX server's /etc/hosts file. Make sure it is all lower case. Then, re-add to vCenter using fully qualified domain name.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
bsteffey01
Contributor
Contributor
Jump to solution

This appeared to work, thanks!

Reply
0 Kudos
kjb007
Immortal
Immortal
Jump to solution

Don't forget to leave points for helpful/correct posts.

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
dschingis
Contributor
Contributor
Jump to solution

Hello

I have the same problem on different hosts in my cluster.

4 Hosts

ESX Version 3.5.0 build 130756

VirtualCenter 2.5.0 build 174768

I added my hosts by IP-Address, not FQDN. Normaly i think, IP are the best way because no naming problems. But if i read your hint "add host with FQDN", i ask why?!

Can you explain why by name and not by IP? Or did you think thats not the problem?

If you need additional informations, i give it.

cu

Jochen

Reply
0 Kudos
jjgunn
Enthusiast
Enthusiast
Jump to solution

VMWare KB

KB resolved this issue. Restart mgmt services.

Reply
0 Kudos