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