VMware Communities
SteDon81
Contributor
Contributor

VMWare 6: "A configuration state change operation is already in progress.."

Hi,

my configuration:

Host OS:

Windows 2003 Advanced Server SP1

Guest OS:

1: Windows 2000 Professional

2: Windows 2003 Advanced Server SP1

I'm using VMWare Workstation 6, starting and stopping my virtual machines only by use of scripts and vmrun.

When VM with a Guest OS is running, and I issue a vmrun start for the other Guest, the following message appears:

"A configuration state change operation is already in progress. Your changes will not be saved"

Behind the message, in the VMWare Workstation window, the Guest OS is starting and everything is fine.

What's the issue with this message, what is it's meaning and how can I avoid the message (often, there is no person that can click on OK)?

Regards,

Stefan D.

Reply
0 Kudos
13 Replies
admin
Immortal
Immortal

In this situation, how exactly was 1st guest OS started?

Also, is the Workstation UI running before the 2nd virtual machine is started?

Reply
0 Kudos
SteDon81
Contributor
Contributor

Hi,

\- initial condition: No VMWare process is running

\- I initiate a vmrun start "..path to 1st Guest.."

\- A VMWare Workstation window pops up showing the first guest starting

\- Some minutes later my script initiates a vmrun start " ... path to 2nd guest .. "

\- The same VMWare Workstation window reports the mentioned error and shows the 2nd guest starting in a second Tab

Regards,

Stefan D.

Reply
0 Kudos
nhatier
Contributor
Contributor

I'm experiencing the same "problem".

Has a solution been found?

Regards,

Nicolas H.

Reply
0 Kudos
SteDon81
Contributor
Contributor

Hi,

just wanted to remember that this issue still exists. It is not really serious, but for me it is relatively annoying when my server runs for several days unattended and I see after some days several such messages on the screen, caused by the every-day-restart of the virtual machines...

I offer some time for testing if you can give a hint what to test.

Regards,

Stefan D.

Reply
0 Kudos
KungFuJoe
Enthusiast
Enthusiast

Just wanted to chime in and say that I'm also having the same problem with W6. However, in my situation, I had suspended my VM, and upon trying to resume, I'm getting that message and I'm unable to resume.

Actually...it looks like it's "stuck" in the resume process. If I try to close the UI, you get the warning that a VM is powered on and gives you the option of suspend, power off, or run in background. Choosing either suspend or power off just pops up a message saying the vm is busy and to wait until it's done.

Message was edited by:

edward23

Reply
0 Kudos
nhatier
Contributor
Contributor

I found out that if Workstation is started before running the vmrun commands starting the VMs, the error message does not appear.

I just added a command to start path/to/vmware.exe directly in my scripts and the problem went away.

This workaround doesn't mean the VMWare developer shouldn't fix that problem... thanks.

Reply
0 Kudos
SteDon81
Contributor
Contributor

Hi nhatier,

well I tried your suggestion, but for me it brought no relief. I'm still getting this error message.

Is there any VMWare developer who is aware of this problem and is looking for a solution?

Thx,

Stefan D.

Reply
0 Kudos
nhatier
Contributor
Contributor

Make sure your script sleeps a few seconds after starting workstation, and before issuing the vmrun commands. This works very well here.

I do this in a batch file:

start "VMWare" /B "c:\Program Files\VMware\VMware Workstation\vmware.exe"

sleep 5

"c:\Program Files\VMware\VMware Workstation\vmrun.exe" start %vmfile%

Reply
0 Kudos
SteDon81
Contributor
Contributor

nhatier,

well, unfortunately, your solution doesn't work for me. I also put a wait in between, but the only effect is, that, after running my two scripts, I have two VMWare Windows opened, one holding both Virtual Machines, the other none, while the window holding both VMs reports the well-known "configuration state change" error...

By the way, is there any reason why you use the /B switch for the start command?

Is there any VMWare option to open each VM in a separate window, and you have it activated and I not, or anything like this?

Thanks for answer,

Stefan D.

Reply
0 Kudos
nhatier
Contributor
Contributor

The /B is to avoid creating a new command window. It may not be required.

I don't know why a new VMWare window is being created on your system, I don't see any related option in Workstation's preferences.

I have 'Run powered on VMs in background after close' and 'Show tray icon when VMs are powered on' enabled in Workstation's preferences (Workspace tab).

Reply
0 Kudos
SteDon81
Contributor
Contributor

Dear nhatier:

thanks for your replies.

Unfortunately, your solution could not help me.

Meanwhile I've tried everything: Starting vmware.exe before, waiting longer or shorter, starting vmware.exe with "start /B ...", killing all vmware.exe processes before initiating vmrun, ... - nothing helped.

Thus, again to the VMWare developers: What is that? Every time, when I issue a "vmrun start..." command per script, while another VM is also running (irrespective, whether or not that VM is running in an open VMWare window), a VMWare window opens, showing both virtual machines and this famous error message "A configuration state change operation is already in progress".

Do you have any solution for that? Or an explanation? Couldn't you at least give hope for an update solving this issue?

Thanks,

Stefan D.

Reply
0 Kudos
sbhalodi
Contributor
Contributor

I'm using VMWare Workstation 6, starting and stopping my virtual machines only by use of scripts and vmrun like you are. I am getting similar message when I STOP one VM machine and START different one. If I STOP the same machine to load another snapshot, I am not getting this error. Are you still getting the error message? If you have found any solution, please let me know. Thanks.

Regards,

Sudhir

Reply
0 Kudos
goth
Contributor
Contributor

Had the same probem as edward23 with a suspended VM. Closing VMWare and choosing "run in background", re opening VMware and choosing resume resolved my issue and successfully resumed the VM to the previous state.

Reply
0 Kudos