.xml-prev is actually .xml-new

[ToddAndMargo]

Hi All,

After upgrading from 3.2.8 to 3.2.10 and having my .xml file corrupt out, I noticed that you guy made me a backup of my .xml (VB-WinXP.xml-prev). Mighty nice of you guys.

Problem: the -prev is not a backup of the previous version. It is an exact copy of the new version, as shown by md5sum. I restored my .xml from backup (VB-WinXP_10-08-2010.xml) and the next time the update did not corrupt my .xml.

It would be nice if the .xml-prev was actually the previous .xml.

Many thanks, -T

# ls -al

-rw------- 1 todd users 8621 Oct 12 23:42 VB-WinXP_10-08-2010.xml -rw------- 1 todd users 8555 Oct 15 12:00 VB-WinXP.xml -rw------- 1 todd users 8555 Oct 15 12:00 VB-WinXP.xml-prev

# md5sum VB-WinXP_10-08-2010.xml VB-WinXP.xml VB-WinXP.xml-prev 15d2b9ac8c30f6b2193b53b411dcf4e3 VB-WinXP_10-08-2010.xml dbe4f92bc1a1ea15682336113f210700 VB-WinXP.xml dbe4f92bc1a1ea15682336113f210700 VB-WinXP.xml-prev

[bird]

Afraid this is just a result of the config file being saved even when there are no actual changes. This is typically the case when closing the VM window and the GUI writes its extra data entries. The xml-prev stuff wasn't really meant as a backup. It's more a little insurance against (1) losing important files when recovering from a crash, and (2) ditto when running out of disk space. That said, we might want to address these unnecessary saves at some point though, since avoiding hitting the disk with duplicate data could be considered a little optimization as well as increasing the value of the .xml-prev for backup purposes.

[ToddAndMargo]

Maybe you could call the actual previous xml "-prev" and the current one "-new". Be nice to have a backup, when changes are made.