Re: [Xen-users] ramdisk option in domU config file does not work

[David F Barrera <dfbp@xxxxxxxxxx>]

On Tue, 2005-07-26 at 17:22 -0500, Anthony Liguori wrote:
> Li Ge wrote:
> 
> > This problem seems to have something to do with the size of the 
> > ramdisk file. But I am not quite sure.
> >
> > I tried it on different distros(SLES9, RHEL4, FC3). Here is what I 
> > observed:
> >
> > 1. Can not create domU with ramdisk option using the domU initrd file 
> > (1.2 MB) of SLES9 or the domU initrd file (1.4 MB) of RHEL.
> > 2. I can create domU on one RHEL box with ramdisk option using the 
> > initrd-2.6.12-xenU file copied from another Fedora Core box, which has 
> > relatively smaller file size (300KB). But using the original ramdisk 
> > file of RHEL, I failed to create domU.
> >
> > Is there a limitation for ramdisk file size, for example <1M?
> >
> The typically limitation is 4MB which is what our default ramdisk size is.
> 
> Please note, that you cannot use out-of-the-box ramdisk that come from 
> distros as they contain kernel modules that have not been compiled for 
> Xen.  You must make a ramdisk with the appropriate utilities.
> 
> Dave might be running into the same problem.
No, I am making the initrd for the appropriate build.
> 
> Regards,
> 
> Anthony Liguori
> 
> > Thanks,
> > Li
> >
> > Inactive hide details for 
> > dfbp@xxxxxxxxxxxxxxxxxxxxxxxxxxxx@us.ltcfwd.linux.ibm.com
> >
> >
> >                         *dfbp@xxxxxxxxxxxxxxxxxxxxxxx*
> >                         Sent by: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> >
> >                         07/26/2005 02:26 PM
> >
> >     
> >
> > To
> >     
> > boris.lenzinger@xxxxxxxxx
> >
> > cc
> >     
> > Li Ge/Austin/IBM@IBMUS, xen-users@xxxxxxxxxxxxxxxxxxx
> >
> > Subject
> >     
> > Re: [Xen-users] ramdisk option in domU config file does not work
> >
> >     
> >
> >
> > I have 1GB of memory on my machine, of which 756 are free. Whenever I
> > try to start a DomU with an initrd file, I get the same error that Li Ge
> > reported:
> > Using config file "vm1.cfg".
> > Error: Error creating domain: (0, 'Error')
> >
> > DomU will start just fine without the initrd; however, in one case where
> > I have a DomU with a Reiser FS, I need to be able to use the initrd (I
> > know I can build support for Reiser into the kernel, but that is not the
> > point).
> >
> > On Tue, 2005-07-26 at 11:18 +0200, Boris Lenzinger wrote:
> > > Hi,
> > >
> > > I had this problem (well I think it was the same): you do not have
> > > enough free memory to run your instance.
> > >
> > > run:
> > > xm info
> > >
> > > It will tell you how much free memory you have.
> > > First solution is to decrease the memory in the configuration to check
> > > if you can run your configuration.
> > > If it is working (and you need more memory), decrease memory of dom0.
> > >
> > > If still not working, what is the log file saying ? (/var/log/xend.log
> > > on a fedora distribution)
> > >
> > > Boris
> > >
> > > Li Ge wrote:
> > >
> > > > Hi,
> > > > I added ramdisk option in domU config file to let it load initrd when
> > > > domU is booting up. I got the follow error message:
> > > >
> > > > # xm create /root/vm1.cfg -c
> > > > Using config file "/root/vm1.cfg".
> > > > Error: Error creating domain: (0, 'Error')
> > > >
> > > > When I commented the ramdisk option out, the problem went away and I
> > > > could start domU without a problem. Here is the domU config file I 
> > used:
> > > >
> > > > # Kernel image file.
> > > > kernel = "/boot/vmlinuz-2.6-xenU"
> > > >
> > > > # Optional ramdisk.
> > > > #ramdisk = "/boot/initrd-2.6.12-xenU-reiserFS"
> > > > ramdisk = "/boot/initrd-2.6.12-xenU"
> > > >
> > > > # Initial memory allocation (in megabytes) for the new domain.
> > > > memory = 128
> > > >
> > > > # A name for your domain. All domains must have different names.
> > > > name = "vm1"
> > > >
> > > > disk = [ 'phy:sda7,hda1,w' ]
> > > >
> > > > # Set if you want dhcp to allocate the IP address.
> > > > #dhcp="dhcp"
> > > > # Set netmask.
> > > > #netmask=
> > > > # Set default gateway.
> > > > #gateway=
> > > > # Set the hostname.
> > > > #hostname= "vm%d" % vmid
> > > >
> > > > # Set root device.
> > > > root = "/dev/hda1 ro"
> > > >
> > > > # Sets runlevel 4.
> > > > extra = "4"
> > > >
> > > > Could it be something I've missed? The xen version is the 
> > xen-unstable
> > > > tree with latest changeset 5814.
> > > >
> > > > Thanks,
> > > > Li
> > > >
> > > 
> > >------------------------------------------------------------------------
> > > >
> > > >_______________________________________________
> > > >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
> > >
> > -- 
> > Regards,
> >
> > David F Barrera
> > Linux Technology Center
> > Systems and Technology Group, IBM
> >
> > "The wisest men follow their own direction. "
> >                                                        Euripides
> >
> >
> > _______________________________________________
> > 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
> >
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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