Thank you very much for that!

thank you for adding information about big.LITTLE seems that will be the next issue when we need to work virtualization on A7A/A7Z but for now, we seems facing the problem during the boot process CPU in the wrong exception levels(model) so the virtualization is not support in any situation(my guess) also Nick thought it's about u-boot issue and used the official binary image so we might need to wait for official update or we need to work by ourself

May boot from new / known-to-work Armbian on SD-card and use command: sudo lsblk and/or sudo lsblk -f to see what is what. mmcblk numbers have swapped sometime in the past years, so indeed even if you know enough about Linux, mixing numbers might be a disater because you would overwrite the runnig installation. That might also be a reason why tooling might refuse or not list as there is a risk of having it wrong. But you should clean-up the 100% full filesystem. It will take time figuring out what should be deleted, but so does going to the toilet as well. It has to be done, cannot assume there is endless space.

Radxa staff actually does not answer the original question w.r.t. Allwinner A733 HW virtualization, it is just that kernel config has it. But I see from releases 'bullseye', that does not look good at all. In theory, that means 5.10 kernel, and oldoldstable libvirtd/KVM/QEMU etc. As this SoC is bigLITTLE, (Cortex-A76 Cortex-A55), starting a qemu-system-aarch64 process will pick some of those cores randomly, assuming you have more than 1 vCore (smp option > 1) . Kernel older than 6.8 or so does not support moving between an A76 and an A55. That is the same for Rockchips (RK3588). It took me quite a while before I discovered that this is known behavior. So on for example on vendor rk35xx 6.1.115, I pin vCPUs, can be done in virt-manager GUI xml config or cmdline via taskset. As easy test, use -smp 1, then it should work. mainline kernel CPU numbers are such that simplest/lowest CPU's get lowest number. That might be the other way around on 6.1 or older downstream/vendor/BSP kernels. On an RK3588, a 2-core VM with 2x A76 and 512MiB is done by: taskset --cpu-list 6-7 qemu-system-aarch64 -M virt -cpu host -enable-kvm -m 512 -smp 2 \ -bios u-boot.bin \ -drive if=none,file=armbian.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -netdev bridge,id=hn1 -device virtio-net,netdev=hn1 \ -nographic Same should work on A733

@Linlunson same, I want to run pxvirt on it but now I can only play some container with docker without virtualization funny thing even old raspberry pi can use kvm feature but this "new" allwinner chip can't this out-of-the-box support this besic feature I think I was also deceived by radxa's staff in some way https://forum.radxa.com/t/a7a-harware-virtualization/29745 anyway I also test on Nick's image, but mean the offical image from radxa https://github.com/radxa-build/radxa-a733/releases and it also not work(still stuck on EL1) so I think maybe Nick is do everything he can do issue might on bootloader I asked about the cpu exception levels on discord channel sometime radxa's staff will answer in there too or maybe someone knows about this we just needs standby...