hi, what is the different between the domU config parameter: [...] extra = "mem=1024" [..] and [...] maxmem="1024" [...] is maxmem only available on 3.0.4 and later? cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
There are really three options. ''extra= "mem=1024"'' tells the kernel inside of the domain that it only has a 1GB of memory. This is really not the way to do this. Instead use memory=1024. "maxmem" tells the hypervisor and the kernel inside of the domain how large it could get. This can be adjusted at any time, but Linux domains don''t use it after boot time. The advantage of using this option is that the Linux inside of the domain sizes its internal tables so it can grow to that size. This means that you can dynamically change the amount of memory available inside of the domain. For example, if you have these options for a domain: memory=1024 maxmem=4096 You will have the kernel boot up with 1GB of memory. At any point you can increase it to, for example, 2 GB with this command: xm mem-set <domain> 2048 The kernel will automagically increase to 2GB of RAM. This is, as you might imagine, extremely cool. Also, you can always size down a domain below its initial RAM usage to free up memory it is not using, which can be handy on busy or complex production servers. On May 15, 2007, at 4:43 AM, Denny Schierz wrote:> hi, > > what is the different between the domU config parameter: > > [...] > extra = "mem=1024" > [..] > > > and > > [...] > maxmem="1024" > [...] > > is maxmem only available on 3.0.4 and later? > > cu denny > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Jayson Vantuyl Systems Architect Engine Yard jvantuyl@engineyard.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi I am using xen-3.0.3,and I try to set "memory" and "maxmem" following your discussion,but it does work as expected Does it only work in xen-3.0.4 and later version,or what should I do ? could you help me Thanks in advance Jayson Vantuyl 写道:> There are really three options. > > > ''extra= "mem=1024"'' tells the kernel inside of the domain that it only > has a 1GB of memory. This is really not the way to do this. Instead > use memory=1024. > > "maxmem" tells the hypervisor and the kernel inside of the domain how > large it could get. This can be adjusted at any time, but Linux > domains don''t use it after boot time. The advantage of using this > option is that the Linux inside of the domain sizes its internal > tables so it can grow to that size. This means that you can > dynamically change the amount of memory available inside of the domain. > > For example, if you have these options for a domain: > > memory=1024 > maxmem=4096 > > You will have the kernel boot up with 1GB of memory. At any point you > can increase it to, for example, 2 GB with this command: > > xm mem-set <domain> 2048 > > The kernel will automagically increase to 2GB of RAM. This is, as you > might imagine, extremely cool. > > Also, you can always size down a domain below its initial RAM usage to > free up memory it is not using, which can be handy on busy or complex > production servers. > > On May 15, 2007, at 4:43 AM, Denny Schierz wrote: > >> hi, >> >> what is the different between the domU config parameter: >> >> [...] >> extra = "mem=1024" >> [..] >> >> >> and >> >> [...] >> maxmem="1024" >> [...] >> >> is maxmem only available on 3.0.4 and later? >> >> cu denny >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> >> http://lists.xensource.com/xen-users > > > > -- > Jayson Vantuyl > Systems Architect > *Engine Yard <http://www.engineyard.com>* > jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com> > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
hi I am sorry for misspelling It does not work in xen-3.0.3 ,I missed the NOT in the last mail Does it work in xen-3.0.4,or what should I do? Thanks tgh 写道:> hi > I am using xen-3.0.3,and I try to set "memory" and "maxmem" following > your discussion,but it does work as expected > Does it only work in xen-3.0.4 and later version,or what should I do ? > > could you help me > Thanks in advance > > > Jayson Vantuyl 写道: >> There are really three options. >> >> >> ''extra= "mem=1024"'' tells the kernel inside of the domain that it >> only has a 1GB of memory. This is really not the way to do this. >> Instead use memory=1024. >> >> "maxmem" tells the hypervisor and the kernel inside of the domain how >> large it could get. This can be adjusted at any time, but Linux >> domains don''t use it after boot time. The advantage of using this >> option is that the Linux inside of the domain sizes its internal >> tables so it can grow to that size. This means that you can >> dynamically change the amount of memory available inside of the domain. >> >> For example, if you have these options for a domain: >> >> memory=1024 >> maxmem=4096 >> >> You will have the kernel boot up with 1GB of memory. At any point you >> can increase it to, for example, 2 GB with this command: >> >> xm mem-set <domain> 2048 >> >> The kernel will automagically increase to 2GB of RAM. This is, as you >> might imagine, extremely cool. >> >> Also, you can always size down a domain below its initial RAM usage >> to free up memory it is not using, which can be handy on busy or >> complex production servers. >> >> On May 15, 2007, at 4:43 AM, Denny Schierz wrote: >> >>> hi, >>> >>> what is the different between the domU config parameter: >>> >>> [...] >>> extra = "mem=1024" >>> [..] >>> >>> >>> and >>> >>> [...] >>> maxmem="1024" >>> [...] >>> >>> is maxmem only available on 3.0.4 and later? >>> >>> cu denny >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> >>> http://lists.xensource.com/xen-users >> >> >> >> -- >> Jayson Vantuyl >> Systems Architect >> *Engine Yard <http://www.engineyard.com>* >> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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
I''m not sure. I use it on 3.0.4-tip. I do not know if it works with earlier versions. On May 15, 2007, at 6:47 PM, tgh wrote:> hi > I am using xen-3.0.3,and I try to set "memory" and "maxmem" > following your discussion,but it does work as expected > Does it only work in xen-3.0.4 and later version,or what should I do ? > > could you help me > Thanks in advance > > > Jayson Vantuyl 写道: >> There are really three options. >> >> >> ''extra= "mem=1024"'' tells the kernel inside of the domain that it >> only has a 1GB of memory. This is really not the way to do this. >> Instead use memory=1024. >> >> "maxmem" tells the hypervisor and the kernel inside of the domain >> how large it could get. This can be adjusted at any time, but >> Linux domains don''t use it after boot time. The advantage of using >> this option is that the Linux inside of the domain sizes its >> internal tables so it can grow to that size. This means that you >> can dynamically change the amount of memory available inside of >> the domain. >> >> For example, if you have these options for a domain: >> >> memory=1024 >> maxmem=4096 >> >> You will have the kernel boot up with 1GB of memory. At any point >> you can increase it to, for example, 2 GB with this command: >> >> xm mem-set <domain> 2048 >> >> The kernel will automagically increase to 2GB of RAM. This is, as >> you might imagine, extremely cool. >> >> Also, you can always size down a domain below its initial RAM >> usage to free up memory it is not using, which can be handy on >> busy or complex production servers. >> >> On May 15, 2007, at 4:43 AM, Denny Schierz wrote: >> >>> hi, >>> >>> what is the different between the domU config parameter: >>> >>> [...] >>> extra = "mem=1024" >>> [..] >>> >>> >>> and >>> >>> [...] >>> maxmem="1024" >>> [...] >>> >>> is maxmem only available on 3.0.4 and later? >>> >>> cu denny >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> >>> http://lists.xensource.com/xen-users >> >> >> >> -- >> Jayson Vantuyl >> Systems Architect >> *Engine Yard <http://www.engineyard.com>* >> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com> >> >> >> --------------------------------------------------------------------- >> --- >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >-- Jayson Vantuyl Systems Architect Engine Yard jvantuyl@engineyard.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Jayson, Jayson Vantuyl schrieb:> There are really three options.> ''extra= "mem=1024"'' tells the kernel inside of the domain that it only > has a 1GB of memory. This is really not the way to do this. Instead > use memory=1024.ok, i discovered it for my self. :-) I knew it already, how could i manage the memory in a cool way, but it seems, that there are some minor differents between 3.0.3 and 3.0.4. I have Xen 3.0.3 running (etch version) and i have to use extra="mem=1024M" do get it working. If you have 3.0.4, so you have to use maxmem="1024" (note the missing >>M<<). Otherwise it wasn''t working for me. cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Denny Schierz > Sent: 16 May 2007 11:38 > To: ''xen-users@lists.xensource.com'' > Subject: Re: [Xen-users] extra = "mem=1024" and maxmem > > Hi Jayson, > > Jayson Vantuyl schrieb: > > There are really three options. > > > ''extra= "mem=1024"'' tells the kernel inside of the domain > that it only > > has a 1GB of memory. This is really not the way to do > this. Instead > > use memory=1024. > > ok, i discovered it for my self. :-) I knew it already, how could i > manage the memory in a cool way, but it seems, that there are > some minor > differents between 3.0.3 and 3.0.4.There''s probably differences in many ways between 3.0.3 and 3.0.4, and how maxmem is dealt with may be different, but the maxmem config option has been in Xen for a VERY long time (long before 3.0.3).> > I have Xen 3.0.3 running (etch version) and i have to use > extra="mem=1024M" do get it working. If you have 3.0.4, so you have to > use maxmem="1024" (note the missing >>M<<). > > Otherwise it wasn''t working for me.Describe what wasn''t working, please. -- Mats> > cu denny > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Denny, You should be able to specify both memory and maxmem (with no extra option) to allow you to change the size of memory on the fly. If you don''t plan to use this, that''s okay. However, I was curious if it wasn''t working. On May 16, 2007, at 4:02 AM, Petersson, Mats wrote:> > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of >> Denny Schierz >> Sent: 16 May 2007 11:38 >> To: ''xen-users@lists.xensource.com'' >> Subject: Re: [Xen-users] extra = "mem=1024" and maxmem >> >> Hi Jayson, >> >> Jayson Vantuyl schrieb: >>> There are really three options. >> >>> ''extra= "mem=1024"'' tells the kernel inside of the domain >> that it only >>> has a 1GB of memory. This is really not the way to do >> this. Instead >>> use memory=1024. >> >> ok, i discovered it for my self. :-) I knew it already, how could i >> manage the memory in a cool way, but it seems, that there are >> some minor >> differents between 3.0.3 and 3.0.4. > > There''s probably differences in many ways between 3.0.3 and 3.0.4, and > how maxmem is dealt with may be different, but the maxmem config > option > has been in Xen for a VERY long time (long before 3.0.3). > >> >> I have Xen 3.0.3 running (etch version) and i have to use >> extra="mem=1024M" do get it working. If you have 3.0.4, so you >> have to >> use maxmem="1024" (note the missing >>M<<). >> >> Otherwise it wasn''t working for me. > > Describe what wasn''t working, please. > > -- > Mats >> >> cu denny >> >> > > > > _______________________________________________ > 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
hi, first: i''m really sorry for my very later answer, but i had a lot of work :-). Petersson, Mats schrieb:>> Otherwise it wasn''t working for me.> Describe what wasn''t working, please.i tried to expand the memory from DOmU on the fly, without need to reboot the guest. actually i have in my setup: memory = 128 maxmem = "512" i can shrink the memory from Dom-0 to get enough free to assign it to the VM. After that i set the memory from Dom-U to the "maxmem" (512MB) and i can see it in xentop, that it was working, but in the Dom-U i see only the 128MB. Only after a reboot the VM get the full 512MB. What is also strange, if i shrink the mem of dom-0 and assign it do Dom-U, "xm info" shows the complete free memory, which i assigned to the guest. Strange, isn''t it? What i want is to expand the memory on the fly, without the needing of a reboot and i swear that it _was_ working with extra = "mem=512M", but now i don''t get it working again :-/ cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi, Denny Schierz schrieb:> What i want is to expand the memory on the fly, without the needing of a > reboot and i swear that it _was_ working with extra = "mem=512M", but > now i don''t get it working again :-/it seems, I''ve got it. No tested both options: memory = 128 extra = "mem=512M" maxmem = "512" now i can reduce or maximize the memory on the fly from Dom-U, but why i have to enable both, i can''t explain myself. cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi
I try to do it in the xen-3.1.0,but it does NOT work,or are there
something I should do?
does it work in the xen-3.1.0?
the config file:
kernel = "/boot/vmlinuz-2.6.16-xenU"
memory = 256
maxmem = 512
name = "dom7"
vcpus = 1
vif = [ '''' ]
disk = [ ''file:/vm/dom7.img,sda1,w'' ]
netmask = "255.255.0.0"
gateway = "192.168.150.1"
hostname = "domp"
ip = "192.168.100.202"
root = "/dev/sda1 ro"
extra = "4"
extra = "mem = 512M"
what should I do?
could you help me
Thanks in advance
Jayson Vantuyl 写道:> I''m not sure.
>
> I use it on 3.0.4-tip. I do not know if it works with earlier versions.
>
> On May 15, 2007, at 6:47 PM, tgh wrote:
>
>> hi
>> I am using xen-3.0.3,and I try to set "memory" and
"maxmem" following
>> your discussion,but it does work as expected
>> Does it only work in xen-3.0.4 and later version,or what should I do ?
>>
>> could you help me
>> Thanks in advance
>>
>>
>> Jayson Vantuyl 写道:
>>> There are really three options.
>>>
>>>
>>> ''extra= "mem=1024"'' tells the kernel
inside of the domain that it
>>> only has a 1GB of memory. This is really not the way to do this.
>>> Instead use memory=1024.
>>>
>>> "maxmem" tells the hypervisor and the kernel inside of
the domain
>>> how large it could get. This can be adjusted at any time, but Linux
>>> domains don''t use it after boot time. The advantage of
using this
>>> option is that the Linux inside of the domain sizes its internal
>>> tables so it can grow to that size. This means that you can
>>> dynamically change the amount of memory available inside of the
domain.
>>>
>>> For example, if you have these options for a domain:
>>>
>>> memory=1024
>>> maxmem=4096
>>>
>>> You will have the kernel boot up with 1GB of memory. At any point
>>> you can increase it to, for example, 2 GB with this command:
>>>
>>> xm mem-set <domain> 2048
>>>
>>> The kernel will automagically increase to 2GB of RAM. This is, as
>>> you might imagine, extremely cool.
>>>
>>> Also, you can always size down a domain below its initial RAM usage
>>> to free up memory it is not using, which can be handy on busy or
>>> complex production servers.
>>>
>>> On May 15, 2007, at 4:43 AM, Denny Schierz wrote:
>>>
>>>> hi,
>>>>
>>>> what is the different between the domU config parameter:
>>>>
>>>> [...]
>>>> extra = "mem=1024"
>>>> [..]
>>>>
>>>>
>>>> and
>>>>
>>>> [...]
>>>> maxmem="1024"
>>>> [...]
>>>>
>>>> is maxmem only available on 3.0.4 and later?
>>>>
>>>> cu denny
>>>>
>>>> _______________________________________________
>>>> Xen-users mailing list
>>>> Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
>>>> http://lists.xensource.com/xen-users
>>>
>>>
>>>
>>> --
>>> Jayson Vantuyl
>>> Systems Architect
>>> *Engine Yard <http://www.engineyard.com>*
>>> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com>
>>>
>>>
>>>
------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
>>> http://lists.xensource.com/xen-users
>>
>
>
>
> --
> Jayson Vantuyl
> Systems Architect
> *Engine Yard <http://www.engineyard.com>*
> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
How much memory are you expecting to use? 512MB? You should really not be using the extra="mem=512M" line, as it shouldn''t be necessary. Also, is 2.6.16-xenU the right version? Shouldn''t it be 2.6.18 for 3.1.0? On Jul 13, 2007, at 2:25 AM, tgh wrote:> hi > I try to do it in the xen-3.1.0,but it does NOT work,or are > there something I should do? > does it work in the xen-3.1.0? > the config file: > kernel = "/boot/vmlinuz-2.6.16-xenU" > memory = 256 > maxmem = 512 > name = "dom7" > vcpus = 1 > vif = [ '''' ] > disk = [ ''file:/vm/dom7.img,sda1,w'' ] > netmask = "255.255.0.0" > gateway = "192.168.150.1" > hostname = "domp" > ip = "192.168.100.202" > root = "/dev/sda1 ro" > extra = "4" > extra = "mem = 512M" > > what should I do? > could you help me > > Thanks in advance > > > > > > Jayson Vantuyl 写道: >> I''m not sure. >> >> I use it on 3.0.4-tip. I do not know if it works with earlier >> versions. >> >> On May 15, 2007, at 6:47 PM, tgh wrote: >> >>> hi >>> I am using xen-3.0.3,and I try to set "memory" and "maxmem" >>> following your discussion,but it does work as expected >>> Does it only work in xen-3.0.4 and later version,or what should I >>> do ? >>> >>> could you help me >>> Thanks in advance >>> >>> >>> Jayson Vantuyl 写道: >>>> There are really three options. >>>> >>>> >>>> ''extra= "mem=1024"'' tells the kernel inside of the domain that >>>> it only has a 1GB of memory. This is really not the way to do >>>> this. Instead use memory=1024. >>>> >>>> "maxmem" tells the hypervisor and the kernel inside of the >>>> domain how large it could get. This can be adjusted at any time, >>>> but Linux domains don''t use it after boot time. The advantage of >>>> using this option is that the Linux inside of the domain sizes >>>> its internal tables so it can grow to that size. This means that >>>> you can dynamically change the amount of memory available inside >>>> of the domain. >>>> >>>> For example, if you have these options for a domain: >>>> >>>> memory=1024 >>>> maxmem=4096 >>>> >>>> You will have the kernel boot up with 1GB of memory. At any >>>> point you can increase it to, for example, 2 GB with this command: >>>> >>>> xm mem-set <domain> 2048 >>>> >>>> The kernel will automagically increase to 2GB of RAM. This is, >>>> as you might imagine, extremely cool. >>>> >>>> Also, you can always size down a domain below its initial RAM >>>> usage to free up memory it is not using, which can be handy on >>>> busy or complex production servers. >>>> >>>> On May 15, 2007, at 4:43 AM, Denny Schierz wrote: >>>> >>>>> hi, >>>>> >>>>> what is the different between the domU config parameter: >>>>> >>>>> [...] >>>>> extra = "mem=1024" >>>>> [..] >>>>> >>>>> >>>>> and >>>>> >>>>> [...] >>>>> maxmem="1024" >>>>> [...] >>>>> >>>>> is maxmem only available on 3.0.4 and later? >>>>> >>>>> cu denny >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xensource.com <mailto:Xen- >>>>> users@lists.xensource.com> >>>>> http://lists.xensource.com/xen-users >>>> >>>> >>>> >>>> -- >>>> Jayson Vantuyl >>>> Systems Architect >>>> *Engine Yard <http://www.engineyard.com>* >>>> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com> >>>> >>>> >>>> ------------------------------------------------------------------- >>>> ----- >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xensource.com <mailto:Xen- >>>> users@lists.xensource.com> >>>> http://lists.xensource.com/xen-users >>> >> >> >> >> -- >> Jayson Vantuyl >> Systems Architect >> *Engine Yard <http://www.engineyard.com>* >> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com> >> >> >> --------------------------------------------------------------------- >> --- >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >-- Jayson Vantuyl Systems Architect Engine Yard jvantuyl@engineyard.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users