From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support Date: Mon, 19 Apr 2010 09:48:04 -0400 Message-ID: <20100419134804.GB17501@phenom.dumpdata.com> References: <201004191658461840246@ncic.ac.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <201004191658461840246@ncic.ac.cn> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: zhangxiang Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Mon, Apr 19, 2010 at 04:58:46PM +0800, zhangxiang wrote: > 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: You need to attach the whole output to help you along. > > 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: > [] panic+0xa0/0x1a0 > [] ? xen_restore_fl_direct_end+0x0/0x1 > [] ? call_rcu_sched+0x10/0x20 > [] ? call_rcu+0x9/0x10 > [] ? put_files_struct+0x7e/0xd0 > [] ? _raw_write_lock_irq+0x15/0x30 > [] ? exit_ptrace+0xb7/0x140 > [] do_exit+0x6df/0x7a0 > [] ? do_page_fault+0x14f/0x310 > [] do_group_exit+0x40/0xd0 > [] sys_exit_group+0x12/0x20 > [] 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: By selected you mean 'y', correct? > CONFIG_PARAVIRT_GUEST > CONFIG_XEN > CONFIG_HVC_DRIVER and CONFIG_HVC_XEN > CONFIG_XEN_BLKDEV_FRONTEND > CONFIG_XEN_NETDEV_FRONTEND I thought there was also a FBDEV and KBDDEV, but I could be wrong. > > 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 > --------------------------------------------------------------------- > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel