I am trying to configure a VMware VM to have a non-persistent disk. This is as simple as making the disk independent f the VM, and selecting the non-persisent option. How do I do this in VMWare fusion?
For some reason VMware Fusion 5 (Even VMware Fusion 5 Professional) lacks a UI option to create Independent, Persistent VMDKs. But it can easily be done in the
.vmx file using a text editor:
VMware documentation about changing disk mode says that the disk must not have any snapshots, so you may need to delete all snapshots. Consider making a backup first
- Shut down your virtual machine and quit VMware Fusion. (Yes, this is necessary)
- Locate the Virtual Machine's package in the Finder. Right click on it and select "Show Package Contents"
- Locate the
.vmxfile and open it with a text editor (you can right click and select "Open with > Text Edit")
Search through until you find the line containing name of the virtual disk (vmdk) which you want to make persistent. It should look something like:
scsi0:1.fileName = "Virtual Disk-000001.vmdk"
(Though it might be
ide0:0, or the bus numbers might be different)
Add below that line the following:
scsi0:1.mode = "independent-nonpersistent"
Make sure to match the bus description. So if your device is
- Save the file and relaunch VMware Fusion, you should be good to go.
It seems you may be over thinking this. Why not just boot the live .iso version of your OS?
I can't say if that's what you want to do particularly since whatever OS you want to use may not be a "live" version. But if you don't "install" to a virtual hard drive then there's almost never any worry about any persistence.
I do it all the time in Virtual Box. I may have to specify a virtual hard drive like a VHD file when installing the machine but that doesn't mean I actually have to install to that drive. In fact, I just delete the virtual hard drive in the machine settings so there's no choice but to boot whatever .iso image I specify. End result, a fully functional virtual OS with absolutely no persistence.
Then again, if we're talking about something like Puppy Linux then even an .iso image might get modified. That's one of Puppies advantages - it's ability to save persistence info to the very disk it booted from.