SCIENTIFIC-LINUX-USERS Archives

May 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Troy Dawson <[log in to unmask]>
Reply To:
Troy Dawson <[log in to unmask]>
Date:
Thu, 22 May 2008 11:58:44 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Jan Kundrát wrote:
> Hi,
> when trying to use a kernel/initrd from SL5.1 i686 Xen dom0 (right now,
> the /boot/initrd-2.6.18-53.1.21.el5xen.img and corresponding kernel) as
> a kernel for domU, the domU won't boot when it's set up to use /dev/xvda
> for root (that's how Xen exports virtual block devices to Xen).
> 
> The solution we use is to run `mkinitrd -f -v --preload=xenblk
> --preload=xennet /boot/initrd-2.6.18-53.1.21.el5xen.img.preloadedxen
> 2.6.18-53.1.21.el5xen` to create a new initrd, which is trivial, but
> annoying. Would it be possible to add this to the kernel-xen RPM?
> 
> Cheers,
> -jkt
> 

Hi,
We do not touch the kernel rpm's.  Not at all.  So the answer is no, I will not 
put that into the kernel rpm.  (the kernel-xen rpm is built from the main 
kernel src rpm)

But I'm a little confused about what you are doing.

Are you trying to boot your guest machines (domU) from your host (dom0) 
machines /boot/ area?  If you are, that sounds dangerous.

Or are you copying your boot kernels from your host machine into your guest 
machines?  If so, I don't see the point, since your guest machines should 
already have their kernel when they are made.

Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__________________________________________________

ATOM RSS1 RSS2