Re: domU memory exceeded =?=> spontaneous reboots

[Mike <debian@xxxxxxxxxxxxxxxxxxxxx>]

On Mar 1, 2025, Paul Leiber wrote:
> I can access
> Xen's serial console via SoL. I successfully tried Intel Manageability
> Commander and Mesh Commander.

I set up an IPMI connection to the Xen box.  I set "loglvl=all" and
"guest_loglvl=all", and am seeing accordingly more messages on the monitor.

I set the BIOS setting for the P1 power level at 87W, the maximum dissipation
that the fanless case is supposed to be able to handle.  I did this just to
prevent overheating, though I still don't believe that's an issue.

I also set "noreboot=true", yet when the system failed spontaneously again,
it rebooted as well.  I know this setting works, because when I manually
rebooted with "shutdown -r", the reboot didn't happen; I had to force it
manually.  This is concerning to me, since it suggests that the failure is
happening at a lower level than what Xen controls.

I'm still not seeing the boot output on the SOL console.  I'm using the one
that's built into the Supermicro IPMI web console, which is based on Java
WebStart--a rather old and oddball technology.  I should try using `ipmitool`
or such.

But I think the real issue with SOL is in the BIOS settings.  It's a
Supermicro board, and the settings appear to be in the "Advanced" menu bar.
Under "Serial Port Console Redirection", "SOL Console Redirection" is already
"Enabled"; under "AST2600SEC Super IO Configuration" > "SOL Configuration",
"SOL" is already "Enabled" with "Device Settings" of "IO=2F8h;  IRQ=3;".  So
I'm adding "com2=115200,8n1,0x2f8,3 console=com2,vga" to Xen.  Yet I'm still
seeing the output on the VGA monitor.  It's not clear to me whether I need to
redirect one of the COM ports as well.  "dmesg | grep ttyS" gets me that
ttyS1 (= COM2?) is at 0x2f8, IRQ 3.