All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Williams, Mitch A" <mitch.a.williams@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Latest pvops hangs on boot
Date: Wed, 11 Nov 2009 16:32:45 -0500	[thread overview]
Message-ID: <20091111213245.GC26139@phenom.dumpdata.com> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FA65FF9FE@rrsmsx501.amr.corp.intel.com>

On Wed, Nov 11, 2009 at 02:16:25PM -0700, Williams, Mitch A wrote:
> Looking for a little advice here.  I've compiled the latest xen-unstable tree along with the latest pvops kernel from Jeremy's git tree.
> 
> Xen boots and loads the Linux kernel but then the system spews a bunch of errors and hangs.  I've set up my serial cable to capture the log, which is appended to this email.

There does not seem to be any Dom0 output. It might be that the hang is not in
the Xen but in Dom0. Try these boot arguments:

title Fedora (2.6.31.5)
        root (hd0,0)
        kernel  /xen-3.5-unstable.gz console=com1,vga guest_loglvl=all loglvl=all console_sync console_to_ring
        module /vmlinuz-2.6.31.5 ro root=UUID=d6d08653-4a4f-4d41-87f2-f42fb7fe3ad5 initrd_ignore_loglevel sysrq_always_enable earlyprintk=xen console=tty console=hvc0 loglevel=10 debug
        module /initrd-2.6.31.5.img

Obviously, replace the names of the vmlinuz, initrd, etc as they might
be different on your machine.

  reply	other threads:[~2009-11-11 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 21:16 Latest pvops hangs on boot Williams, Mitch A
2009-11-11 21:32 ` Konrad Rzeszutek Wilk [this message]
2009-11-11 21:54 ` Jeremy Fitzhardinge
2009-11-11 22:03   ` Williams, Mitch A
2009-11-11 22:34     ` Williams, Mitch A
2009-11-11 22:19 ` Austin Schuh
2009-11-11 22:42   ` Williams, Mitch A
2009-11-11 22:46     ` Austin Schuh
2009-11-12  7:49       ` 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=20091111213245.GC26139@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=mitch.a.williams@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.