Fedora Account System
Red Hat Associate
Red Hat Customer
We updated our s390x lpar a while back and when we booted into 7.0.10 it killed pretty much all kvm guests right after starting them. ;( Booting back to 6.19.8-200.fc43.s390x and everything is back to normal. I'll attach the journal from that boot. Any ideas what could be causing this? Reproducible: Always
Created attachment 2146415 [details] 7.0.11-oom-killing journal Here's the journal from that boot.
7.2.0-61.fc45 and 7.1.8-200.fc44 do the same thing. Downgraded to 6.19.14-108.fc42
Still happens with 7.3.0-0.rc5.45.fc46
Created attachment 2159563 [details] 7.3.0-0.rc5.45.fc46.s390x-killing dmesg from a 7.3.0-rc5 boot
So, some progress/info. We got more memory allocated to our lpar and I booted again into 7.2.x. This time things all came up and no oom's. It seems that guests are getting allocated their entire max memory on start, then inside the vm the memory slowly seems to drop to the set current memory This is unlike in 6.18, where vm's memory was only allocated to the current memory size on startup. qemu 13553 151 1.4 101320752 32069280 ? Sl 17:26 77:29 /usr/bin/qemu-system-s390x -name guest=buildvm-s390x-01.s390.fedoraproject.org... maxmem is set to 96G there and 48G current So, this just seems a change in behavior and it's not clear exactly what...