[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: domU memory exceeded =?=> spontaneous reboots


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Paul Leiber <paul@xxxxxxxxxxxxxxxx>
  • Date: Mon, 17 Mar 2025 19:24:21 +0100
  • Arc-authentication-results: i=1; strato.com; arc=none; dkim=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1742235863; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=GLD4Xvn/DfsENKkwMtNmnUNHJ5Y/Ut9h+qpAy8K0tVE=; b=bxM1rLlmgu1L1jJPBuRym7jM/AiUNhQOUGhPl0hbQRb3bSIDSCPvByBFYaO979cOQ3 jRNK/D6Jj41lEaziti6+8+czHi094BKnMOYOg5zvPXrJsaiemsukHDQLZfQirYY3S/ah Z+K1Va0HJprTJG+EqihnDy9h2nY/OXRXWcERdXR6h/JSlSx1pKgv7ttdIb0pJAqEqNxn GUg8VKwOnnYUYpWjTWLSH4btWxrDtLO46fBXKhga49rxERUPcLW0Zbt/d/fnm6nLKydJ +LzcJqySh2onCfB8fp94045MR9WuTD/TvZUAGEhOCabKjKOQWanrNdPnzwPaEmehXbM0 4vWg==
  • Arc-seal: i=1; a=rsa-sha256; t=1742235863; cv=none; d=strato.com; s=strato-dkim-0002; b=N7kJ4WA/lL5YRUvz1+Gjs8xbEsRJqBdfxOnQ7fRw9TwZZmiIoe5nBixnJi0phaNQ6A sZ6sAo2L3sjjYeLmbiwl0OirP7VKA5rVeW7cBVgNfZ6R56JjH86s7KXbMxEyNqqjmVIY f5IRIKVnMLCf3odtp8txxFvxV25jeQKzRqjSWTUB87dRsRrtef+Mlil8rYrFtGr7wdBo 0YOOIbUdPVkgLx3d4xMxtNqpCd78gl5D1PHrm6qHqX0SksjakEP+iPDXOgzVmOdckjLi QtMpc2gDBu9BeYiDIGAI0sBUs/VybSzAeaZfhD4dKO+kdUjsVDlN/FCLu09lJeakuJIh H1xA==
  • Delivery-date: Mon, 17 Mar 2025 18:24:54 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>

Am 17.03.2025 um 18:47 schrieb Mike:
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.


Looks similar to what I am doing:

loglvl=all guest_loglvl=all com1=115200,8n1,0xe2a0,17 console=vga,com1

Did you check the wiki on serial console [1]? It has a paragraph on SoL ("Configuring serial console for non-standard PCI serial ports (for example Intel AMT)").

Best regards,

Paul

[1] https://wiki.xenproject.org/wiki/Xen_Serial_Console



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.