On Tuesday 2017-11-14 12:04, Brüns, Stefan wrote:
_constraints set to 6G, VM is started with -m 8192, available memory (Mem
- Swap) in the build environment: 3G + 2G
-> _constraints is *not* honored
Huh? It is, the VM is providing 8GB what is more than 6GB.
It is not up to the constraints system what the content (here the kernel) is doing with that...
From the user perspective this is clearly unexpected behaviour - the user has requested a worker with 8 GB of memory, but only gets 4...5 GByte (RAM + Swap, as documented).
A worker which is started with more than 3 GByte (-m >= 3000) should be using a PAE/HIGHMEM64G kernel.
I can confirm; kvm is started with 64-bit "hardware", but uses the non-PAE 32-bit kernel (kernel-default). It either has to use kernel-pae, or has to use the 64-bit kernel-default. init=/.build/build will switch to the ILP32 personality anyway. I have a feeling though, that such won't be enough to get those unspeakably fat browsers to link - it may become necessary to use a 64-bit toolchain with -m32 to complete it, and then the baselibs mechanism to export the build results. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org