On 31 Jan 2007 at 14:31, Petersson, Mats wrote:
>
>
> > -----Original Message-----
> > From: Ligesh [mailto:myself@xxxxxxxxxx]
> > Sent: 31 January 2007 13:18
> > To: Petersson, Mats
> > Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: DomU boot fails with can't find root on Fedora 6
> >
> > On Wed, Jan 31, 2007 at 02:10:21PM +0100, Petersson, Mats wrote:
> > >
> > > Probably caused by the fact that you're using the same
> > initrd for your
> > > guest as you do for the host - you should use a separate
> > initrd for your
> > > guest (using the same kernel is fine). My guess is that the
> > initrd is
> > > "messing" with the root argument.
> > >
> >
> > But initrd is nothing but a archive of the drivers. I
> > checked it, and it doesn't contain an etc or anything that
> > can mess with the boot. Or if it does, that's a very wrong
> > design. Anyway how do I create a new initrd that won't mess
> > with the boot?
>
> Usually, the initrd contains a little bit of scripting too, which sets
> up devices and such, and I suspect this is what causes a problem.
>
> You can create a new initrd with "mkinitrd file linuxver", such as
> "mkinitrd someplace/initrd-xen 2.6.18-xen" - obviously, don't overwrite
> your existing /boot initrd.
For me (using SUSE) the following did help: mount your file structure in Dom0
(plus the /dev tree like "mount --bind /dev /mnt/dev"), then do a "chroot /mnt
mkinitrd", possibly with "-d root_device". Also assuming that some magic pulls
out
kernel and initrd from the device or image to boot those, like:
bootloader = '/usr/lib/xen/boot/domUloader.py'
bootentry = 'sda1:/boot/vmlinuz-xen,/boot/initrd-xen'
>
> I'm by no means an expert on initrd (nor do I use LVM on any of my
> current machines), but the above is what I understand of it. (I had a
> look at mkinitrd, but it's a fairly BIG shell-script file - but from
> what I can see, it does set up a bunch of script stuff, and some are
> directly related to using LVM).
>
> --
> Mats
> >
> > PS: I solved the fedora-xen ml problem. I have around 60
> > mailboxes, and it appears I had filtered all mails from
> > redhat to another mbox, because rh used to spam me with their
> > newsletter. So I will ask there too.
> >
> > Thanks.
> >
> >
> >
> >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|