WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
From: David F Barrera <dfbp@xxxxxxxxxx>
Date: Tue, 21 Dec 2004 15:25:46 -0600
Delivery-date: Tue, 21 Dec 2004 21:26:48 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Ian,

OK. I copied all the contents from (hdc3) /dev to (hdc1) /dev, and that let's me boot xenU on hdc1. The problem, however, is that this is not they way RHEL 4 works--I need to figure out how the xen0 is able to boot off essentially the same setup.

[root@dyn95394184 xen]# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      495        0      r----    126.0
test1                   1        64        0      -b---       2.0    9601
[root@dyn95394184 xen]#




-------- Original Message --------
Subject: Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Date:   Tue, 21 Dec 2004 12:53:15 -0600
From:   David F Barrera <dfbp@xxxxxxxxxx>
To:     xen-devel@xxxxxxxxxxxxxxxxxxxxx
References: <E1CgWrK-0003vv-00@xxxxxxxxxxxxxxxxx> <41C844BA.7020801@xxxxxxxxxx>



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/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel




-------------------------------------------------------
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/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel