I am a decade long FreeNAS/TrueNAS user and just upgrade to from Core to Scale. I feel like a total newb again and it really sucks.
Currently, I am stuck reintalling a VM which bootlooped after the upgrade. I deleted it to start over. Unfortnately, I cannot find the proper permissions for the existing iso files in my dataset. When I start the VM, I get
[EFAULT] internal error: QEMU unexpectedly closed the monitor (vm=‘30_fred’): 2026-05-22T23:05:02.062877Z qemu-system-x86_64: -blockdev {“driver”:“file”,“filename”:“/mnt/support/iso”,“node-name”:“libvirt-2-storage”,“read-only”:true}: Could not open ‘/mnt/support/iso’: Permission denied
How do I fix this please?
I also set permissions recursively for owner@ - libvirt-qemu and group@ - libvirt-qemu to Allow/Full Control, but this did not help
Just root:root and 444 should suffice for ISOs.
I deleted all isos and the data set, then recreated it and EVERYONE full control, will figure out later how to narrow this down.
This now loads the Windows Server 2025 initially but after the initial bar is complete, this just boot loops. Not sure if the SPICe web interface is the issue. Completely puzzled.
It seems the problem is windows server 2025 version. 2019 loads fine. not sure what i am missing, on Core this worked just fine.
How are you defining your VM and devices?
- System clock should be local
- Hyper-V enlightenments should be enabled
- TPM should be enabled
- CPU should be a recent Intel model, like Cooper Lake
- GPU box for ensure display device should be checked
- Use VirtIO for all your disk and NIC devices, and load the VirtIO drivers during the install
This is an older CPU Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz. I tried enabling Hyper-V enlightenments and TPM, but the hardware likely does not support this. Nevertheless, on Core this worked just fine in bhyve. Any way to fudge this?
Ok, you have to select “Secure Boot” to access the Q35 machine type that supports Server 2025. Otherwise, the machine type has legacy components that don’t have driver support in Server 2025, which results in the boot loop.
Thank you @Samuel_Tai . I will play around with this some more using your hints. I may take a break soon but will report back. I appreciate the prompt back and forth and I apologize for my slight agitation 
I can relate after a Core→Scale migration myself. 
ok, I think I am in business now. There is a CPU Model setting for the VM, which shows as optional. However, it is not! I now set this to Ivy Bridge v2, which corresponds to my CPU generation, and now Server 2025 and Windows 11 are booting!
