From: Jeremy Fitzhardinge <jeremy@goop.org>
To: jonr@destar.net
Cc: xen-devel@lists.xensource.com
Subject: Re: Console output with pv_ops kernel
Date: Mon, 16 Feb 2009 14:53:45 -0800 [thread overview]
Message-ID: <4999EE79.3090508@goop.org> (raw)
In-Reply-To: <20090216125429.aj6amf9ts0ccskgg@www.destar.net>
jonr@destar.net wrote:
> I am trying to get my Xen-3.4-unstable with 2.6.29-rc3-tip to output
> to the console after Xen releases control back to the kernel. I can
> see the Xen portion but as soon as it scrubs memory it goes to a blank
> screen. It will boot up but I will never see a login prompt. I have to
> ssh into the box.
>
> I have tried various options for grub but have not found the correct
> combination as of yet. Here is what I have for my menu.lst:
>
> This is the latest incantation:
>
> title Xen 3.4 / kernel 2.6.29-tip-rc3
> root(hd0,0)
> kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
> module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0
> earlyprintk=xen pci=nomsi
> module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
>
> ====
> Also:
> ====
> title Xen 3.4 / kernel 2.6.29-tip-rc3
> root(hd0,0)
> kernel /boot/xen-3.4-unstable.gz dom0_mem=512M
> module /boot/vmlinuz-2.6.29-rc3-tip-new ro console=hvc0
> earlyprintk=xen pci=nomsi
> module /boot/initramfs-2.6.29-rc3-tip-new.cpio.gz
>
>
> Has anybody gotten this to output to the screen? Is there some magic
> that I am missing?
>
This should work if you're using a serial console. Otherwise, you can
use a vga console; I use:
title xen-unstable pvops
kernel /xen-3.gz loglvl=all guest_loglvl=all
module /vmlinuz-2.6.29-rc5-tip ro root=/dev/VolGroup00/LogVol00 ignore_loglevel pci=nomsi earlyprintk=vga console=tty0
module /initrd-2.6.29-rc5-tip.img
J
next prev parent reply other threads:[~2009-02-16 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 21:54 Console output with pv_ops kernel jonr
2009-02-16 22:53 ` Jeremy Fitzhardinge [this message]
2009-02-17 5:14 ` How to build vmlinuz-2.6.29-rc5-tip ? Boris Derzhavets
2009-02-17 8:15 ` Boris Derzhavets
2009-02-17 8:28 ` Ian Campbell
2009-02-17 9:40 ` Boris Derzhavets
2009-02-17 10:00 ` M A Young
2009-02-17 11:59 ` Boris Derzhavets
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=4999EE79.3090508@goop.org \
--to=jeremy@goop.org \
--cc=jonr@destar.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 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.