I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and 3.3.0-rc7 with most recent version I see strange issue I am running two server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am attempting to start Linux install running hvm with 512 memory it crashes domO . I have 512 allocated to domO but free shoes that 343 was assigned after starring two instances. Where is the memory going to. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 28 March 2012 15:19, jacek burghardt <jaceksburghardt@gmail.com> wrote:> I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and > 3.3.0-rc7 with most recent version I see strange issue I am running two > server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am attempting > to start Linux install running hvm with 512 memory it crashes domO . I have > 512 allocated to domO but free shoes that 343 was assigned after starring > two instances. Where is the memory going to.Hey! this seems related to a problem I''ve reported many months ago. http://lists.xen.org/archives/html/xen-users/2011-12/msg00069.html I would like to know how is the state of the fix process, as regard this issue. -- Flavio
Does your xl/xm dmesg state anything about the memory maps being used? I wonder if it is related to the EFI memory bug I''ve run into with the e801 & e820 maps. On Wed, Mar 28, 2012 at 10:11 AM, Flavio <fbcyborg@gmail.com> wrote:> On 28 March 2012 15:19, jacek burghardt <jaceksburghardt@gmail.com> wrote: > > I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and > > 3.3.0-rc7 with most recent version I see strange issue I am running two > > server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am > attempting > > to start Linux install running hvm with 512 memory it crashes domO . I > have > > 512 allocated to domO but free shoes that 343 was assigned after starring > > two instances. Where is the memory going to. > Hey! > > this seems related to a problem I''ve reported many months ago. > http://lists.xen.org/archives/html/xen-users/2011-12/msg00069.html > > I would like to know how is the state of the fix process, as regard this > issue. > > -- > Flavio > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 28 March 2012 16:53, Casey DeLorme <cdelorme@gmail.com> wrote:> > Does your xl/xm dmesg state anything about the memory maps being used? I > wonder if it is related to the EFI memory bug I've run into with the e801 & > e820 maps.Here's my xl dmesg: http://pastebin.com/v2JiDUVX but, as you can see I have 8GB of RAM, and this is the free output: total used free shared buffers cached Mem: 819316 596504 222812 0 71036 290540 -/+ buffers/cache: 234928 584388 but even htop (top) says I have only 800MB of RAM O_O. -- Flavio _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
I use ssh so it dies and system reboots just fine. Xm does not habe any issues allocati.g memory but it no longer being used. What is realy strange that now is taking wrong memory xl was never able to make use of all free memory on number of systems but now it does not check for lack of free memory on dom0 and just takes it before I would get error that there is not enough memory On Mar 28, 2012 8:53 AM, "Casey DeLorme" <cdelorme@gmail.com> wrote:> > Does your xl/xm dmesg state anything about the memory maps being used? I > wonder if it is related to the EFI memory bug I''ve run into with the e801 & > e820 maps. > > On Wed, Mar 28, 2012 at 10:11 AM, Flavio <fbcyborg@gmail.com> wrote: > >> On 28 March 2012 15:19, jacek burghardt <jaceksburghardt@gmail.com> >> wrote: >> > I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and >> > 3.3.0-rc7 with most recent version I see strange issue I am running two >> > server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am >> attempting >> > to start Linux install running hvm with 512 memory it crashes domO . I >> have >> > 512 allocated to domO but free shoes that 343 was assigned after >> starring >> > two instances. Where is the memory going to. >> Hey! >> >> this seems related to a problem I''ve reported many months ago. >> http://lists.xen.org/archives/html/xen-users/2011-12/msg00069.html >> >> I would like to know how is the state of the fix process, as regard this >> issue. >> >> -- >> Flavio >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 28 March 2012 17:27, jacek burghardt <jaceksburghardt@gmail.com> wrote:> I use ssh so it dies and system reboots just fine. Xm does not habe any > issues allocati.g memory but it no longer being used. What is realy strange > that now is taking wrong memory xl was never able to make use of all free > memory on number of systems but now it does not check for lack of free > memory on dom0 and just takes it before I would get error that there is not > enough memory > > On Mar 28, 2012 8:53 AM, "Casey DeLorme" <cdelorme@gmail.com> wrote: >> >> >> Does your xl/xm dmesg state anything about the memory maps being used? I >> wonder if it is related to the EFI memory bug I've run into with the e801 & >> e820 maps. >> >> On Wed, Mar 28, 2012 at 10:11 AM, Flavio <fbcyborg@gmail.com> wrote: >>> >>> On 28 March 2012 15:19, jacek burghardt <jaceksburghardt@gmail.com> >>> wrote: >>> > I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and >>> > 3.3.0-rc7 with most recent version I see strange issue I am running two >>> > server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am >>> > attempting >>> > to start Linux install running hvm with 512 memory it crashes domO . I >>> > have >>> > 512 allocated to domO but free shoes that 343 was assigned after >>> > starring >>> > two instances. Where is the memory going to. >>> Hey! >>> >>> this seems related to a problem I've reported many months ago. >>> http://lists.xen.org/archives/html/xen-users/2011-12/msg00069.html >>> >>> I would like to know how is the state of the fix process, as regard this >>> issue.For instance, it may also happen that if I don't pass the dom0_mem=1024M parameter to the hypervisor in grub.conf, the memory "situation" is like this: total used free shared buffers cached Mem: 6152824 155936 5996888 0 20864 40820 -/+ buffers/cache: 94252 6058572 Swap: 8388604 0 8388604 So, 6GB out of 8GB are available for dom0, instead of 800MB, but this is completely random on every boot. -- Flavio _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
My mistake, not the same problem I had. However, it does sound like a ballooning problem, Dom0 starts with an initial assigned memory from the dom0_mem flag, but it gets smaller over time possibly because ballooning is on by default. With the xm toolstack you can set dom0-min-mem in the xend-config file, but I don''t know how to do this with the xl toolstack, I imagine there is a grub flag for it though. On Wed, Mar 28, 2012 at 11:44 AM, Flavio <fbcyborg@gmail.com> wrote:> On 28 March 2012 17:27, jacek burghardt <jaceksburghardt@gmail.com> wrote: > > I use ssh so it dies and system reboots just fine. Xm does not habe any > > issues allocati.g memory but it no longer being used. What is realy > strange > > that now is taking wrong memory xl was never able to make use of all free > > memory on number of systems but now it does not check for lack of free > > memory on dom0 and just takes it before I would get error that there is > not > > enough memory > > > > On Mar 28, 2012 8:53 AM, "Casey DeLorme" <cdelorme@gmail.com> wrote: > >> > >> > >> Does your xl/xm dmesg state anything about the memory maps being used? > I > >> wonder if it is related to the EFI memory bug I''ve run into with the > e801 & > >> e820 maps. > >> > >> On Wed, Mar 28, 2012 at 10:11 AM, Flavio <fbcyborg@gmail.com> wrote: > >>> > >>> On 28 March 2012 15:19, jacek burghardt <jaceksburghardt@gmail.com> > >>> wrote: > >>> > I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and > >>> > 3.3.0-rc7 with most recent version I see strange issue I am running > two > >>> > server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am > >>> > attempting > >>> > to start Linux install running hvm with 512 memory it crashes domO . > I > >>> > have > >>> > 512 allocated to domO but free shoes that 343 was assigned after > >>> > starring > >>> > two instances. Where is the memory going to. > >>> Hey! > >>> > >>> this seems related to a problem I''ve reported many months ago. > >>> http://lists.xen.org/archives/html/xen-users/2011-12/msg00069.html > >>> > >>> I would like to know how is the state of the fix process, as regard > this > >>> issue. > For instance, it may also happen that if I don''t pass the > dom0_mem=1024M parameter to > the hypervisor in grub.conf, the memory "situation" is like this: > > total used free shared buffers cached > Mem: 6152824 155936 5996888 0 20864 40820 > -/+ buffers/cache: 94252 6058572 > Swap: 8388604 0 8388604 > > So, 6GB out of 8GB are available for dom0, instead of 800MB, but this is > completely random on every boot. > > -- > Flavio >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 28 March 2012 18:25, Casey DeLorme <cdelorme@gmail.com> wrote:> My mistake, not the same problem I had.No problem mate.> > However, it does sound like a ballooning problem,Yes, it is actually (as already mentioned in the discussion I''ve reported few post ago).> Dom0 starts with an > initial assigned memory from the dom0_mem flag, but it gets smaller over > time possibly because ballooning is on by default. > > With the xm toolstack you can set dom0-min-mem in the xend-config file, but > I don''t know how to do this with the xl toolstack, I imagine there is a grub > flag for it though.Yes, but if the following sentence is still verified, I think there is nothing to do now: On 7 December 2011 18:51, Ian Tobin <itobin@tidyhosts.com> wrote:> The memory is all screwed up even on kernel 3.1 and still isn''t fixed!-- Flavio
On Mar 28, 2012 10:35 AM, "Flavio" <fbcyborg@gmail.com> wrote:> On 28 March 2012 18:25, Casey DeLorme <cdelorme@gmail.com> wrote: > > My mistake, not the same problem I had. > No problem mate. > > > > > However, it does sound like a ballooning problem, > Yes, it is actually (as already mentioned in the discussion I''ve reported > few post ago). > > > Dom0 starts with an > > initial assigned memory from the dom0_mem flag, but it gets smaller over > > time possibly because ballooning is on by default. > > > > With the xm toolstack you can set dom0-min-mem in the xend-config file, > but > > I don''t know how to do this with the xl toolstack, I imagine there is a > grub > > flag for it though. > Yes, but if the following sentence is still verified, I think there is > nothing to do now: > > On 7 December 2011 18:51, Ian Tobin <itobin@tidyhosts.com> wrote: > > The memory is all screwed up even on kernel 3.1 and still isn''t fixed! > > -- > Flavio > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Well dom balooning is comented out in xl.conf and is still happening but prior version of xen unstable 4.2 had check before now that gone On Mar 28, 2012 10:35 AM, "Flavio" <fbcyborg@gmail.com> wrote:> > On 28 March 2012 18 > > On 28 March 2012 18:25, Casey DeLorme <cdelorme@gmail.com> wrote: > > My mistake, not the same problem I had. > No problem mate. > > > > > However, it does sound like a ballooning problem, > Yes, it is actually (as already mentioned in the discussion I''ve reported > few post ago). > > > Dom0 starts with an > > initial assigned memory from the dom0_mem flag, but it gets smaller over > > time possibly because ballooning is on by default. > > > > With the xm toolstack you can set dom0-min-mem in the xend-config file, > but > > I don''t know how to do this with the xl toolstack, I imagine there is a > grub > > flag for it though. > Yes, but if the following sentence is still verified, I think there is > nothing to do now: > > On 7 December 2011 18:51, Ian Tobin <itobin@tidyhosts.com> wrote: > > The memory is all screwed up even on kernel 3.1 and still isn''t fixed! > > -- > Flavio > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 28 March 2012 18:38, jacek burghardt <jaceksburghardt@gmail.com> wrote:> Well dom balooning is comented out in xl.conf and is still happening but > prior version of xen unstable 4.2 had check before now that goneYes, it is commented out on my system too. i.e.: #autoballoon=1. But at this point, I don't understand. Should I put dom0_mem=XXM and set autoballon=1 to get it working or what else? Because I have to admit that I make a bit of confusion on such issue. -- Flavio _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Not sure if you have been reviewing these: http://wiki.xen.org/wiki/Xen_Man_Pages http://xenbits.xen.org/docs/unstable/man/xl.1.html According to the documentation, to stop ballooning the xl.conf flag "autoballoon" should be set to 0, and you have to make sure that the /etc/init.d/xencommons is loading and that it loads the xl.conf settings. On Wed, Mar 28, 2012 at 12:58 PM, Flavio <fbcyborg@gmail.com> wrote:> On 28 March 2012 18:38, jacek burghardt <jaceksburghardt@gmail.com> wrote: > > Well dom balooning is comented out in xl.conf and is still happening but > > prior version of xen unstable 4.2 had check before now that gone > Yes, it is commented out on my system too. > i.e.: #autoballoon=1. > But at this point, I don''t understand. Should I put dom0_mem=XXM and > set autoballon=1 to get it working or what else? > Because I have to admit that I make a bit of confusion on such issue. > > -- > Flavio >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 28 March 2012 20:56, Casey DeLorme <cdelorme@gmail.com> wrote:> Not sure if you have been reviewing these: > > http://wiki.xen.org/wiki/Xen_Man_Pages > http://xenbits.xen.org/docs/unstable/man/xl.1.htmlOK! Thanks.> > According to the documentation, to stop ballooning the xl.conf flag > "autoballoon" should be set to 0,Well, I''ve put dom0_mem=1024M and autoballoning=0, but I still have the RAM problem (the system only sees 800MB out of 8000M). But nothing changes with autoballoning=1.> and you have to make sure that the > /etc/init.d/xencommons is loading and that it loads the xl.conf settings.Mmh.... I have only these three files: /etc/init.d/xenconsoled /etc/init.d/xendomains /etc/init.d/xenstored They start as default at every boot. -- Flavio