wolfyportal

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

@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...

I've also been dealing with KVM issues these past couple of days and try to ask AI too it said Nick is build the right kernel, like the command you check but the problem seems is cpu can enter to EL2 mode(which has virtualization support) and that's the problem on bootloader so we need to wait Allwinner and radxa to fix together and also since Nick quoted the offical response on "A7A: Harware Virtualization" so I check the offical image too and have the same issue, the system also don't supported virtualization too I think this also confirms to some extent for EL2 mode switch support btw Nick also discussing this issue with others in the Discord channel seems to have yielded no results because I know very little about ARM SBC I'm unable to participate in this discussion(can only watch and test) but I think maybe this issue should be reported to official so they will know only hardware supported it but the bootloader stuck(if AI's conclusions right)