I am currently using kernel 6.7.0 and virtualbox 7.0.12. As the 7.0.14 update for virtualbox came in, I found that the configure step exits with an error: Checking for 32-bit support: Cannot execute 32-bit applications! Either enable 32-bit support in the kernel configuration or use --disable-vmmraw to disable 32-bit guests. But it is not a 7.0.14 issue, 7.0.12 also gets this error with kernel 6.7.0 (so my virtualbox installation is older than the kernel). Kernel 6.7 changed the 32bit support behaviour, see https://www.phoronix.com/news/Linux-6.7-IA32-Emulation-Boot and https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=a11e097504ac1889b35b6858f495565838325f88 My kernel allows 32bit emulation but disables it by default as I want to ensure there is no 32bit legacy left, here is the snippet from the kernel .config file: CONFIG_IA32_EMULATION=y CONFIG_IA32_EMULATION_DEFAULT_DISABLED=y I modified the ebuild and added --disable-vmmraw to src_configure() and virtualbox was able to build (and run openSUSE 15.5). It may be a good idea to add a USE-flag to utilize the vmraw option and check the kernel settings to warn if the flag is not used: - if emulation is not available, the flag is required and the ebuild can fail "ex-ante" - if emulation is available but deactivated, either the flag is required or the emulation should be activated and a warning is helpful to guide the user to a solution - if the flag is set but emulation is available and enabled, a notice should tell that the build will not use 32bit emulation though the kernel supports it The option --disable-vmraw itself seems to be quite old, I found a google hit from about 11 years ago. It seems there is a use case now :-) Reproducible: Always Steps to Reproduce: 1. Use a 6.7.0 kernel without 32bit emulation enabled or disabled 32bit support 2. emerge virtualbox, e.g. version 7.0.14
