Package Details: virtualbox-bin 7.1.8-1

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: 63
Popularity: 0.37
First Submitted: 2015-08-18 09:16 (UTC)
Last Updated: 2025-04-16 21:49 (UTC)

Required by (15)

Sources (13)

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.

Latest Comments

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

Ralf_Mardorf commented on 2023-08-11 08:22 (UTC)

Hi ng0177, Oracle's concept is inherently inconsistent because if their products were as user-friendly as they claim, then there would be no need to offer Premier Support to paying users. Indeed, for Windows guests I use Virtualbox for ease of use, while for Linux I use QEMU/KVM. But since Virtualbox 6.1 will expire at the end of this year, I will probably have to give up Virtualbox. I can't use a Windows 11 guest with Virtualbox 7, regardless of which branch I use, so I'm maintaining my own packages at the moment.

$ pacman -Q virtual box
virtual box 1:6.1.46-7010.1

Regards, Ralf

ng0177 commented on 2023-08-11 06:47 (UTC) (edited on 2023-08-11 06:48 (UTC) by ng0177)

A Oracle Linux guest installation seems not to respect the Workstation selection which is ignored but the Server version is always installed instead unlike during a native install. Anyone to reproduce?

dbermond commented on 2023-06-20 20:09 (UTC)

@seboss666 Sorry, but Manjaro is not supported. Please seek help in your distribution support channels. AUR helpers (like yay) are also not supported on Arch Linux.

seboss666 commented on 2023-05-07 21:41 (UTC)

Hello,

I'm currently using the 7.0.6-3 from community, with the ext-pack from AUR (and the host modules for my 5.15 kernel - I'm on Manjaro).

But now yay wants to replace it with this package alongside the ext-pack. As I see from the Arch repository that the package still exist (cf https://archlinux.org/packages/community/x86_64/virtualbox/), is there a way to prevent this one to be "selected" ?

Ralf_Mardorf commented on 2023-01-22 12:15 (UTC)

PS:

MemoryShadow commented on 2023-01-22 08:02 (UTC) (edited on 2023-01-22 08:10 (UTC) by MemoryShadow):

"Which package should I install?"

Maybe you are asking the wrong question. The culprit is probably not a missing package, but your AUR helper yay and/or that you don't build within a clean chroot.

Ralf_Mardorf commented on 2023-01-22 10:28 (UTC) (edited on 2023-01-22 10:29 (UTC) by Ralf_Mardorf)

Hi, I don't build virtualbox-bin anymore, but I maintain my own virtualbox 6.1.40 package, based on the community PKGBUILD, since the community/virtualbox 7.0+ as well as the aur/virtualbox-bin 7.0+ packages can't run a Windows 11 guest on my machine.

If I try to build without a clean chroot it fails to build, too.

[rocketmouse@archlinux ~]$ grep virtualbox\  /var/log/pacman.log | grep 6.1.40 | tail -6
[2022-11-01T17:48:40+0100] [ALPM] upgraded virtualbox (6.1.40-1 -> 7.0.2-1)
[2022-11-13T22:16:10+0100] [ALPM] upgraded virtualbox (7.0.2-2 -> 1:6.1.40-702.2)
[2022-11-18T23:07:23+0100] [ALPM] upgraded virtualbox (1:6.1.40-702.2 -> 1:6.1.40-704.1)
[2023-01-04T15:50:37+0100] [ALPM] downgraded virtualbox (1:6.1.40-704.1 -> 7.0.4-3)
[2023-01-08T00:44:43+0100] [ALPM] installed virtualbox (1:6.1.40-704.3)
[2023-01-18T04:40:20+0100] [ALPM] upgraded virtualbox (1:6.1.40-704.3 -> 1:6.1.40-706.1)

IIRC I could build 1:6.1.40-702.2 and 1:6.1.40-704.1 in November 2022 without a clean chroot. At least when I tried to build 1:6.1.40-704.3 in January 2023 without a clean chroot it failed to build. 1:6.1.40-704.3 and 1:6.1.40-706.1 were build in a clean chroot without a problem. IOW try building within a clean chroot by following the DeveloperWiki's classic way guide. Regards, Ralf

MemoryShadow commented on 2023-01-22 08:02 (UTC) (edited on 2023-01-22 08:10 (UTC) by MemoryShadow)

seek solutions:
Which package should I install? What module is 'SetuptoolsDeprecationWarning' in?
Error code: 

Traceback (most recent call last):
...
from setuptools import SetuptoolsDeprecationWarning
ImportError: cannot import name 'SetuptoolsDeprecationWarning' from 'setuptools' (/home/memoryshadow/.local/lib/python3.10/site-packages/setuptools/__init__.py)

drankinatty commented on 2022-11-02 05:46 (UTC)

Anyone interested in maintaining virtualbox6-bin? The 6.1 branch will remain supported until December 2023. See https://www.virtualbox.org/wiki/Downloads

dion_starfire commented on 2022-11-01 17:47 (UTC)

As of 7.x, VirtualBox requires Vulkan. I'm still in the process of troubleshooting my particular situation (after installing Vulkan deps, I no longer get a black screen and instead make it to where the guest tools attempts to resize the guest screen, at which point the entire VirtualBoxVM process dumps core), but the relevant part for this page is that we need to add vulkan libraries as (optional?) dependencies to the package.

dion_starfire commented on 2022-10-31 18:51 (UTC)

3D acceleration appears to be broken in 7.0.2-1 (with virtualbox-ext-oracle-7.0.2-1). Booting an Ubuntu 22.04 guest with 3D acceleration disabled works fine, but with it enabled, guest hangs at a black screen during boot. Downgrading everything to 6.1.38-1 works perfectly. Looking at the logs, VirtualBox appears to be failing to find a Direct3D lib, of all things:

00:00:01.632355 Changing the VM state from 'CREATED' to 'POWERING_ON'
00:00:01.637862 rtldrNativeLoad: dlopen('D3DCompiler_47.so', RTLD_NOW | RTLD_LOCAL) failed: D3DCompiler_47.so: cannot open shared object file: No such file or directory
00:00:01.637875 VMSVGA: Single DX device mode: enabled
00:00:01.658047 DxvkInstance::enumAdapters: Failed to enumerate adaptersD3D11CreateDevice: Failed to create a DXGI factoryVMSVGA3d: 3D support disabled! (vmsvga3dPowerOn -> VERR_NOT_SUPPORTED)

Google is failing me on figuring out what dependency could provide this library.

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