Package Details: virtualbox-bin-sdk 6.1.38-1

Git Clone URL: https://aur.archlinux.org/virtualbox-bin.git (read-only, click to copy)
Package Base: virtualbox-bin
Description: VirtualBox software developer kit for use with virtualbox-bin package
Upstream URL: https://www.virtualbox.org/
Keywords: machine oracle virtualization vm
Licenses: GPL2, custom, BSD, LGPL2.1
Conflicts: virtualbox-sdk
Provides: virtualbox-sdk
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 57
Popularity: 0.000027
First Submitted: 2015-08-18 09:16 (UTC)
Last Updated: 2022-09-03 17:13 (UTC)

Dependencies (3)

Required by (9)

Sources (12)

Pinned Comments

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

dbermond commented on 2022-09-03 17:13 (UTC)

@drankinatty Package updated.

drankinatty commented on 2022-09-02 05:50 (UTC)

6.1.38 is out with support for Linux 6.0 kernel. (for once Oracle is ahead of the kernel)

j77h commented on 2022-07-24 14:13 (UTC) (edited on 2022-07-24 14:31 (UTC) by j77h)

@Ralf_Mardorf: I should have come back a month ago to say that Vbox 6.1.34 worked fine after I upgraded my kernel to 5.18; found that trick here: https://forum.manjaro.org/t/virtualbox-error-in-the-last-update/113744/ Haven't upgraded vbox yet as I use Manjaro stable and 6.1.36 is in testing atm. (That's from community repo; I don't use this AUR package, and came here only when my vbox 6.1.34 wasn't working. As that turned out to be fixable by upgrading to kernel 5.18, I didn't need to try this AUR vbox package.)

Ralf_Mardorf commented on 2022-07-24 13:00 (UTC) (edited on 2022-07-24 13:05 (UTC) by Ralf_Mardorf)

Hi, with virtualbox-bin 6.1.36-1 and 6.1.36-1 extensions I can't start a Windows 11 guest anymore [1]. The used 4.19+ rt-patched kernel is a LTS kernel supported by kernel.org. After downgrading [2] to 6.1.34-2 and extensions 6.1.34-1 everything is working again, despite of the depmod warnings . Regards, Ralf

[1]

Failed to start the virtual machine winos11.

Failed to load R0 module /opt/VirtualBox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuEnd' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
$ pacman -Q virtualbox-bin; uname -a
virtualbox-bin 6.1.36-1
Linux archlinux 4.19.246-rt110-0.1000 #1 SMP PREEMPT RT Tue, 14 Jun 2022 11:29:01 +0200 x86_64 GNU/Linux

[2]

$ sudo pacman -U virtualbox-*
[...]
warning: downgrading package virtualbox-bin (6.1.36-1 => 6.1.34-2)
warning: downgrading package virtualbox-bin-guest-iso (6.1.36-1 => 6.1.34-2)
warning: downgrading package virtualbox-bin-sdk (6.1.36-1 => 6.1.34-2)
warning: downgrading package virtualbox-ext-oracle (6.1.36-1 => 6.1.34-1)
[...]
==> depmod 4.19.246-rt110-0.1000
depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/4.19.246-rt110-0.1000: No such file or directory
[...]

j77h commented on 2022-06-20 13:04 (UTC) (edited on 2022-06-20 14:53 (UTC) by j77h)

EDIT: I've had some unexpected restarts that I don't think were Windows' fault, so these updates don't seem to have compleetely fixed it.

Manjaro has pushed these to stable:

linux515 5.15.46-1 → 5.15.48-1
linux515-virtualbox-host-modules 6.1.34-14 → 6.1.34-17

(also linux 5.10, but I'm only reporting for the one I actually use)

VBox is [edit: NOT] running fine for me now.

j77h commented on 2022-06-20 04:04 (UTC) (edited on 2022-06-20 04:16 (UTC) by j77h)

I'm using 5.15, which is affected, and someone on the vbox forum mentioned that 5.10 is affected. Don't know about any kernels further back.

Currently it seems that the solution is to downgrade kernel minor version and/or downgrade vbox to 6.1.32; don't know if I need to do both or if only one is enough.

Fedora people report that vbox 6.1.35 test version works, so I would rather run that, but don't know (or have time to figure out) how to convert the .run file to an Arch/AUR package. (Don't know if that's even necessary; will have a look, see if its contents can run from a manual placement.)

I don't understand all the details -- just an end-user who needs to do a bit of work in Win11. ;)

Ralf_Mardorf commented on 2022-06-19 15:06 (UTC)

Hi, which LTS kernels are affected? LTS kernels are 4.9, 4.14, 4.19, 5.4, 5.10, 5.15. The link provided by j77h mentions the EOL kernel 5.17. See https://www.kernel.org/ for a list of mainline, stable, stable EOL, longterm and linux-next. FWIW my Arch Linux host is using rt-patched 4.19 kernels. At least those 4.19 LTS kernels don't cause issues with virtualbox-bin 6.1.34-1 as well as 6.1.34-2. I can't comment on Arch Linux's core/linux-lts package 5.15 kernel. Regards, Ralf

j77h commented on 2022-06-19 14:16 (UTC)

Looks like VirtualBox 6.1.35 test build might be useful now. Could save people downgrading kernels. https://forums.virtualbox.org/viewtopic.php?f=7&t=106071&start=15#p519330 The VBox problem also happens with LTS kernels due to kernel backports.

dbermond commented on 2022-06-17 20:10 (UTC)

@firewalker Package updated with linux 5.18 patch.

drankinatty commented on 2022-06-15 08:50 (UTC)

Additionally, the 5.17 package has problems with remote display size set to frame-buffer size even though the actual window on the remote host is full-size. Meaning in my case you only see 1024x768 of the total 1440x864 for the guest shown on the remote host through rdesktop. No replies on the vbox-users-list, so I suspect this may be from the older commit we draw .c files from in the PKGBUILD? I haven't tried the 5.18 patch that originated from Larry Finger at SuSE.