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@lists.xensource.com http://lists.xensource.com/xen-users
Boris Lenzinger
2005-Jul-26 09:18 UTC
Re: [Xen-users] ramdisk option in domU config file does not work
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@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/26/05, Boris Lenzinger <boris.lenzinger@gmail.com> 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. >oops, there is a patch for xend to automatically do this, but dont know when the patch gets merged ;-) regards, aq _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David F Barrera
2005-Jul-26 19:26 UTC
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@lists.xensource.com > >http://lists.xensource.com/xen-users > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users
Li Ge
2005-Jul-26 22:14 UTC
Re: [Xen-users] ramdisk option in domU config file does not work
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? Thanks, Li dfbp@us.ltcfwd.li nux.ibm.com Sent by: To xen-users-bounces boris.lenzinger@gmail.com @lists.xensource. cc com Li Ge/Austin/IBM@IBMUS, xen-users@lists.xensource.com Subject 07/26/2005 02:26 Re: [Xen-users] ramdisk option in PM 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 Iused:> > > > # 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@lists.xensource.com > >http://lists.xensource.com/xen-users > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anthony Liguori
2005-Jul-26 22:22 UTC
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@us.ltcfwd.linux.ibm.comdfbp@us.ltcfwd.linux.ibm.com > > > *dfbp@us.ltcfwd.linux.ibm.com* > Sent by: xen-users-bounces@lists.xensource.com > > 07/26/2005 02:26 PM > > > > To > > boris.lenzinger@gmail.com > > cc > > Li Ge/Austin/IBM@IBMUS, xen-users@lists.xensource.com > > 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@lists.xensource.com > > >http://lists.xensource.com/xen-users > > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > 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@lists.xensource.com > http://lists.xensource.com/xen-users > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Li Ge
2005-Jul-26 22:30 UTC
Re: [Xen-users] ramdisk option in domU config file does not work
Dave and I both used the initrd-2.6.12-xenU file which was based on /lib/modules/2.6.12-xenU. Li aliguori@us.ltcfw d.linux.ibm.com Sent by: To xen-users-bounces Li Ge/Austin/IBM@IBMUS @lists.xensource. cc com xen-users-bounces@lists.xensource.c om, dfbp@us.ltcfwd.linux.ibm.com, xen-users@lists.xensource.com, 07/26/2005 05:22 boris.lenzinger@gmail.com PM 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@us.ltcfwd.linux.ibm.comdfbp@us.ltcfwd.linux.ibm.com > > > *dfbp@us.ltcfwd.linux.ibm.com* > Sent by: xen-users-bounces@lists.xensource.com > > 07/26/2005 02:26 PM > > > > To > > boris.lenzinger@gmail.com > > cc > > Li Ge/Austin/IBM@IBMUS, xen-users@lists.xensource.com > > 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@lists.xensource.com > > >http://lists.xensource.com/xen-users > > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > 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@lists.xensource.com > http://lists.xensource.com/xen-users > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Li Ge
2005-Jul-26 22:45 UTC
Re: [Xen-users] ramdisk option in domU config file does not work
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 Li Ge/Austin/IBM@IBM US To Sent by: aliguori@us.ltcfwd.linux.ibm.com xen-users-bounces cc @lists.xensource. xen-users-bounces@lists.xensource.c com om, dfbp@us.ltcfwd.linux.ibm.com, xen-users@lists.xensource.com, boris.lenzinger@gmail.com 07/26/2005 05:30 Subject PM Re: [Xen-users] ramdisk option in domU config file does not work Dave and I both used the initrd-2.6.12-xenU file which was based on /lib/modules/2.6.12-xenU. Li Inactive hide details for aliguori@us.ltcfwd.linux.ibm.com aliguori@us.ltcfwd.linux.ibm.com alig uori @us. ltcf wd.l To inux .ibm Li Ge/Austin/IBM@IBMUS .com cc Sent by: xen-users-bounces@lists.xensource. xen- com, dfbp@us.ltcfwd.linux.ibm.com, user xen-users@lists.xensource.com, s-bo boris.lenzinger@gmail.com unce s@li Subject sts. xens Re: [Xen-users] ramdisk option in ourc domU config file does not work e.co m 07/2 6/20 05 05:2 2 PM 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@us.ltcfwd.linux.ibm.comdfbp@us.ltcfwd.linux.ibm.com > > > *dfbp@us.ltcfwd.linux.ibm.com* > Sent by: xen-users-bounces@lists.xensource.com > > 07/26/2005 02:26 PM > > > > To > > boris.lenzinger@gmail.com > > cc > > Li Ge/Austin/IBM@IBMUS, xen-users@lists.xensource.com > > 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@lists.xensource.com > > >http://lists.xensource.com/xen-users > > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > 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@lists.xensource.com > http://lists.xensource.com/xen-users > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David F Barrera
2005-Jul-27 14:34 UTC
Re: [Xen-users] ramdisk option in domU config file does not work
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@us.ltcfwd.linux.ibm.comdfbpp@us.ltcfwd.linux.ibm.com > > > > > > *dfbp@us.ltcfwd.linux.ibm.com* > > Sent by: xen-users-bounces@lists.xensource.com > > > > 07/26/2005 02:26 PM > > > > > > > > To > > > > boris.lenzinger@gmail.com > > > > cc > > > > Li Ge/Austin/IBM@IBMUS, xen-users@lists.xensource.com > > > > 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@lists.xensource.com > > > >http://lists.xensource.com/xen-users > > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > 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@lists.xensource.com > > http://lists.xensource.com/xen-users > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Xen-users mailing list > >Xen-users@lists.xensource.com > >http://lists.xensource.com/xen-users > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > 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@lists.xensource.com http://lists.xensource.com/xen-users