This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] current xen/stable failed upgrade from

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] current xen/stable failed upgrade from
From: Josip Rodin <joy@xxxxxxxxxxxxxx>
Date: Thu, 11 Mar 2010 16:08:23 +0100
Delivery-date: Thu, 11 Mar 2010 07:12:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100307233147.GA20068@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100306115833.GA28039@xxxxxxxxxxxxxxx> <20100306132711.GK2580@xxxxxxxxxxx> <20100307233147.GA20068@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Mar 08, 2010 at 12:31:47AM +0100, Josip Rodin wrote:
> > > I tried adding loglvl=all guest_loglvl=all sync_console console_to_ring
> > > to the hypervisor options, and console=hvc0 earlyprintk=xen initcall_debug
> > > to the kernel options, to no avail. The hypervisor showed the sync console
> > > warning, but the dom0 kernel didn't change its behaviour.
> > 
> > You should set up a serial console so you can capture the boot/error logs,
> > and we can analyze them to troubleshoot the problem, see:
> > 
> > http://wiki.xensource.com/xenwiki/XenSerialConsole
> The machine has iLO VSP, so I'll try that next time I have a debugging
> time slot, thanks.

Sadly, it looks this iLO VSP is completely useless, because when I defined
com1, the hypervisor started *not* displaying anything on the physical
console or the virtual serial port. I tried this once and it made the
machine seem broken for a while, when all of the sudden fifteen minutes
later it happily showed the getty on ttyS1 on VSP.

I wonder if perhaps this was caused by some hypervisor console lock timeout
expiring, so I tried to change the setup a bit by removing that getty from
inittab. Then I rebooted it again, and the machine again became catatonic
for a while, but it didn't come back like the last time - it doesn't ping,
nothing is shown on physical console, and nothing is shown on VSP. :(

Maybe I'm missing something regarding the iLO VSP setup on this HP DL380...

     2. That which causes joy or happiness.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>