Arch Linux User Repository

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.

Thanks, @dbermont – worked like a charm in Safe mode (F5 during startup), using virtualbox-guest-iso made available through Tools-Media-Optical.

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.

Hi, building the package{,s} fails. Regards, Ralf

$ makechrootpkg -c -r $CHROOT 
[snip]
curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 104
==> ERROR: Failure while downloading https://www.virtualbox.org/svn/vbox/trunk/include/VBox/VBoxAuth.h?p=96547
    Aborting...
==> ERROR: Could not download sources.

Actually VirtualBox 7.0.0 is out since October 10, 2022... https://www.virtualbox.org/

If you want to try 6.1.40, all you need to do is update the PKGBUILD with pkgver=6.1.40 and _build=154048. Rest is the same. Then update checksums and it will build fine.

Also, we may need to rename this package virtualbox-bin-6 for the remainder of the support period (likely 9 mo. or so). Oracle on the virtualbox users-list recommends remaining with the 6.1 branch for production installs until the bugs with the new 7.0 branch have been identified and fixed.

@drankinatty Package updated.

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

@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.)

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
[...]

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.