[Xen-bugs] [Bug 110] Ramdisk option in domU config file does not work

[lge@xxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=110

lge@xxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major



------- Additional Comments From lge@xxxxxxxxxx  2005-07-27 19:41 -------
I have posted the problem I saw on the xen-user mailing list and got some 
updates on it. So I am copying them to the bug report....

****************************************************************************
Sorry, I guess that " the original ramdisk file of RHEL" is kind of misleading 
here. What I really meant was the ramdisk file generated on RHEL and based on 
2.6.12-xenU, not the ramdisk file comes from the distro. 

A little bit more information to answer Boris' question:

1. I have 1G memory. Dom0 used 512 MB. In domU file, I set "memory = 128". So 
it should have enough memory to use.
2. /var/log/xend.log does not say much. Here is the output:

[2005-07-26 17:40:47 xend] DEBUG (image:129) initDomain: cpu=-1 mem_kb=225280 
ssidref=-1 dom=4
[2005-07-26 17:40:47 xend] DEBUG (XendDomainInfo:674) init_domain> Created 
domain=4 name=vm1 memory=220
[2005-07-26 17:40:47 xend] INFO (image:178) buildDomain os=linux dom=4 vcpus=1
[2005-07-26 17:40:47 xend] INFO (XendRoot:128) EVENT> xend.domain.create 
['vm1', 4]
[2005-07-26 17:40:47 xend] INFO (XendRoot:128) EVENT> xend.virq 3

Thanks,
Li

aliguori@xxxxxxxxxxxxxxxxxxxxxxx

aliguori@xxxxxxxxxxxxxxxxxxxxxxx 
Sent by: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
07/26/2005 05:22 PM     
        

To

Li Ge/Austin/IBM@IBMUS

cc

xen-users-bounces@xxxxxxxxxxxxxxxxxxx, dfbp@xxxxxxxxxxxxxxxxxxxxxxx, xen-
users@xxxxxxxxxxxxxxxxxxx, boris.lenzinger@xxxxxxxxx

Subject

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

        

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.

Regards,

Anthony Liguori

> Thanks,
> Li
>
> Inactive hide details for 
> dfbp@xxxxxxxxxxxxxxxxxxxxxxxxxxx@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



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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