Hi,
I downloaded the xen 3.1.0 tarballs for 64Bit SMP to install it on a HP
DL365 AMD64. After ./install, I added this to the grub menu.lst:
title XenSource-XEN (2.6.18-xen-3.1)
root (hd0,0)
kernel /boot/xen-3.1.0.gz
module /boot/vmlinuz-2.6.18-xen ro root=/dev/cciss/c0d0p1
module /boot/initrd-2.6.18-xen
Additionally I had to run mkinitrd, as there was no initrd for that kernel
after the ./install. Nevertheless, after reboot it ended in a kernel panic.
"Screenshot" of the panic is attached, and can also be found here:
https://www.l00-bugdead-prods.de/Image033.jpg
I ran a depmod and mkinitrd. Then after reboot, the boot process ended in a
panic, see attached screenshot.
Any hint what is going wrong here? Further in the README, there is still Xen
3.0 and Kernel 2.16 mentioned, which should be Xen 3.1 and Kernel 2.18.
cheers
Sebastian
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
The error message clearly indicates that you''ve got a broken /init in your initrd. I guess you''ll need to examine what went wrong during its creation. Jan>>> "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 30.01.08 10:02 >>>Hi, I downloaded the xen 3.1.0 tarballs for 64Bit SMP to install it on a HP DL365 AMD64. After ./install, I added this to the grub menu.lst: title XenSource-XEN (2.6.18-xen-3.1) root (hd0,0) kernel /boot/xen-3.1.0.gz module /boot/vmlinuz-2.6.18-xen ro root=/dev/cciss/c0d0p1 module /boot/initrd-2.6.18-xen Additionally I had to run mkinitrd, as there was no initrd for that kernel after the ./install. Nevertheless, after reboot it ended in a kernel panic. "Screenshot" of the panic is attached, and can also be found here: https://www.l00-bugdead-prods.de/Image033.jpg I ran a depmod and mkinitrd. Then after reboot, the boot process ended in a panic, see attached screenshot. Any hint what is going wrong here? Further in the README, there is still Xen 3.0 and Kernel 2.16 mentioned, which should be Xen 3.1 and Kernel 2.18. cheers Sebastian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi, "Jan Beulich" <jbeulich@novell.com> wrote:> The error message clearly indicates that you''ve got a broken /init in your > initrd. I guess you''ll need to examine what went wrong during itscreation. I just did that. For some reason there was an caps="$(</proc/xen/capabilities)" if [ "$caps" != "${caps%control_d*}" ]; then echo nothing fi I added the "echo nothing" into the if statement, then it worked. After restarting again, it panicked again, but now because of missing cciss HDD controler driver to access the root partition. I added this and it is starting now. Sorry for the noise. Sebastian> > Jan > > >>> "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 30.01.08 10:02 >>> > Hi, > > I downloaded the xen 3.1.0 tarballs for 64Bit SMP to install it on a HP > DL365 AMD64. After ./install, I added this to the grub menu.lst: > > title XenSource-XEN (2.6.18-xen-3.1) > root (hd0,0) > kernel /boot/xen-3.1.0.gz > module /boot/vmlinuz-2.6.18-xen ro root=/dev/cciss/c0d0p1 > module /boot/initrd-2.6.18-xen > > Additionally I had to run mkinitrd, as there was no initrd for that kernel > after the ./install. Nevertheless, after reboot it ended in a kernelpanic.> "Screenshot" of the panic is attached, and can also be found here: > https://www.l00-bugdead-prods.de/Image033.jpg > > I ran a depmod and mkinitrd. Then after reboot, the boot process ended ina> panic, see attached screenshot. > > Any hint what is going wrong here? Further in the README, there is stillXen> 3.0 and Kernel 2.16 mentioned, which should be Xen 3.1 and Kernel 2.18. > > cheers > Sebastian > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 30.01.08 11:04 >>> >"Jan Beulich" <jbeulich@novell.com> wrote: >> The error message clearly indicates that you''ve got a broken /init in your >> initrd. I guess you''ll need to examine what went wrong during its >creation. > >I just did that. >For some reason there was an >caps="$(</proc/xen/capabilities)" >if [ "$caps" != "${caps%control_d*}" ]; then > echo nothing >fiHmm, that section is there on purpose, but the body certainly shouldn''t be empty.>I added the "echo nothing" into the if statement, then it worked. After >restarting again, it panicked again, but now because of missing cciss HDD >controler driver to access the root partition. I added this and it is >starting now.This sounds like your /etc/sysconfig/kernel (INITRD_MODULES) isn''t set up properly. But otoh I assume other kernels get their initrd generated correctly. Maybe you missed some detail of how mkinitrd needs to be invoked, or what prerequisites it has? That would also explain why that section above as empty.>Sorry for the noise.That''s not just noise, thanks for pointing this out. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
"Jan Beulich" <jbeulich@novell.com> wrote:> >>> "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 30.01.08 11:04 >>> > >"Jan Beulich" <jbeulich@novell.com> wrote: > >> The error message clearly indicates that you''ve got a broken /init inyour> >> initrd. I guess you''ll need to examine what went wrong during its > >creation. > > > >I just did that. > >For some reason there was an > >caps="$(</proc/xen/capabilities)" > >if [ "$caps" != "${caps%control_d*}" ]; then > > echo nothing > >fi > > Hmm, that section is there on purpose, but the body certainly shouldn''t > be empty. > > >I added the "echo nothing" into the if statement, then it worked. After > >restarting again, it panicked again, but now because of missing cciss HDD > >controler driver to access the root partition. I added this and it is > >starting now. > > This sounds like your /etc/sysconfig/kernel (INITRD_MODULES) isn''t set up > properly. But otoh I assume other kernels get their initrd generated > correctly. Maybe you missed some detail of how mkinitrd needs to be > invoked, or what prerequisites it has? That would also explain why that > section above as empty.yeah, other kernels do not have this problem, I followed the README file, in point 5) To rebuild a kernel with a modified config... I think, after that I just only ran depmod -a and mkinitrd without parameters, and then it was working, this is the way I usually use. also mkinitrd on sles10sp1 does not know about the -v parameter, and then it did not liked the --with paramters too: mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen Unknown option: -v Try mkinitrd -h srv4:/usr/local/src/dist # mkinitrd -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen Unknown option: -- Try mkinitrd -h these versions are installed: module-init-tools-3.2.2-32.33 mkinitrd-1.2-106.61 Sebastian> > >Sorry for the noise. > > That''s not just noise, thanks for pointing this out. > > Jan > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel