upgraded the leap 15.6 machine the other day, there was some earlier virtualbox on that situation, but all from opensuse repositories.
after leap 16.0 upgrade, I needed use the virtualbox
Name : virtualbox
Version : 7.2.4
Release : Virt.1600.2.19
from the virtualization repo:
https://download.opensuse.org/repositories/Virtualization/16.0/
i have a simple basic debian machine as a guest in there, when i fire it up now on leap 16.0, and the debian is idling only, the local cpu of the host goes mad and has huge full load of multiple cores, I hear the fan on the host machine, I never heard it before for running virtualbox with this same debian guest machine.
the resources area inside virtualbox shows that the guest cpu is almost idle for this debian machine, but the host cpu goes into high loads and cpu consumption during these times.
i even reduced cpu cores for the guest from previously four to two in this leap 16.0 host situation having read something about these kind of things. doesnt help a bit.
secureboot is disabled on the host machine, as was before with leap 15.6 as well.
leap 16.0 kernel not very good for virtualbox currently or somethings amiss? thanks.
Working here without problems.
zypper se -si virtualbox
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------------------------+---------+---------------------------------------+--------+---------------
i | virtualbox | package | 7.2.4-Virt.1600.2.19 | x86_64 | Virtualization
i+ | virtualbox-kmp-default | package | 7.2.4_k6.12.0_160000.8-Virt.1600.2.15 | x86_64 | Virtualization
i+ | virtualbox-qt | package | 7.2.4-Virt.1600.2.19 | x86_64 | Virtualization
I am seeing something similar on a Tumbleweed host, so there is something going on with the last few versions of openSUSE VBox and/or recent 6.x kernels…
my kmp package is slightly differing in version at the end:
7.2.4_k6.12.0_160000.8-Virt.1600.2.13
other than that. where is your .15 from?
okay apparently my virtualization repo from above had a wrong prio, my package came from @system or so it showed, I am not very familiar with these parts of the system. thanks.
Why not showing as requested in #5?
@system means:
The packages is not available in any of your enabled Repositories.
This is clear because when a new virtualbox-kmp-default is build, the old will be deleted in the Repo and is not available any more.
So sdow your Repo list andf we can see, if there is something to do.
Apparently we are not alone, what I see here is huge VMM load like described in this VirtualBox forum post which links a ticket that has been open for 5 years now…
i can only compare the situation on 15.6 before and the virtualbox version from that os level and from that that is available for leap 16.0. i am only using the opensuse provided stuff, built on their buildservice, infrastructure and these things. so i dont understand that disucussion and its relation to the change between 15.6 and 16.0. thanks.