[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Weird xl mem-set behavior
Yes, I am. Using the old xm stack works fine, though... xm mem-set 0 <mem> sets the memory just fine... it's xl who's failing. However, the dom0_mem boot parameter still doesn't work properly. On Wed, May 18, 2011 at 11:18 PM, Ian Tobin <itobin@xxxxxxxxxxxxx> wrote: > Hi, > > Same here, are u using grub? > > > Tidyhosts UK - Server & Web Specialists > > W: www.tidyhosts.com > E: Âenquiries@xxxxxxxxxxxxx > T: Â0871 910 6732 > > This email and its attachments are scanned by TidyHosts UK. All emails and > attachments should also be scanned by the recipient. TidyHosts UK accept no > responsibility for any damage caused by any virus attached to this email.  > This email is confidential and is intended only for the addressee(s). > > > > > > > On 18 May 2011, at 16:52, "Iain Kay" <spam@xxxxxxxxxxx> wrote: > >> Hi Claudiu, >> >> Xen 4.1.0 stable from the tar archive running on CentOS 5.6 with Jeremy's >> 2.6.32.x kernel seems rock solid for me. >> >> I boot with dom0_mem=512M and get domain 0 with bang on 512MB of ram >> allocated. >> >> Just tried ammending the line to 1024M and have domain-0 booted with 1024MB >> of ram. >> >>  ÂName                    ÂID  Mem VCPUs   ÂState  >> Time(s) >>  ÂDomain-0                   0 Â1024   2   r-----   >> 15.9 >> >> Iain >> >> On 18 May 2011, at 16:22, Claudiu CurcÄ wrote: >> >>> Hello, >>> >>> I'm struggling to handle the amount of memory that dom0 gets on some system. >>> >>> It's a system with 8GB of RAM, running 2.6.38-6 with pv_ops and Xen 4.1 >>> If I want to set the amount of memory for dom0, I get very bogus >>> results. See here: http://pastebin.com/gRgY9ERN If I use the M >>> notation (xl mem-set 0 4096M) the outcome is similarily unpredictable, >>> and sometimes I get the memory set to something like 200-300MB and in >>> rare cases a kernel panic. >>> >>> Also, if I set the "dom0_mem=X" kernel parameter, the amount of memory >>> Xen gives to dom0 is fairly random... sometimes 2GB, sometimes 6GB, >>> sometimes ~500MB, regrardless of what value I use or the unit I use (M >>> or no unit, for the default KB). >>> >>> Anyone else has experienced this in Xen 4.1? Thanks! >>> >>> _______________________________________________ >>> 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 > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |