Yes, it (virtualbox VMs) worked before the bios update. I re-ran the module install, and also reinstalled the whole package, svm is listed by “cat /proc/cpu” for each cpu. Something changed with the bios update.
The full error message:
VirtualBox can’t enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).
I used the EFI shell updater, yesterday; all working great so far. Including staying suspended when plugging/unplugging power, and closing the lid, while still being able to wake with a keyboard button press.
I use VMs alot so this was an important check for me also. Default settings on bios inc auto gpu memory.
No issues with virtualbox OS edition(ubuntu repo) on 24.04, I did install boxes and it complained about not being able to access the kvm module though. This was the first time i ran boxes though so cant rule out misconfiguration gremlins.
svm and svm_lock are both in my cpu information. framework 13 7640u / 24.04.1, 32gb kingston 5600 jdec ram
Fixed. The problem was not the new bios, but an incomplete removal of VMWare workstation. Once I removed the kvm_amd module and reinstalled it virtualbox VMs ran fine. Sorry for the false attribution.
Correction. Kernel 6.12 defaults to automatic kvm loading, and blocking that fixed the issue (kernel command line addition: kvm.enable_virt_at_load=0, thanks to Mario L., aka superm1). VMWare residuals were probably not the problem.
Yeah, I updated the kernel, the new BIOS, a new beta release of virtualbox, and installed (and removed) vmware workstation pro all in quick succession. Bad, bad, bad sysop behavior.
The beta virtualbox had a minor bug with guest additions not running the standard video mode properly, VMware didn’t uninstall its kernel modules, the 6.12 kernel update changed kvm loading (the actual cause of the failure), all adding to my self-caused confusion.
I was also asking this as the current FW16 BIOS 3.05 has an “imortant note” saying:
After updating to this version you will not be able to downgrade to an earlier version.
I understand that this means you can’t downgrade the specific BIOS upgrade for the FW16.
Now the notes to this FW13 BIOS update do not mention this topic.
But since this is a very important fact, I want to know if this BIOS upgrade can be downgraded again. @Kieran_Levin : could you please let us know?
@everybody else: please do not answer if you don’t know for sure (f.e. made the downgrade yourself).
I have the exact same problem as you, the 2.8k screen works fine on my 7640u, but the diagnostic led came on a short while after booting into Windows. I just updated to 3.06 and at the moment, it seems the diagnostic led problem is gone.
