Click on the banner to learn about and purchase my database training on Azure

VMware Player - Using independent nonpersistent disk mode

Views: 657 views
Reading Time: 2 minutes

Speak guys!
In this article today I’m going to talk about a very different topic than what I usually address here on the site, which is VMware Player, a free virtualization software from VMware that I use to create my study VMs, labs and where I create content for this blog .

A long time ago, when I started in this world of virtualization, I started with VirtualBox and then got to know VMWare Workstation Pro, where I used it for a few days in the Trial version to test its functionality and really enjoyed the tool, making me switch from VirtualBox to VMware. Player

However, after this exchange I realized that one of the coolest features I liked about VMware Workstation I didn't have in the Player (free) version, which is to choose how to use the disk as persisted (changes are recorded directly to disc) or nonpersistent (changes are NOT written to disk and are discarded when you turn off the VM), which is very useful for testing software and routines that can damage your environment, such as viruses and ransomware (theme of my next article):

Only after a long time when I installed the Trial version just to create these VMs with independent nonpersistent mode I found that even in the Player version of VMware was possible to use this read mode, even without interface.

To change this VM parameter, simply edit the VMX extension file and add the entry below, taking into account the disk ID on the VM and the disk type (SCSI, IDE, etc.):

Just like the example below:

After reopening the VM in the software, we can already see that the change made to the file was actually applied and the disk mode changed:

Ready! You can comfortably test on your VM that by turning it off and back on, everything you did in the session will be undone immediately and it will return to its previous state. Remember that you can restart the VM quietly and it will be started keeping the changes you made in the session. Just by shutting down the VM or rolling back a snapshot the changes are undone (in fact, not even written to disk)

I hope you enjoyed this post very fast, short and objective and until the next article!
Strong hug!