From mboxrd@z Thu Jan 1 00:00:00 1970 From: David F Barrera Subject: Re: Kernel panic - not syncing: Attempted to kill init! Date: Tue, 21 Dec 2004 12:53:15 -0600 Message-ID: <41C8711B.9000001@us.ibm.com> References: <41C844BA.7020801@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <41C844BA.7020801@us.ibm.com> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org Ian, As I indicated earlier, I created an image file, and I am able to boot xenU now: Red Hat Enterprise Linux Desktop release 3.90 (Nahant) Kernel 2.6.9-xenU on an i686 (none) login: I still can't log in, but I will continue to add files to the image to make it work. In the image, I copied the contents of (hdc3) /dev to the image/dev. I still don't understand why I can get xenU to boot using the system partition (hdc1). I'll keep digging. David F Barrera > > > Ian Pratt wrote: > >>>>> I had tried that (and hda1) before, but sda1 I get an error, too: >>>>> [root@dyn95394184 xen]# xm create -c test1 vmid=1 >>>>> Using config file "test1". >>>>> Error: Error creating domain: vbd: Device not found: sda1 >>>>> >>>> >>>> try disk = [ 'phy:hdc1,0801,w' ] >>>> >>>> 0801 == sda1 >>>> >>> >>> No difference. Same Kernel panic >>> >> >> >> Something odd is going on here -- I believe other people have had >> RHEL3 working. >> >> > I believe it. But RHEL 4 has some differences from RHEL 3, among them > the fact that in RHEL 4 the devices in /dev are created dynamically. > Thus, if I mount hdc1 and look at /dev, it is empty. However, /dev in > hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive > that I export (equivalent to hdc1, in this case) has many devicen on > /dev, meaning they are static; RHEL 3 is similar. > >> Can you mount hdc1 in dom 0 OK? > > Yes: > > [root@dyn95394184 ~]# mount /dev/hdc1 /data1 > [root@dyn95394184 ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hdc3 6372520 2732376 3316436 46% / > none 251384 0 251384 0% /dev/shm > /dev/hdc1 7055144 2422572 4274180 37% /data1 > [root@dyn95394184 ~]# > >> Is there an sbin/init > > [root@dyn95394184 ~]# ls /data1/sbin/init > /data1/sbin/init > [root@dyn95394184 ~]# > >> ? Is there >> a dev directory? >> > Yes, but it is empty: > [root@dyn95394184 dev]# pwd > /data1/dev > [root@dyn95394184 dev]# ls > [root@dyn95394184 dev]# > >> It might be worth enabling the debugging printks in >> drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h >> and rebuilding xen0 / xenU. >> >> >> > I created an image file to experiment, and it seems to go a little > further. The problem has got to be related to the /dev issue. > > disk = [ 'file:/boot/initrd.x86.image,0801,w' ] > # Set if you want dhcp to allocate the IP address. > # dhcp="dhcp" > # Set root device. > root = "/dev/sda1 ro" > > > Red Hat nash version 4.1.18 starting > Mounted /proc filesystem > Mounting sysfs > Creating /dev > Starting udev > Creating root device > Mounting root filesystem > Switching to new root > init started: BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call > binary > Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 > i686 unknown > > >> Ian >> >> >> >> >> >> > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/