From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Marcial Rion <marcial.rion@swissonline.ch>
Cc: xen-devel@lists.xensource.com
Subject: Re: Issue with pv_ops Kernel 2.6.31.6 and Xen
Date: Mon, 8 Feb 2010 13:22:06 -0500 [thread overview]
Message-ID: <20100208182206.GA6035@phenom.dumpdata.com> (raw)
In-Reply-To: <4B6EDE9A.4010205@swissonline.ch>
On Sun, Feb 07, 2010 at 04:39:06PM +0100, Marcial Rion wrote:
> BTW: The problem also persists when using XEN 4.0.0-rc3-pre. See the
> dump of the bootup trace below:
>
> Booting 'Xen 4.0, Kernel 2.6.31'
>
> root (hd0,0)
> Filesystem type is ext2fs, partition type 0x83
> kernel /boot/xen-4.0.gz dom0_mem=256M loglvl=all guest_loglvl=all
> sync_co
> nnsole console_to_ring com2=38400,8n1 console=com2
> [Multiboot-elf, <0x100000:0x12d000:0xad000>, shtab=0x2da078,
> entry=0x100000]
> module /boot/kernel-2.6.31.6-xen root=/dev/hda3 ro console=hvc0
> earlyprin
> tk=xen
Well, all your arguments look right, so I can think of two things:
1). You don't have /dev/console, /dev/hvc0 and /dev/tty0 created
by init scripts during boot. Usually this is a udev job, but
I don't know how Gentoo does it.
2). Gentoo has it hard-coded to use a different console. Are there
any documention online about configuring Xen with Gentoo and what
needs to be done?
Is your machine pingable after you have booted it? If you give it
enought time (say 3 minutes) do you see anyting on the screen?
next prev parent reply other threads:[~2010-02-08 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 22:38 Issue with pv_ops Kernel 2.6.31.6 and Xen Marcial Rion
2010-01-28 5:59 ` Marcial Rion
2010-01-28 19:46 ` Konrad Rzeszutek Wilk
2010-01-29 23:55 ` Marcial Rion
2010-01-30 21:11 ` Marcial Rion
2010-02-07 15:39 ` Marcial Rion
2010-02-08 18:22 ` Konrad Rzeszutek Wilk [this message]
2010-02-08 21:48 ` Marcial Rion
2010-02-08 23:40 ` Konrad Rzeszutek Wilk
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=20100208182206.GA6035@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=marcial.rion@swissonline.ch \
--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).