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: Josip Rodin <joy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] current xen/stable failed upgrade from
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Thu, 11 Mar 2010 21:24:56 +0200
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 11 Mar 2010 11:25:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100311150823.GA9011@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> <20100311150823.GA9011@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Thu, Mar 11, 2010 at 04:08:23PM +0100, Josip Rodin wrote:
> 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...

If you boot baremetal (non-Xen) Linux, on what IO-port and IRQ is the iLO 
serial port? 

Is it on the standard IO-port/IRQ, or some non-standard? In this case you might 
to specify the IOport on the xen cmdline options in grub.conf.

See also:

-- Pasi

Xen-devel mailing list

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