Any way to force a VM to start if the user doesn't have WRITE rights?

[jeremym]

Here's the scenario:

1. I've taken ownership of the VMX file and prevented a standard user on the box from editing it.

2. Now that VM refuses to launch.

Basically, it seem that if the VMX file isn't WRITE-able by the user, then VMware Workstation falls over and dies.

I wouldn't have guessed that.

I would have supposed that it would simply:

a. Read what it could from the VMX file.

b. Launch.

c. Write files in the folder if it needed to.

But it doesn't.

So.. is there some secret way to, say, inside a VMX file.. give it a parameter to say "Launch anyway, even if the VMX file itself is not writeable?"

Thanks in advance.

[continuum · Accepted solution]

I use a workaround to run VMs from CDs - which is similar to your need.
Before copying the VM to CD I create a snapshot but do not start the VM.
Then to run the VM from CD I create a temp directory and copy the vmx and the small snapshot vmdk into it. Then I fix the path in the snapshot-vmdk descriptor so that I points to the basedisk on CD. Then I can start the copied vmx-file.
I found no other way to start VMs from readonly vmx-files

[jeremym]

Interesting. I will have to give that a try. VERY helpful answer (as usual.)

Thanks !