| Git Clone URL: | https://aur.archlinux.org/virtualbox-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | virtualbox-bin |
| Description: | Powerful x86 virtualization for enterprise as well as home use (Oracle branded non-OSE) |
| Upstream URL: | https://www.virtualbox.org/ |
| Keywords: | machine oracle virtualization vm |
| Licenses: | GPL-3.0-only |
| Conflicts: | virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch |
| Provides: | virtualbox, virtualbox-host-dkms, VIRTUALBOX-HOST-MODULES |
| Replaces: | virtualbox-sun, virtualbox_bin |
| Submitter: | Rainmaker |
| Maintainer: | dbermond |
| Last Packager: | dbermond |
| Votes: | 62 |
| Popularity: | 0.000041 |
| First Submitted: | 2015-08-18 09:16 (UTC) |
| Last Updated: | 2025-01-25 11:39 (UTC) |
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.
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. ;)
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
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.
@firewalker Package updated with linux 5.18 patch.
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.
With linux 5.18 dkms fails to build. There is a patch. 020-linux518.patch but it doesn;t seem to apply for the bin version.
https://www.mail-archive.com/arch-commits@lists.archlinux.org/msg321191.html
Hi, I needed to downgrade dkms from 3.0.2-1 to 3.0.1-1, see the aur-general Archives. Regards, Ralf
With Linux 5.15, for Linux Guests, vboxadd-setup.log will show:
error: no such file or directory # include <drm/drm_irq.h>
Since most of the features are native in the kernel, this build failure installing guest additions seems to only effect the initial modesetting for the terminal. X, Shared-Folders, and the rest continues to work fine on the guest. Notified Oracle via the Virtualbox list and we will see what they say. Current Oracle TestBuilds (revs: 148164 and 148140-ext pack) do not address the issue.
So at least for virtualbox-bin, the 5.15 update doesn't cause any significant issues (thankfully!)
Pinned Comments
dbermond commented on 2022-10-21 19:08 (UTC)
Notice:
To avoid crashes when upgrading Guest Additions from version 6.x to 7.x on Windows guests, uninstall the old Guest Additions first, then reboot, and then install the new ones. It's recommended to do all these operations in Safe Mode. See this upstream bug ticket for more details.