View unanswered posts | View active topics It is currently Fri Dec 15, 2017 1:34 pm



Reply to topic  [ 2 posts ] 
 VM_STATE_INVALID_CONFIG 
Author Message

Joined: Fri Sep 16, 2011 1:49 pm
Posts: 11
Reply with quote
Post VM_STATE_INVALID_CONFIG
I had a minimal .vmx file that I was able to poweron via vim-cmd vmsvc/power.on 80
I added some updates and performed a vim-cmd vmsvc/reload 80 and the vm failed to reload. I noticed the following /var/log/messages entries:

info 'TaskManager'] Task Created : haTask-80-vim.VirtualMachine.powerOn-1119

error 'vm:/vmfs/volumes/4e71f8a0-4f57fb5a-62eb-14feb5eae480/aas_p8core/aas_p8core_min.vmx'] Invalid transition requested (VM_STATE_INVALID_CONFIG --> VM_STATE_POWERING_ON): Invalid state

Task Completed : haTask-80-vim.VirtualMachine.powerOn-1119 Status error

AdapterServer caught exception: 07b5b748

When I enter: vim-cmd vmsvc/getallvms
Skipping invalid VM '64'
Skipping invalid VM '80'
Vmid Name File Guest OS Version Annotation

I destroyed the above VMs via:
vim-cmd vmsvc/destroy 64
vim-cmd vmsvc/destroy 80

but vim-cmd vmsvc/getallvms ((still shows them as invalid))
Skipping invalid VM '64'
Skipping invalid VM '80'



Q: What is the preferable way to clear invalid VM's ?

Q: what is the preferable way to clear an out of config VM ?
Q: Should the VM be powerOff, reload, powerOn for each .vmx update ?

NOTE: I created another minimal VM successfull that is now assigned VMID 128
vim-cmd vmsvc/getallvms

Skipping invalid VM '64'
Skipping invalid VM '80'
Skipping invalid VM '96'
Vmid Name File Guest OS Version Annotation
128 aas_p8core [datastore1] aas_p8core/aas_p8core_min3.vmx rhel4_64Guest vmx-07

Also interesting that a new vmware.log is created for this successful VM create and the old log is renamed vmsare-1.log ... would be nice if failed operations were logged or updated to the current log, rather than just to /var/log/messages as appears to be the case for this ESXi 4.1 install


Mon Sep 19, 2011 9:40 am
Profile

Joined: Fri Sep 16, 2011 1:49 pm
Posts: 11
Reply with quote
Post Re: VM_STATE_INVALID_CONFIG
Modifying .vsx files for VM directly on the ESXi server was difficult since incompatible parameters resulted in this VM_STATE_INVALID_CONFIG

Once I went to viclient access (VMware vSphere Client) it was much simpler to create and modify VM settings without encountering any such miss configuration issues. viclient is the way to go. Its a shame that there is only a windows version.


Thu Oct 06, 2011 6:27 am
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 2 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.