WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] [FYI] Recipe of build and boot of Xen/IA64

To: "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [FYI] Recipe of build and boot of Xen/IA64
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Tue, 13 Dec 2005 07:05:14 -0800
Delivery-date: Tue, 13 Dec 2005 15:07:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcX8sbtn8RfGfVOpSPqqr/k9nxzBHQDRCaEg
Thread-topic: [Xen-ia64-devel] [FYI] Recipe of build and boot of Xen/IA64
Hi Akio --

How did you build your (dom0) RHEL4 root disk?  I see you are
booting using /dev/sda2 as root. The standard
RHEL4 build process creates an LVM disk as root and the process
you describe won't work with an LVM root disk.

Thanks,
Dan

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Akio Takebe
> Sent: Friday, December 09, 2005 4:13 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] [FYI] Recipe of build and boot of Xen/IA64
> 
> Hi,
> 
> We can boot RHEL4 domU without initrd.
> I have written the recipe.
> (Thank you for many advice, everyone :-))
> 
> My enviroment is;
>   Machine  : Tiger4
>   Dom0 OS  : RHEL4 U2
>   DomU OS  : RHEL4 U2
>   changeset: 8241:0255f48b757f
> 
> ----------------------------
> Build xen
>  1. Download source
>     # hg clone http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> 
>  2. # make world -j4
>     
>  3. make menuconfig in Dom0
>     # cd linux-2.6.12-xen0
>     # make menuconfig
>       CONFIG_IA64_DIG=y
>     # cd ..
> 
>  4. make menuconfig in DomU
>     # cd linux-2.6.12-xenU
>     # make menuconfig 
>       CONFIG_IA64_DIG=y
>       # CONFIG_EFI_RTC is not set
>     # cd ..
> 
>  5. # make kernels -j4
> 
>  6. # make uninstall
> 
>  7. # make install-tools
> 
>  8. copy kernels and xen
>     # cp xen/xen.gz /boot/efi/efi/xen/
>     # cp linux-2.6.12-xen0/vmlinux.gz 
> /boot/efi/efi/xen/vmlinuz-2.6.12-xen0
>     # cp linux-2.6.12-xenU/vmlinux.gz /boot/vmlinux-2.6.12-xenU
> 
>  9. make initrd for Dom0
>     # cd linux-2.6.12-xen0/
>     # make modules_install
>     # mkinitrd -f /boot/efi/efi/xen/initrd-2.6.12-xen0.img 
> 2.6.12.6-xen0 --builtin mptbase --builtin mptscsih
>     # cd ..
> 
> ---------------------------------
> Make OSimg for DomU
>  1. make file
>     # dd if=/dev/zero of=/root/rhel4.img bs=1M count=4096
>     # mke2fs -F -j /root/rhel4.img
>     # mount -o loop /root/rhel4.img /mnt
>     # cp -ax /{dev,var,etc,usr,bin,sbin,lib} /mnt
>     # mkdir /mnt/{root,proc,sys,home,tmp}
> 
>  2. modify DomU's fstab
>     # vi /mnt/etc/fstab 
>        /dev/hda1   /            ext3    defaults        1 1
>        none        /dev/pts     devpts  gid=5,mode=620  0 0
>        none        /dev/shm     tmpfs   defaults        0 0
>        none        /proc        proc    defaults        0 0
>        none        /sys         sysfs   defaults        0 0
> 
>  3. modify inittab (runlevel and tty)
>     # vi /mnt/etc/inittab
>        id:3:initdefault:
>     # Run gettys in standard runlevels
>     1:2345:respawn:/sbin/mingetty tty0
>     #1:2345:respawn:/sbin/mingetty tty1
>     #2:2345:respawn:/sbin/mingetty tty2
>     #3:2345:respawn:/sbin/mingetty tty3
>     #4:2345:respawn:/sbin/mingetty tty4
>     #5:2345:respawn:/sbin/mingetty tty5
>     #6:2345:respawn:/sbin/mingetty tty6
>     
>  4. add tty0 into /etc/securetty
>     # vi /mnt/etc/securetty (add tty0)
>  
>  5. umount
>     # umount /mnt
>     
> -------------------------------------
> Boot Xen
>  1. replace elilo
>     download from the below
>     http://elilo.sourceforge.net/cgi-bin/blosxom
>     
>  2. modify elilo.conf
>      prompt
>      timeout=20
>      default=xen
>      relocatable
>      
>      image=vmlinuz-2.6.12-xen0
>              label=xen
>              vmm=xen-.gz
>              initrd=initrd-2.6.12-xen0.img
>              read-only
>              append="com2=115200,8n1 console=com2 sched=bvt 
> tbuf_size=128 -- nomca nosmp console=tty0 
> console=ttyS1,115200,8n1 rhgb root=/dev/sda2"
>      image=vmlinuz-2.6.9-22.EL
>              label=linux
>              initrd=initrd-2.6.9-22.EL.img
>              read-only
>              append="rhgb root=/dev/sda2"
>  3. make config of DomU
>    # vi /etc/xen/rhel4
>      kernel = "/boot/vmlinux-2.6.12-xenU"
>      memory = 384
>      name = "rhel4"
>      nics=0
>      disk = [ 'file:/root/rhel4.img,hda1,w' ]
>      root = "/dev/hda1 ro"
>      extra = "3"
>  
>  4. After boot xen and dom0, start xend
>    # /etc/init.d/xend start
>    ( In the debugging case, # XEND_DEBUG=1 xend trace_start )
>    
>  5. start domU
>    # xm create -c rhel4
>  
> Best Regards,
> 
> Akio Takebe
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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

<Prev in Thread] Current Thread [Next in Thread>