Am Donnerstag, 27. August 2020, 07:14:50 CEST schrieb Larry Finger:
On 8/25/20 1:38 PM, Stefan Brüns wrote:
On Dienstag, 25. August 2020 19:13:44 CEST Hans-Peter Jansen wrote:
Hi,
FYI: Virtualbox 6.1.97, fetched from SVN, and built here: https://build.opensuse.org/package/show/home:frispete:kernel/virtualbox does work including USB-{2,3} support, given the extpack r140056 from https://www.virtualbox.org/wiki/Testbuilds is installed properly.
No kernel patching nor driver patching necessary. Well, internally, I'm using (an unpatched) kernel 5.8.3 from stable tree, but apart from USB-{2,3} support, that was missing due to an extpack mismatch, this was tested with 5.8.0 as well.
Be aware that the Extension Pack, unless you purchase an Enterprise license, is limited to Personal and Educational use. And no, "Homeoffice" definitely does not qualify for Personal use.
The licensing is exactly the same whether you use the openSUSE packages, or if you download from an Oracle website.
@pete: I am trying to backport the 6.1.97 changes to our 6.1.12, but I am at an impass. No matter what I try, I keep getting the VERR_NO_EXEC_MEMORY error. If you have any suggestions, let me know.
That's exactly the result, that I tried to communicate in https:// bugzilla.suse.com/show_bug.cgi?id=1175201, but obviously failed. Sorry. The procedures you described there just didn't fit together. When made to fit, you named the result two paragraphs above. I suspect, the problem is due some subtly changes in the core, although I went through the changesets between 6.1.12 and 6.1.97 several times (after mostly cleaning up the damn SVN tags from SVN master with a script in order to reduce the diff (attached)). At this point, and because the VB OSE SVN doesn't provide any branches, I decided to move on. The official 6.1.97 test build failed for me as well, but incorporating 6.1.97 into your base package and adjusting the patches (but a few, that I disabled), succeeded. That's the result, that I published. Some users, that I care about, likes the ease, that VB provide in managing VMs, so do I. This comes with legal, architectural and organizational restrictions. Like you, I invested way too much time into this issue already. Therefor I'm going to migrate some critical VMs to kvm (@Stefan: that never used/needed the extension pack) in order to avoid such a situation in future. As a fun fact, the extpack well deserves the license limits, since activating the USB pass-through scheuentor is a security nightmare, that should be avoided at all costs in any commercial setups. Cheers, Pete