xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Josip Rodin <joy@entuzijast.net>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6
Date: Thu, 11 Mar 2010 21:24:56 +0200	[thread overview]
Message-ID: <20100311192456.GY1878@reaktio.net> (raw)
In-Reply-To: <20100311150823.GA9011@orion.carnet.hr>

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 have
to specify the IOport on the xen cmdline options in grub.conf.

See also:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00263709/c00263709.pdf

-- Pasi

  reply	other threads:[~2010-03-11 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100306115833.GA28039@orion.carnet.hr>
     [not found] ` <20100306132711.GK2580@reaktio.net>
2010-03-07 23:31   ` current xen/stable 2.6.32.9 failed upgrade from 2.6.31.6 Josip Rodin
2010-03-08 23:16     ` Jeremy Fitzhardinge
2010-03-09  9:01       ` Josip Rodin
2010-03-11 23:25         ` Yasir Assam
2010-03-11 23:40           ` Boris Derzhavets
2010-03-12  2:22             ` Yasir Assam
2010-03-12  7:14               ` Pasi Kärkkäinen
2010-03-12 11:28               ` Boris Derzhavets
2010-03-12 21:41                 ` Yasir Assam
2010-03-11 15:08     ` Josip Rodin
2010-03-11 19:24       ` Pasi Kärkkäinen [this message]
2010-03-12 11:41         ` Josip Rodin
2010-03-12 12:09           ` Josip Rodin
2010-03-23 23:18             ` Josip Rodin
2010-03-23 23:22               ` Josip Rodin
2010-03-24  5:10                 ` Jeremy Fitzhardinge
2010-03-24  8:37                   ` Josip Rodin
2010-03-12 13:02           ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100311192456.GY1878@reaktio.net \
    --to=pasik@iki.fi \
    --cc=joy@entuzijast.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).