I’ve been using OpenSUSE Tumbleweed for more than a month. I’m relatvely new to Linux. I still need Windows 10 for my Line 6 Helixs Edit software since it doesn’t have Linux support and it is not work with wine sadly. This is a guitar amp modeller wich works as an audio interface.
I always keep up to date, but since updating from 6.11.8-1.2024-12-22T10:06 to 6.12.6-12.2024-12-22T1 0:10. I get the following error when trying to start Windows 10 in Oracle VirtualBox:
VirtualBox can’t operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot
I switched off KVM modules and the VM started, but the Helix Edit software was unusable. I use it with an USB passthrough and the connection is getting lost like every 10 seconds.
I started rolling back, the VM was working, but still had the issue that device connection is lost in the VM.
I had to roll back to 6.11.8-1.2024-12-16T1 6:24, pre, zypp. Here the VM was working fine and device connection wasn’t lost once.
Now I haven’t finalized the rollback, but is there a way to find out what is causing this issue with the updates?
I update throgh the terminal with the command line: sudo zypper dup.
And yet, many other folks report it works for them … I wouldn’t avoid a possible solution based on one person’s opinion /results. It would take less than 15 minutes to test.
Good luck!
(sidenote: many months ago, my desktop would randomly / spontaneously reboot, and I spent numerous days looking for a fix. I found the fix from a bug report at kernel.org.
That thread now has 329 Replies. That bug was created Mar 2020, and it’s still open. The workaround is two kernel entries (Reply #33), so 10 minutes later, the random reboots stopped for me.
Guess what - for some folks, that workaround did not work, but for many, it is a fix. Waiting for an official bug fix isn’t always the best option, in addition to some folks’ opinions).
Yea, sometimes, it’s worth it to try a workaround. When they finally provide a true fix, you can remove that kernel entry. Good that you’re back working.
As far as any “negative effects”, I’d say “no”. The workaround will not affect performance, etc.
And as you mentioned, that workaround also resulted in a fix for the passthrough issue. So two problems eliminated with one easy workaround.
Operating systems and software can be very tricky and unpredictable at times. Got a flat tire? 90% of the time, it’s a nail, easily found and fixed. With software, it’s not always obvious what the problem / solution is.