Virtualbox stopped working after the recent upgrade. I was following another thread and assuming it was because of the bug. But qemu is updated and I’ve restarted the computer, but it still doesn’t work.
Maybe the problem is unique to me. Can anyone help troubleshoot?
qemu isn’t used by VirtualBox.
I’d try running it from a terminal and see what errors are given when you launch it. It also would be good to know where you installed from and what version of TW you’re using (“recent update” doesn’t give us anything particularly specific to work with).
I just launched a VirtualBox VM on my TW system, which is running 20250405:
$ cat /etc/os-release | grep VER
# VERSION="20250405"
VERSION_ID="20250405"
I have version 7.1.6a installed:
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------------------------+---------+----------------------+--------+----------------------
i+ | virtualbox | package | 7.1.6a-1.1 | x86_64 | Main Repository (OSS)
i+ | virtualbox-kmp-default | package | 7.1.4_k6.13.7_1-8.7 | x86_64 | (System Packages)
i+ | virtualbox-kmp-default | package | 7.1.6a_k6.14.0_1-1.1 | x86_64 | Main Repository (OSS)
i+ | virtualbox-qt | package | 7.1.6a-1.1 | x86_64 | Main Repository (OSS)
Looks like I need to clean up some old kernel modules related to an earlier release, but that’s for an older kernel that I’m not using, so isn’t affecting my use of it.
@hendersj actually VirtualBox can use qemu/kvm as a backend…
https://github.com/cyberus-technology/virtualbox-kvm
https://kvm-forum.qemu.org/2024/KVM_Forum_2024_VirtualBox_6WZ70Vm.pdf
Interesting, I didn’t know that. 
Something new to play with, then.
I found that on some of my machines that something changed VirtualBox from 755 to 4755 and it is not permitted to run as root.
chmod 755 /usr/bin/VirtualBox
fixed it to run again.
Something changes the permissions on a reboot.
Here is the error that I get when attempting to run from terminal:
Waiting for VM "Windows 11" to power on...
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
I have the exact same version of Virtualbox as you and it is from openSUSE
chmod 755 /usr/bin/VirtualBox
I tried running this and restarted, but no luck.
00:00:00.994247 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Here is the error line in the log. If more of the log info is needed, let me know. There is a large amount of text there.
(Just a tip, but for larger log files, https://paste.opensuse.org is very useful)
Here is the full log file read out, if anyone can make sense of that:
Any other info I can provide to help solve this?
It’s not so easy for me to start fresh with the VM. I have two programs on the Windows OS that are licensed and supposed to be “removed” from the old system before I can install on a new one.
If the host and guest are x86_64, try configuring it to not use qemu at all. VirtualBox doesn’t need it, but can use it, as Malcolm pointed out.
Can you walk me through that a bit?
Actually I’m not sure VirtualBox is using qemu. When the first happened, I didn’t have it installed, but added because I saw that listed as a possible solution. That didn’t help, so I removed qemu. But then I noticed with an update it was installed again.
Digging into it a little bit more, it looks like it can be built to use it, but it isn’t here, so it’s very unlikely that that’s the issue here since you installed it from the openSUSE repo.
Looking at the logs, it looks like there’s an issue with hardware video acelleration - you might try disabling that in the VM configuration as a starting point.
If that resolves it, then look to the host’s video driver.
Yay!! That fixed it. I disabled the 3D acceleration in the VM and it worked right away.
But I’m not sure what I should do with the host’s video driver.
An added layer to this is that I wasn’t notified of your reply, so I went and did some trouble shooting on my own. I discovered you can install a new VM, but use an existing virtual hard-drive. So did that to access the software apps I needed and it worked fine. Maybe on install the 3D acceleration was not enabled.
Anyways, everything seems to be working fine. Thanks for sticking with me. I just wasn’t sure what action needs to be taken with the host driver.