[vbox-dev] why should virtualbox 5.1.4 enable uses 32-bit capabilities (legacy support in use) as default?

Frank Mehnert frank.mehnert at oracle.com
Tue Aug 30 08:32:15 UTC 2016

On Tuesday, 30 August 2016 16:23:17 CEST getonga wrote:
> I use virtualbox as the vagrant provider, it works very well.
> Recently I update the virtualbox to version 5.1.4, the message appears:
> $ dmesg | grep -i warn
> [   92.028562] capability: warning: `VirtualBox' uses 32-bit capabilities
> (legacy support in use)
> I have three linux machines, all has these msg. All of them have the secure
> virtual mode enable. Why should virtualbox use 32-bit as default, not the
> 64-bit? Some old versions not use this as default, but I am not sure which
> version starts to use this as default.
> It also works, but I'd like to know why this enables as default?

I don't think that using the legacy 32-bit capabilities causes any issue.
It's just a message in the host kernel log file and it's there for ages.
Capability support is required to create a raw net socket for ICMP with
NAT, see SUPR3HardenedMain.cpp.

Kind regards,

Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox
ORACLE Deutschland B.V. & Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstraße 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

More information about the vbox-dev mailing list