[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] [Patch] booting Guest domains w/o initrd on RHEL4


  • To: "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Wed, 30 Nov 2005 14:29:52 -0800
  • Delivery-date: Wed, 30 Nov 2005 22:34:20 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcX1rSuHqAFP9dypQNq6zR+1zmCutAAUCkFw
  • Thread-topic: [Xen-ia64-devel] [Patch] booting Guest domains w/o initrd on RHEL4

This is the same point I got to when I tried this two weeks
ago.  I think the problem is that just like dom0 requires
an initrd to boot RHEL4, domU also requires an initrd to
boot a RHEL4 image.  I don't think initrd for domU is
implemented yet.

Dan 

> -----Original Message-----
> From: Akio Takebe [mailto:takebe_akio@xxxxxxxxxxxxxx] 
> Sent: Wednesday, November 30, 2005 5:48 AM
> To: Akio Takebe; Magenheimer, Dan (HP Labs Fort Collins); 
> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-ia64-devel] [Patch] booting Guest domains 
> w/o initrd on RHEL4
> 
> Hi all
> 
> I'm sorry.
> I have not been able to boot completely yet.
> 
> DomU's booting stoped at the below point. :<
> -------------------------
> ALSA device list:                                             
>             
>                 
>   No soundcards found.
> NET: Registered protocol family 2
> Registering block device major 3 
> IP: routing cache hash table of 8192 buckets, 128Kbytes
> TCP established hash table entries: 65536 (order: 6, 1048576 bytes)
> TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)       
> TCP: Hash tables configured (established 65536 bind 65536)  
> arp_tables: (C) 2002 David S. Miller                      
> NET: Registered protocol family 1   
> NET: Registered protocol family 17
>                                   
> -------------------------
> 
> Does anyone have the same problem?
> 
> Best Regards,
> 
> Akio Takebe
> >Hi, all
> >
> >This patch can boot DomU WITHOUT initrd as RHEL3
> >when we boot Xen + Domain0 using RHEL4.
> >
> >Domain0 using RHEL4 must use initrd.
> >The following error is showed when we boot DomainU.
> >  RAMDISK: Couldn't find valid RAM disk image starting at 0.
> >This error is caused by "bp->initrd_start" used Domain0 value.
> >I fixed it's bug.
> >But this patch is temporal,
> >because I want to make a part of initrd in libxc and so on.
> >Please wait. ;)
> >
> >Signed-off-by Akio Takabe <takebe_akio@xxxxxxxxxxxxxx>
> >
> >==============================
> >diff -r 0ee00faf332d xen/arch/ia64/xen/dom_fw.c
> >--- a/xen/arch/ia64/xen/dom_fw.c        Wed Nov 23 21:23:28 2005
> >+++ b/xen/arch/ia64/xen/dom_fw.c        Wed Nov 30 19:29:43 2005
> >@@ -832,9 +832,14 @@
> >        bp->console_info.orig_x = 0;
> >        bp->console_info.orig_y = 24;
> >        bp->fpswa = 0;
> >-        bp->initrd_start = (dom0_start+dom0_size) -
> >-                (PAGE_ALIGN(ia64_boot_param->initrd_size) + 4*1024*
> >1024);
> >-        bp->initrd_size = ia64_boot_param->initrd_size;
> >+       if (d == dom0) {
> >+                bp->initrd_start = (dom0_start+dom0_size) -
> >+                        
> (PAGE_ALIGN(ia64_boot_param->initrd_size) + 4*
> >1024*1024);
> >+                bp->initrd_size = ia64_boot_param->initrd_size;
> >+       }else{
> >+                bp->initrd_start = 0;
> >+                bp->initrd_size = 0;
> >+       }
> >                 printf(" initrd start %0xlx", bp->initrd_start);
> >                 printf(" initrd size %0xlx", bp->initrd_size);
> >
> >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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.