From: Mike Wright <mike.wright@mailinator.com>
To: xen-devel@lists.xensource.com
Subject: can't boot into dom0
Date: Fri, 17 Jun 2011 14:13:26 -0700 [thread overview]
Message-ID: <4DFBC376.6050101@mailinator.com> (raw)
Hi all,
New to this list.
I built xen-4.1.1 successfully and can see that it boots from grub with
the kernel /xen.gz line.
I'm using the following kernel (3.0.0-rc2):
http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git and its default
.config file,
which also builds successfully and boots standalone.
When I try to boot it as a dom0 I get a segfault.
There is nothing in any of the logs (probably segfaults very early) and
I can't even see the tail end of the segfault because the screen blanks
afterward, even though I specify noreboot on the module "kernel" line.
Here's my boot stanza:
title FedoraXen (4.1.1-3.0.0-rc2)
root (hd0,0)
kernel /xen.gz
module ### all on one line
/vmlinuz-3.0.0-rc3
ro
root=/dev/mapper/vg_lan51-lv_root
rd_LVM_LV=vg_lan51/lv_root
rd_LVM_LV=vg_lan51/lv_swap
rd_NO_LUKS
rd_NO_MD
rd_NO_DM
LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16
KEYBOARDTYPE=pc
KEYTABLE=us
console=tty0
xencons=hvc
console=hvc0
dom0_mem=752M
noreboot
module /initramfs-3.0.0-rc2.img
If anybody can point me in some direction where I can capture additional
info or give me any pointers I'd be most appreciative.
Thanks,
Mike Wright
next reply other threads:[~2011-06-17 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 21:13 Mike Wright [this message]
2011-06-18 5:11 ` can't boot into dom0 Todd Deshane
2011-06-18 20:00 ` can't boot into dom0 - followup Mike Wright
2011-06-20 13:15 ` Konrad Rzeszutek Wilk
2011-06-20 13:31 ` Konrad Rzeszutek Wilk
2011-06-21 2:29 ` Tian, Kevin
2011-06-21 13:19 ` Konrad Rzeszutek Wilk
2011-06-20 19:34 ` Mike Wright
2011-06-20 19:41 ` Mike Wright
2011-06-21 1:46 ` Todd Deshane
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=4DFBC376.6050101@mailinator.com \
--to=mike.wright@mailinator.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.