Farrukh

Good job and thanks I will try this out. I believe you are right about the AES-NI requirement but I think we should be good for 2.5. For now they have removed the requirements for it. Here is the article I was reading. https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html

I am using RAW for my pfsense vdisk. After upgrading to 6.8 I thought that my vdisk got corrupted. Happened to me once before hence I suspected the vdisk. I was going through process of elimination to see what will get the vm to get pass the 100% stuck state. This is what I did: Force stop pfsense vm Using cli cd /mnt/user/domain/pfsense/ mv vdisk1.img vdisk1.old (keep RAW based vdisk) touch vdisk1.img (create a file called vdisk. This is not RAW or Qcow2. This is just to get the vm to start) Even though this got me pass the 100% stuck state it doesn't matter since this mean there is no disk drive attached to the vm.

Same issue here. Went from 6.7.2 stable to 6.8. Pfsense vm stuck at 100% during initial boot. Went back to 6.7.2 for now. I do apologise for not having any diagnostics to help the cause. However, I did find something interesting during my troubleshooting. I suspected the issue was with the vdisks. Hence I started playing around with the vdisks and noticed if I create just a dummy file by using <touch vdisk1.img>. I was able to get pass the 100% hang state. Now obviously this won't work since that vdisk1.img is not really a vdisk but this test seems to confirm my suspicion. Oh well 6.9 will probably address it I am hoping.