From: "zhangxiang" <zhangxiang@ncic.ac.cn>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support
Date: Mon, 19 Apr 2010 16:58:46 +0800 [thread overview]
Message-ID: <201004191658461840246@ncic.ac.cn> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2794 bytes --]
Hello, everyone!
I am trying to boot linux-2.6.33.2 as DomU' kernel in my virtualization platform
(Xen-3.4.2, linux-2.6.18.8 as Dom0, paravirtualization, AMD Opteron 2216,
CentOS 5.3 without virtualization support). But it is always core-dump when
booting. The messages are as follows:
Loading aic79xx.ko module
Loading sata_nv.ko module
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.33.2 #13
Call Trace:
[<ffffffff81042d00>] panic+0xa0/0x1a0
[<ffffffff810075df>] ? xen_restore_fl_direct_end+0x0/0x1
[<ffffffff81078e40>] ? call_rcu_sched+0x10/0x20
[<ffffffff81078e59>] ? call_rcu+0x9/0x10
[<ffffffff8104521e>] ? put_files_struct+0x7e/0xd0
[<ffffffff81457955>] ? _raw_write_lock_irq+0x15/0x30
[<ffffffff8104d4b7>] ? exit_ptrace+0xb7/0x140
[<ffffffff81046a8f>] do_exit+0x6df/0x7a0
[<ffffffff8102c7af>] ? do_page_fault+0x14f/0x310
[<ffffffff81046b90>] do_group_exit+0x40/0xd0
[<ffffffff81046c32>] sys_exit_group+0x12/0x20
[<ffffffff8100af02>] system_call_fastpath+0x16/0x1b
The DomU's configuration file is as follows:
kernel = "/boot/vmlinuz-2.6.33.2"
ramdisk = "/boot/initrd-2.6.33.2.img"
memory = 512
name = "vmtmp"
vcpus = 2
vif = [ '' ]
ip = "10.10.135.182"
netmask = "255.255.0.0"
disk = [ 'file:/sda3/vmdisk2,xvda,w']
root = "/dev/xvda rw"
extra = "4"
extra='xencons=hvc0'
I do this experiment depend on the link:
http://wiki.xensource.com/xenwiki/XenParavirtOps
I download linux-2.6.33.2 from www.kernel.org, and make sure that all the following
config options are selected when compling:
CONFIG_PARAVIRT_GUEST
CONFIG_XEN
CONFIG_HVC_DRIVER and CONFIG_HVC_XEN
CONFIG_XEN_BLKDEV_FRONTEND
CONFIG_XEN_NETDEV_FRONTEND
I also use /dev/xvdX instead of /dev/sda1 in both DomU's configurion file and /etc/fstab.
So I really do not know why the experiment always fails.
Could somebody help me with this?
Thank you very much for your help!
Xiang Zhang
Apr 19th, 2010
---------------------------------------------------------------------
National Research Center for Intelligent Computing System
Institute of Computing Technology
Chinese Academy of Sciences
P.O. Box 2704, Beijing 100190, P. R. China
Tel: +86-10-6260 1009
---------------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 7240 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-04-19 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:58 zhangxiang [this message]
2010-04-19 13:48 ` Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support Konrad Rzeszutek Wilk
2010-04-19 14:29 ` Booting Failures when using linux-2.6.33.2 as DomUwith " zhangxiang
2010-04-19 15:50 ` Konrad Rzeszutek Wilk
2010-04-20 8:15 ` Booting Failures when using linux-2.6.33.2 asDomUwith " zhangxiang
2010-04-20 18:46 ` Konrad Rzeszutek Wilk
2010-04-21 7:41 ` Booting Failures when using linux-2.6.33.2asDomUwith " zhangxiang
2010-04-21 13:09 ` 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=201004191658461840246@ncic.ac.cn \
--to=zhangxiang@ncic.ac.cn \
--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).