Mark Wilson
2007-May-29 12:55 UTC
[Xen-users] Missing initial RAM disk after Xen installation
After installing the Xen RPMs on SUSE Enterprise Linux Desktop, I edited /boot/grub/menu.lst file to include: title SUSE with Xen (2.6.18-xen_3.1.0) root (hd0,0) kernel /boot/xen-3.1.0.gz module /boot/vmlinuz-2.6.18-xen_3.1.0 ro root=/dev/hda2 module /boot/initrd-2.6.18-xen_3.1.0.img (based on the advice in the readme file at http://www.xensource.com/download/docs/README-xen31-hostrpms.txt) Unfortunately this fails at the initrd stage with GRUB error 15 (file not found). Digging further, I can see that although a symlink has been created from initrd-2.6-xen.img to initrd-2.6.18-xen_3.1.0.img, initrd-2.6.18-xen_3.1.0.img does not seem to exist. I think I''ve found out why the image is missing, but I''m still stuck! After removing Xen and the Xen kernel, then reinstalling in a terminal (rather than by double-clicking the RPM file), I saw this: hostname:/home/mark/Desktop # rpm -ivh xen-3.1.0-1.i686.rpm Preparing... ########################################### [100%] 1:xen ########################################### [100%] hostname:/home/mark/Desktop # rpm -ivh kernel-xen-2.6.18-3.1.0.i686.rpm Preparing... ########################################### [100%] 1:kernel-xen ########################################### [100%] /sbin/mkinitrd: line 2958: /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab: No such file or directory No ''/'' mountpoint specified in /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab It seems that there is a problem with the RPM... Please can anyone help me work around this? Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-May-29 12:58 UTC
RE: [Xen-users] Missing initial RAM disk after Xen installation
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Mark Wilson > Sent: 29 May 2007 13:56 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Missing initial RAM disk after Xen installation > > After installing the Xen RPMs on SUSE Enterprise Linux > Desktop, I edited /boot/grub/menu.lst file to include: > > title SUSE with Xen (2.6.18-xen_3.1.0) > root (hd0,0) > kernel /boot/xen-3.1.0.gz > module /boot/vmlinuz-2.6.18-xen_3.1.0 ro root=/dev/hda2 > module /boot/initrd-2.6.18-xen_3.1.0.img > > (based on the advice in the readme file at > http://www.xensource.com/download/docs/README-xen31-hostrpms.txt) > > Unfortunately this fails at the initrd stage with GRUB error > 15 (file not found). Digging further, I can see that although > a symlink has been created from initrd-2.6-xen.img to > initrd-2.6.18-xen_3.1.0.img, initrd-2.6.18-xen_3.1.0.img does > not seem to exist. > > I think I''ve found out why the image is missing, but I''m > still stuck! After removing Xen and the Xen kernel, then > reinstalling in a terminal (rather than by double-clicking > the RPM file), I saw this: > > hostname:/home/mark/Desktop # rpm -ivh xen-3.1.0-1.i686.rpm > Preparing... ########################################### [100%] > 1:xen ########################################### [100%] > hostname:/home/mark/Desktop # rpm -ivh > kernel-xen-2.6.18-3.1.0.i686.rpm > Preparing... ########################################### [100%] > 1:kernel-xen ########################################### [100%] > /sbin/mkinitrd: line 2958: > /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab: No such file or directory > No ''/'' mountpoint specified in > /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab >I believe this is a problem caused by a bad "mkinitrd" script - I''ve seen it once before. Try looking in the archive on www.xensource.com for this mailing list. -- Mats> It seems that there is a problem with the RPM... Please can > anyone help me work around this? > > Cheers, Mark >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Wilson
2007-May-29 13:31 UTC
Re: [Xen-users] Missing initial RAM disk after Xen installation
Thanks Mats - I think I''ve found the message you referred to: http://lists.xensource.com/archives/html/xen-users/2007-04/msg00367.html however it reads as though the only workaround would be to compile from source - i.e. dump the RPMs and download the tarballs. As a Linux newbie, I''m a little anxious about this so I just wanted to confirm that would be the recommended approach before I get in too deep. Mark> From: "Petersson, Mats" <Mats.Petersson@amd.com> > Date: Tue, 29 May 2007 14:58:59 +0200 > To: Mark Wilson <markw@markwilson.co.uk>, <xen-users@lists.xensource.com> > Conversation: [Xen-users] Missing initial RAM disk after Xen installation > Subject: RE: [Xen-users] Missing initial RAM disk after Xen installation > > > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of >> Mark Wilson >> Sent: 29 May 2007 13:56 >> To: xen-users@lists.xensource.com >> Subject: [Xen-users] Missing initial RAM disk after Xen installation >> >> After installing the Xen RPMs on SUSE Enterprise Linux >> Desktop, I edited /boot/grub/menu.lst file to include: >> >> title SUSE with Xen (2.6.18-xen_3.1.0) >> root (hd0,0) >> kernel /boot/xen-3.1.0.gz >> module /boot/vmlinuz-2.6.18-xen_3.1.0 ro root=/dev/hda2 >> module /boot/initrd-2.6.18-xen_3.1.0.img >> >> (based on the advice in the readme file at >> http://www.xensource.com/download/docs/README-xen31-hostrpms.txt) >> >> Unfortunately this fails at the initrd stage with GRUB error >> 15 (file not found). Digging further, I can see that although >> a symlink has been created from initrd-2.6-xen.img to >> initrd-2.6.18-xen_3.1.0.img, initrd-2.6.18-xen_3.1.0.img does >> not seem to exist. >> >> I think I''ve found out why the image is missing, but I''m >> still stuck! After removing Xen and the Xen kernel, then >> reinstalling in a terminal (rather than by double-clicking >> the RPM file), I saw this: >> >> hostname:/home/mark/Desktop # rpm -ivh xen-3.1.0-1.i686.rpm >> Preparing... ########################################### [100%] >> 1:xen ########################################### [100%] >> hostname:/home/mark/Desktop # rpm -ivh >> kernel-xen-2.6.18-3.1.0.i686.rpm >> Preparing... ########################################### [100%] >> 1:kernel-xen ########################################### [100%] >> /sbin/mkinitrd: line 2958: >> /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab: No such file or directory >> No ''/'' mountpoint specified in >> /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab >> > I believe this is a problem caused by a bad "mkinitrd" script - I''ve > seen it once before. Try looking in the archive on www.xensource.com for > this mailing list. > > -- > Mats > >> It seems that there is a problem with the RPM... Please can >> anyone help me work around this? >> >> Cheers, Mark >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-May-29 13:36 UTC
RE: [Xen-users] Missing initial RAM disk after Xen installation
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Mark Wilson > Sent: 29 May 2007 14:32 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Missing initial RAM disk after Xen > installation > > Thanks Mats - I think I''ve found the message you referred to: > http://lists.xensource.com/archives/html/xen-users/2007-04/msg00367.html> however it reads as though the only workaround would be to > compile from > source - i.e. dump the RPMs and download the tarballs. As a > Linux newbie, > I''m a little anxious about this so I just wanted to confirm > that would be > the recommended approach before I get in too deep.No, as long as the rest of the install works OK, you should be able to just fix up the "mkinitrd" script (do "which mkinitrd" to see where it "lives"), and perform the "mkinitrd /boot/some-name-of-initrd.img 2.6.18-xen" [note, you may need to modify the "2.6.18-xen" to match whatever version the kernel has, and of course use a more sensible name of the initrd... ;-)]. The problem isn''t with the RPM as such, it''s the "mkinitrd" script that appears to be missing a space somehow. -- Mats> > Mark > > > > From: "Petersson, Mats" <Mats.Petersson@amd.com> > > Date: Tue, 29 May 2007 14:58:59 +0200 > > To: Mark Wilson <markw@markwilson.co.uk>, > <xen-users@lists.xensource.com> > > Conversation: [Xen-users] Missing initial RAM disk after > Xen installation > > Subject: RE: [Xen-users] Missing initial RAM disk after Xen > installation > > > > > > > >> -----Original Message----- > >> From: xen-users-bounces@lists.xensource.com > >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > >> Mark Wilson > >> Sent: 29 May 2007 13:56 > >> To: xen-users@lists.xensource.com > >> Subject: [Xen-users] Missing initial RAM disk after Xen > installation > >> > >> After installing the Xen RPMs on SUSE Enterprise Linux > >> Desktop, I edited /boot/grub/menu.lst file to include: > >> > >> title SUSE with Xen (2.6.18-xen_3.1.0) > >> root (hd0,0) > >> kernel /boot/xen-3.1.0.gz > >> module /boot/vmlinuz-2.6.18-xen_3.1.0 ro root=/dev/hda2 > >> module /boot/initrd-2.6.18-xen_3.1.0.img > >> > >> (based on the advice in the readme file at > >> http://www.xensource.com/download/docs/README-xen31-hostrpms.txt) > >> > >> Unfortunately this fails at the initrd stage with GRUB error > >> 15 (file not found). Digging further, I can see that although > >> a symlink has been created from initrd-2.6-xen.img to > >> initrd-2.6.18-xen_3.1.0.img, initrd-2.6.18-xen_3.1.0.img does > >> not seem to exist. > >> > >> I think I''ve found out why the image is missing, but I''m > >> still stuck! After removing Xen and the Xen kernel, then > >> reinstalling in a terminal (rather than by double-clicking > >> the RPM file), I saw this: > >> > >> hostname:/home/mark/Desktop # rpm -ivh xen-3.1.0-1.i686.rpm > >> Preparing... ########################################### [100%] > >> 1:xen ########################################### [100%] > >> hostname:/home/mark/Desktop # rpm -ivh > >> kernel-xen-2.6.18-3.1.0.i686.rpm > >> Preparing... ########################################### [100%] > >> 1:kernel-xen ########################################### [100%] > >> /sbin/mkinitrd: line 2958: > >> /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab: No such file > or directory > >> No ''/'' mountpoint specified in > >> /boot/initrd-2.6.18-xen_3.1.0.img/etc/fstab > >> > > I believe this is a problem caused by a bad "mkinitrd" script - I''ve > > seen it once before. Try looking in the archive on > www.xensource.com for > > this mailing list. > > > > -- > > Mats > > > >> It seems that there is a problem with the RPM... Please can > >> anyone help me work around this? > >> > >> Cheers, Mark > >> > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users