Hey does anyone know if an updated Virtualbox that works with kernel 7.0 is in the Zorin repo now since the Zorin Dev/Bros FIX?
Or do we need to goto Virtualbox's site to download a compatible version?
Hey does anyone know if an updated Virtualbox that works with kernel 7.0 is in the Zorin repo now since the Zorin Dev/Bros FIX?
Or do we need to goto Virtualbox's site to download a compatible version?
I understood that you can use the normal virtual box package now in kernel 7.0 after applying the new updates and fixes.
But please wait that someone else confirms this.
Yes, that is confirmed.
VirtualBox from the Zorin REPO Installed fine and DKMS Status shows no errors:
scott@scott-Falcon-Talon:~$ sudo dkms status
nvidia/580.159.03, 6.17.0-40-generic, x86_64: installed
nvidia/580.159.03, 7.0.0-28-generic, x86_64: installed
virtualbox/7.0.16, 7.0.0-28-generic, x86_64: installed
BUT WHEN I TRY AND START WINDOWS 11 IN VIRTUALBOX I AM GETTING AN ERROR - SEE PIC BELOW:
Maybe try a Reinstall of VirtualBox.
I did un-install and re-install
Another user showed the same issue...
Can you try this and see if it makes any difference?
I tried still got the error when trying to launch Win 11 using Virtualbox
Looking at your posted error...
VERR_SVM_IN_USE
In the other thread, it is VERR_NOT_AVAILABLE.
It looks like KVM is in use, so VB cannot use it. Can you try (since you are using AMD):
sudo modprobe -r kvm_amd
sudo modprobe -r kvm
scott@scott-Falcon-Talon:~$ sudo modprobe -r kvm_amd
[sudo] password for scott:
modprobe: FATAL: Module kvm_amd is in use.
So something is actively using it.
But what?
sudo lsof | grep /dev/kvm
scott@scott-Falcon-Talon:~$ sudo lsmod | grep kvm
[sudo] password for scott:
kvm_amd 253952 1
kvm 1507328 3 kvm_amd
irqbypass 16384 1 kvm
ccp 188416 1 kvm_amd
Eh... That only shows what we know - that 1 process is using it.
What about
sudo fuser -v /dev/kvm
For grins I did a Time-shift back to 6.17.0-40-generic and have Oracle Virtualbox running Win 11
See screeny below:
Now not running Virtualbox:
From this, I do not know about you but, it looks to me like there is still an issue with the 7.0 kernel and the stable VirtualBox package in the repository.
I am not sure what it is, or how to solve that in this moment.
But too similar reports right after the 7.0 kernel conflict suggest that these are not isolated cases.
I think the proper course is to redirect this to the Zoringroup.