Re: [Xen-users] 2.6.20-1-amd64 Xen with RHEL5 guest

[Alex Samad <alex@xxxxxxxxxxxx>]

On Thu, May 17, 2007 at 12:20:22PM +0100, Daniel P. Berrange wrote:
> On Thu, May 17, 2007 at 04:51:43PM +1000, Alex Samad wrote:
> > On Thu, May 17, 2007 at 02:39:00PM +1000, Alex Samad wrote:
> > > On Wed, May 16, 2007 at 02:39:15PM +0100, Daniel P. Berrange wrote:
> > > > On Wed, May 16, 2007 at 12:34:54PM +1000, Alex Samad wrote:
> > > > > ==============
> > > > > cat rhel5-x86_64.cfg
> > > > > ==============
> > > > > #
> > > > > #  Kernel + memory size
> > > > > #
> > > > > kernel      = '/etc/xen/data/rhel5-x86_64/vmlinuz'
> > > > > ramdisk     = '/etc/xen/data/rhel5-x86_64/initrd.img'
> > > > > memory      = '128'
> > > > > 
> > > > > #
> > > > > #  Disk device(s).
> > > > > #
> > > > > root        = '/dev/sda1 ro'
> > > > 
> > > > This is redundant (&wrong) when booting off the vmlinux & initrd.img
> > > > for purposes of installation. The initrd contains sets up the root
> > > > filesystem in a ramdisk for the install.
> > > got rid of 
> > > 
> > > > 
> > > > > disk        = [ 'phy:vglocal/rhel5-x86_64-disk,sda,w', 
> > > > > 'phy:vglocal/rhel5-x86_64-swap,sdb,w']
> > > > 
> > > > Better off using xvda & xvdb there
> > > 
> > > I am presuming you mean change sda & sdb with xvda xvdb
> > > 
> > > tried that 
> > > 
> > > i captured this of the console during the rhel boot up
> > > XENBUS: Device with no driver: device/vbd/51712                           
> > >                                                                      
> > > XENBUS: Device with no driver: device/vbd/51728                           
> > >                                                                      
> > > XENBUS: Device with no driver: device/vif/0                               
> > >                                                                      
> > 
> > 
> > okay made the changes to xvba & xvbb, went forward with the rhel5 install, 
> > it 
> > wants to partition up the drives. which I let it do in its default way - 
> > which 
> > means I have a /boot, pv1, pv2.
> > From the host machine how can I get to /boot for the vmlinux and the initrd?
> > I am presuming I need these to insert into my xen config file !
> 
> No need. Just use pygrub bootloader. eg instead of kernel + initrd config
> options, use
> 
>   bootloader='/usr/bin/pygrub'

This is a debian host, what package is this part of and will it look in the 
guest disks for this information ?

> 
> It will automatically look in /boot for the guest disk & extract the default
> kernel & initrd. If you use 'xm create -c' it'll present you the usual grub
> style menu for choosing a non-default kernel.
> 
> Dan.
> -- 
> |=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
> |=-           Perl modules: http://search.cpan.org/~danberr/              -=|
> |=-               Projects: http://freshmeat.net/~danielpb/               -=|
> |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users