Package Base Details: virtualbox-bin

Git Clone URL: (read-only, click to copy)
Keywords: machine oracle virtualization vm
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 58
Popularity: 1.30
First Submitted: 2015-08-18 09:16
Last Updated: 2021-04-30 10:55

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

dbermond commented on 2020-08-14 13:06

@nursoda At the time of this writing, VirtualBox 6.1.13 is not yet released by upstream. Not even the repository package is updated to 6.1.13.

nursoda commented on 2020-08-14 13:01

For the time being, could you please update to 6.1.13 – virtualbox-ext-oracle is updated already and breaks virtualbox-bin due to 12 vs 13 version mismatch. I know that I can downgrade that but … I try to stay up-to-date on all packages ;) Anyway: Does 6.1.13 solve the Kernel 5.8 issue?

dbermond commented on 2020-08-12 20:25

Upgrading linux to 5.8 will break virtualbox-bin 6.1.12.

I've prepared a patch for linux 5.8 (based on the repository package) but apparently it modifies the modules version, since it causes a 'module version mismatch' error when running a virtual machine.

So a patch for the dkms sources will not be sufficient. We need an update from upstream supporting linux 5.8. Based on the release history, it should not take too much long.

Ralf_Mardorf commented on 2020-07-17 03:59

Update: VirtualBox Ticket #19719

Ralf_Mardorf commented on 2020-07-17 03:08

Hi, after installing 6.1.12-1 + extension pack a Windows 10 guest can be used with the new guest additions, but a Windows 7 guest doesn't boot anymore, after installing the guest additions. Starting Windows 7 in safe mode works, but doesn't find a solution. I restored Windows 7 from a snapshot and tried again. The Windows 7 guest failed to boot again after installing the guest additions. Does anybody experience the same issue?

dbermond commented on 2020-04-21 23:26

@joerg-krause AUR helpers are not supported. Please use makepkg.

No malicious code on this PKGBUILD, it's just extracting the main source file.

joerg-krause commented on 2020-04-16 06:30

The Aura package manager fails to build this package to avoid potentially malicious code:

sudo aura -Ax virtualbox-bin
aura >>= Determining dependencies...
aura >>= WARNING: The PKGBUILD of `virtualbox-bin` contains blacklisted bash expressions.

    sh "VirtualBox-${pkgver}-${_build}" --target "${pkgname}-${pkgver}" --nox11 --noexec

aura >>= `sh` can be used to execute arbitrary code not tracked by this PKGBUILD.
aura >>= Do you wish to quit the build process? [Y/n] 
aura >>= Cancelled further processing to avoid potentially malicious bash code.

Ralf_Mardorf commented on 2020-04-06 11:12

Romario74, see the "Update" added to my original comment. I noticed that the extension pack needed to be reinstalled already before you replied. However, there's still an issue displayed for one guest's settings, even while the guest seems to be usable. After doing some further testing virtualbox-bin 6.1.4-2 seems not to work when booted to the real-time patched kernel 5.6.2, it seems to work when booted to the real-time patched kernel 4.19.106. "Seems", since I only made short tests and those failed when booted to the kernel 5.6.2, but worked when booted to the kernel 4.19.106. Now I'll try to backup two tablets with the Windows 7 and with the Windows 10 guest, while booted into 5.6.2-arch1-2 with "threadirqs". Until now the Windows 7 guest works. If I don't report anything else within the next hours, it continued to work without failure and the Windows 10 guest worked, too.

Romario74 commented on 2020-04-05 20:37

You have to reinstall the extension pack. This is what gives you USB support for your VMs. No need to restore from backup. And thanks for the virtualbox update, works fine with kernel 5.6.

Ralf_Mardorf commented on 2020-04-05 18:18

A self-build real-time patched kernel 5.6.2-rt1 as well as 5.6.2-arch1-2 from Testing, with virtualbox-bin 6.1.4-2, trying to start a Windows 10 or Windows 7 guest fails with "Implementation of the USB 2.0 controller not found!" The same happens for a self-build real-time patched 4.19.106-rt46. After downgrading to virtualbox-bin 6.1.4-1, the self-build real-time patched kernel 4.19.106-rt46, that could be used before the upgrade to virtualbox-bin 6.1.4-2, still results in the same error. Even while I'm loading and unloading the modules on demand, I restarted the machine to no avail. FWIW all modules were build. The vbox and vbox-prev files do only contain different timestamps, anything else doesn't differ. The snapshots were not touched at all. Since it worked a few hours before I upgraded virtualbox-bin, nothing else was upgraded, I'll restore the guests from backups or what ever else might be broken.

Update: There was no need to restore from a backup, I just needed to reinstall the extension pack, so perhaps it even works with kernel 5.6. I can't test it now. Both Windows guests can be used again, but an invalid setting for the Windows 7 guest is detected, it's just not mentioned what setting.