Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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?

share|improve this question
add comment

2 Answers

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:

  1. First, shut down your virtual machine and quit VMware Fusion. (Yes, this is necessary)
  2. Locate the Virtual Machine's package in the Finder. RIght click on it and select "Show Package Contents"
  3. Locate the .vmx file and open it with a text editor (you can right click and select "Open with > Text Edit")
  4. 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)

  5. Add below that line the following:

    scsi0:1.mode = "independent-persistent"
    

    Make sure to match the bus description. So if your device is ide0:0 you'd write ide0:0.mode

  6. Save the file and relaunch VMware Fusion, you should be good to go.

I think the virtual disk in question must not have any snapshots if you make it independent-persistent, but I am not sure.

share|improve this answer
add comment

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.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.