Ok, I have sorted out setting up grub tow different ways. One with LVM and one without.
But I still get the kernel-panic which appears to be the same in both cases. I get something like Kernel panic : not syncing : attempted to kill init Then the sytem reboots. I have found one clue on the net so far. <quote> I have finally figured it out ... The reason why I got the first panic is because I didn't have Initial RAM Disk support compiled in the kernel ( I had it as a module), it turns out a module won't work ... ... but hey I have a bootable 2.6.16.1 kernel !!! So the lessons learnt from this exercise ... the linux kernel would panic if some of the drivers are not configured as kernel ( i.e if they are M instead of Y) ... so make sure atleast the following are compiled into the kernel.. 1. Initial RAM disk support ( Drivers-->Block Devices) 2. ATA/ATAPI Support ( That includes the support to chipsets generic or otherwise ... as well as DMA) 3. The filesystems ... (ext2, ext3) All of the above needs to be compiled into the kernel not as a module ... </quote> So I am guessing this is my problem. Ok, so how do I determine what is compiled in versus being a module on my kernel? I can run lsmod ... but what is an easy way to know what the modules do? Is there an obvious module that is the RAM Disk? ??? Is there a simple command that will tell me what is and is not compiled into a kernel? TIA my gurus, BobLQ ---------- Forwarded message ---------- From: Bob La Quey <[EMAIL PROTECTED]> Date: Mar 24, 2007 2:55 PM Subject: Oboy! I got a kernel panic ... To: Main Discussion List for KPLUG <[email protected]> For the first time in years. Here is how I did it. But first a disclaimer. I am just hacking along with no real understanding of what it is that I am doing :) I tried setting up Xen on a Ubuntu 6.06 server that uses LVM. I think the interaction between LVM and Xen caused the problem but ... I do not know enough about either to be sure. I started with the very good howto at http://www.howtoforge.com/xen_3.0_ubuntu_dapper_drake They offer the grub entry title Xen 3.0 / XenLinux 2.6 kernel /boot/xen-3.gz module /boot/vmlinuz-2.6-xen root=/dev/hda2 ro module /boot/initrd.img-2.6.16-xen which I mindlessly changed to title Xen 3.0 / XenLinux 2.6 root (hd0,4) kernel /boot/xen-3.gz module /vmlinuz-2.6-xen root=/dev/mapper/Ubuntu-root ro module /initrd.img-2.6.16-xen (In early attempts grub could not find the modules ... so I added the root= mapper stuff that I simply copied from the orignal Ubuntu grub lines.) This then results in a kernel panic, follwed by an almost instant reboot. Does anyone know how to mix Xen and LVM ... or should I just for get LVM for a first cut until I am more familiar with Xen? BobLQ -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
