taoj2@cs.rpi.edu
2007-Jul-26 19:23 UTC
[Fedora-xen] Kernel panic - not syncing: Attepmted to kill init!
Hi, While I use "xm create -c guestvm" to create the domain at Fedora Core 6, the following error msg appears: Kernel panic - not syncing: Attepmted to kill init! This never happened before, when several guest domains are running with CPU usage < 5%, and I was trying to create a new one. This time, the CPU usage of the running guest domains are 25%, much higher than before, and above error msg appears while I create a new guest domain. Is this due to the reason of not enough resource can be allocated to the new domain? Any clue? Thanks. Best Angel
master@bradleyland.com
2007-Jul-26 22:01 UTC
Re: [Fedora-xen] Kernel panic - not syncing: Attepmted to kill init!
Did you recently update the kernel? And get a new initrd as well? I ask because from what I''ve seen, this is a common problem. When you update the kernel (and a new initrd is created), the initrd doesn''t get built to include the xenblk.ko driver. You can check by unpacking the initrd into a directory using this command: gunzip < /boot/initrd.img |cpio -i --make-directories Create a new directory first, cd to the directory, run the above command. Look at the init script. Does it have the following lines in it? echo "Loading xenblk.ko module" insmod /lib/xenblk.ko If not, you''ll need to move xenblk.ko into the initrd directory (correct version of course), add the above lines and repack the initrd using this command: find . | cpio --quiet -co | gzip -9 > /boot/initrd-XXXXX.img Just went through this (again) so it''s fresh in my mind. I tried using the mkinitrd command to create a proper initrd in the domU but couldn''t get it to add the xenblk driver for some reason. If the above isn''t the problem, I''ll bet it''s leprechauns.