"Stopped" does not work correctly.

[macgebruiker]

I am unable to edit my VM settings.

When I doubleclick a .PVS of run Parallels and choose the wanted VM. I see the screen with VM info. This screen also says the VM is stopped.

However before I have time to check 'edit ->VM Settings' the VM is started (booting) and I cannot change any settings.

How do I solve this?

 

[drval]

I am unable to edit my VM settings.

When I doubleclick a .PVS of run Parallels and choose the wanted VM. I see the screen with VM info. This screen also says the VM is stopped.

However before I have time to check 'edit ->VM Settings' the VM is started (booting) and I cannot change any settings.

How do I solve this?

Use Text Edit and load the relevant <name>.PVS file AS IF it were just a text file you wanted to edit. Then look for the following:

Start auto = 1
AutoShutdown = 0

1 = TRUE whereas 0 = FALSE. Make sure at least ONE of those is set to 0, ie FALSE, and you'll be able to edit the file even while Parallels is running, but the VM is not.

BTW, once you've edited the file, it should continue to populate the "Open Recent" list of Text Edit, so that will make it easier to edit it again, later.

 

[macgebruiker]

Use Text Edit and load the relevant <name>.PVS file AS IF it were just a text file you wanted to edit. Then look for the following:
Start auto = 1
AutoShutdown = 0
1 = TRUE whereas 0 = FALSE. Make sure at least ONE of those is set to 0, ie FALSE, and you'll be able to edit the file even while Parallels is running, but the VM is not.
.

They were both 0 (zero). I changed the autoshutdown to 1 but that did not solve the problem.
The I tried startauto=1 and autoshutdown=0. No effect either.
Also tried both at 1, no effect.

So independent of the settings the VM is started. This happens with my 4 different VM's that I created.

 

[drval]

They were both 0 (zero). I changed the autoshutdown to 1 but that did not solve the problem.
The I tried startauto=1 and autoshutdown=0. No effect either.
Also tried both at 1, no effect.

So independent of the settings the VM is started. This happens with my 4 different VM's that I created.

I don't understand how that is happening -- or you certain that you're using THOSE pvs files and not some others when starting up the VM? Perhaps there is some other configuration that is relevant -- are you staring up the VM in OS, Full Screen or Coherence mode?

 

[macgebruiker]

I don't understand how that is happening -- or you certain that you're using THOSE pvs files and not some others when starting up the VM? Perhaps there is some other configuration that is relevant -- are you staring up the VM in OS, Full Screen or Coherence mode?

I doubleclick on the .PVS file so this should eliminate the chance of mixe-ups.

All VM's are started in a Window. Presently I use the latest release 2.5 (build 3150) but the previous (beta) had the same problem.

Is there an easy way so that I could start with a blank PVS? Then I could do all the settings and this might eliminate some contradiction.