Foreman, Tim
2007-Mar-01 16:14 UTC
RE: [Xen-users] Xen 3.0.4 on RH EL 4.4 - can''t make it boot kerne l
> -----Original Message----- > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > Sent: Thursday, March 01, 2007 10:12 AM > To: Foreman, Tim > Cc: xen-users@lists.xensource.com > Subject: RE: [Xen-users] Xen 3.0.4 on RH EL 4.4 - can''t make it boot > kerne l > > > > -----Original Message----- > > From: Foreman, Tim [mailto:tforeman@ibsys.com] > > Sent: 01 March 2007 16:02 > > To: Petersson, Mats > > Subject: RE: [Xen-users] Xen 3.0.4 on RH EL 4.4 - can''t make > > it boot kerne l > > > > > Ok, that didn''t tell me what I wanted to know, how about > > the output of > > > "mount"? > > > > > > I want to see what "/" is really mounted to. > > > > It''s mounted to /dev/hda1: > > > > /dev/hda1 on / type ext2 (rw) > > none on /proc type proc (rw) > > none on /sys type sysfs (rw) > > none on /dev/pts type devpts (rw,gid=5,mode=620) > > usbfs on /proc/bus/usb type usbfs (rw) > > none on /dev/shm type tmpfs (rw) > > /dev/hda2 on /opt type ext2 (rw) > > /dev/hda3 on /usr type ext2 (rw) > > /dev/hda6 on /var type ext2 (rw) > > /dev/hda7 on /var/log/IBS type ext2 (rw) > > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > > That looks sane. > > > > > Which is why I had root=/dev/hda1 in grub.conf. > > Yes, just checking - because you wouldn''t be the first trying to boot > from the wrong place! ;-) [This is particularly the case when dealing > with "error 6", as that means "No such device" - error 2 is "no such > file or directory"]. > > You also get an error loading the IDE driver, which may be > the cause of > all other problems. You may want to try rebuilding the kernel with a > builtin IDE driver (as you DO need that driver allways, using it as a > module is only to satisfy those who complain when they get an > IDE driver > when they only have SCSI drives on the system). > > I''ve also CC''d this back to the Xen users list so that others may take > part in the communication. > > > > > Thanks for your assistance. > > You''re welcome.I was hoping to avoid rebuilding the kernel, but the stuff I found using Google seemed to indicate that the ide module might have been the issue. I guess I''ll try heading down that road. --Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
bdarlt
2007-Mar-07 14:20 UTC
[Xen-users] RE: Xen 3.0.4 on RH EL 4.4 - can''t make it boot kerne l
Foreman, Tim wrote:> >> You also get an error loading the IDE driver, which may be >> the cause of all other problems. You may want to try rebuilding the >> kernel with a >> builtin IDE driver > > I was hoping to avoid rebuilding the kernel, but the stuff I found > using Google seemed to indicate that the ide module might have been > the issue. > --Tim >I had this same error. Sadly I am too late to help you avoid some work/compile time. But for the benefit of others... *Don''t rebuild the kernel*, just rebuild the initrd image. My IDE controller doesn''t appear in the default initrd image included in the RPMs from Xen (for RHEL 4 anyway), but there is a module in the RPM for it. I had to rebuild the initrd image with my IDE controller driver in. This is the same as the old Linux problem of SCSI controllers - I need the disk to load the driver, but need the driver to access the disk. 0 Boot to a working Linux 1 Run "lspci | grep IDE" to find out which IDE controller you are using 1a My output looks like this: 00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 2 Look in the kernel/drivers/ide/pci directory to find out what your driver''s filename is. 2a There is one file with "via" in the name called via82cxxx.ko, so I probably want that one. 3 Run: "mkinitrd --with=ide-driver-filename-without-.ko initrd-image-name kernel-version" 3a For me, because I have a Via controller, I ran this: mkinitrd --with=via82cxxx initrd-2.6-xenbrad.img 2.6.16.33-xen_3.0.4.1 4 Now use the newly create initrd image when you boot to your Dom0 kernel - do this by say editing grub.conf 4a Worked like a charm for me. -- View this message in context: http://www.nabble.com/RE%3A-Xen-3.0.4-on-RH-EL-4.4---can%27t-make-it-boot-kerne-l-tf3327592.html#a9353653 Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users