Comment # 14 on bug 1209497 from Stefan Hundhammer

So now we also have the log from the serial console. We can see that the
installation finished successfully, and that's the end of it. We don't see it
come up using the serial console after the reboot.

That is a bit of information (quite literally a bit), but nothing more. Now we
know that the system is not just trying to communicate with us on the serial
console.

Other than that, we are not much better off than before. It doesn't come up.
Why, we don't know. And we (the YaST team) have no way to find out from the
existing information.

I was hoping that somebody who knows a bit more about s/390 machines can use
some s/390 tools to figure out what is happening. On the PC architecture, we
could watch the hardware / BIOS self test and see what the BIOS is trying to
do; if it tries to start an OS, and from what disk / what partition. There
would be messages.

Does it get to the Grub2 stage? Does it get to starting to load an OS from
Grub2? What's happening? We don't know. Unless somebody with more s/390
know-how can continue investigating here, I don't see how to continue here.