We downloaded the latest version of the ontap simulator (9.13.1) and deployed the .ova on our vmware esx-cluster.
No matter what we're doing with the new VM, after starting the first time and finishing the initial setup, every time the VM has to be rebooted for any reason, the bsd doesn't boot anymore.
That happens in any case. Even if the VM is forced to restart after the initial setup, without doing anything with it. We also tried to finalize the normal cluster-setup. All is working fine until the restart.
We also tried it with more RAM (8GB, 16GB) but nothing changes the result, VM always stops at the same point after restart.
As an additional information: During the first start of the VM (which works normal), we noticed that the VM displays double the amount of RAM than we provided for the VM. Even if the VM is configured with 6 GB of RAM, the displayed amount is 12 GB. If we configured 8 GB, the displayed amount is 16 GB. If we configured 16 GB, the displayed amount is 32 GB.
We checked this issue with an older version (9.12.1). There both values are corresponding. 8 GB configured and 8 GB displayed while booting.
I am having the exact same issue. It works until I have to reboot, then fails to load at the same spot. See https://community.netapp.com/t5/Simulator-Discussions/Issue-with-ONTAP-Simulator-9-13-1/m-p/446223
have you checked if your freshly deployed VM displays double the amount of RAM which you configured for the VM prior to the first start? (Like shown at the screenshot of my 2nd post). Perhaps it's a bug within the ova itself.
Yes, agree something up with 9.13.1. It doesn't matter how much memory/cpu is given, it simply hangs when it goes for a reboot. Only way I have managed to get it to work, is by restoring it to the working-snapshot of the console when it was first setup. I guess, as this is a simulator, it will be difficult to get any update on the root cause of this simulator build.