[TrueNAS VM - snapshots of VMs vdisks and recognizing changes]

I rewatched Spaceinvader video and I noticed, that:
1. His Windows vdisk is in /mnt/remotes/zfs_vms/sandbox_windows_10/vdisk1.qcow2
2. There are 3 snapshots:
- Neo/vm-storage/big_sur
- Neo/vm-storage/sandbox_windows_10
- Neo/vm-storage/
When he uses Rollback, he selected "Neo/vm-storage/" and not "Neo/vm-storage/sandbox_windows_10" which means, that changes in "big_sur VM" were also reversed (if there were any).
I checked this in on my system and it works. Rollback on snapshot BACKUP_POOL/VMs restores my Manjaro.

So it looks like the vdisk has to be under another Dataset to recognize the changes, in my test example it looks like this:
Pool:
BACKUP_POOL/VMs/TEST2/TEST3

 

NFS share in Unraid:
nfs    TRUENAS:/mnt/BACKUP_POOL/VMs/TEST2

 

VM vdisk location:
/mnt/remotes/TRUENAS_TEST2/TEST3/vdisk1.img

 

I did Snapshots and Rollback for:
BACKUP_POOL/VMs/TEST2

 

 

EDIT:

I found better solution. Instead creating additional Dataset, just create a Folder inside existing Dataset and place there the vdisk

 

 

[TrueNAS VM - snapshots of VMs vdisks and recognizing changes]

I'm running TrueNAS as VM and I want to do snapshots of other VMs - just like in Spaceinvader Video "Ransomeware VS Snapshots with VMS". The problem is that TrueNAS doesn't recognize changes on vdisk- I can create snapshot, then save couple files in VM, turn VM off, Rollback (with "No Safety Check") and the files are still there. I assume it's because vdisks have always the same size, but somehow it worked by Spaceinvader. Is there something I forgot to change in TrueNAS or VM?

 

My pool looks like this:

BACKUP_POOL

      VMs (Dataset)

             Manjaro (Dataset)

 

I do snapshot for BACKUP_POOL/Vms/Manjaro

 

 

[pfSense VM on a Ryzen 5 5600X = fatal trap 12]

I had this same issue on my CPU (5900) and it looks like 6.10RC2 solves it. Maybe the devs will mention something about this in the changelog, after the new version becomes stable.