WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Weird xl mem-set behavior

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Weird xl mem-set behavior
From: Claudiu Curcă <alexstrasza2@xxxxxxxxx>
Date: Thu, 19 May 2011 13:35:43 +0300
Delivery-date: Thu, 19 May 2011 03:37:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=VUztG753XtxqvvGBvOCSdTxYhbZR7nqF7hkKnjf47qQ=; b=jIq/tPQHalFcWWZtt2fz96wK4nt48MmG+kw8qamjUwKXd/canXusce2CNwWOU85glq cJl/NO4/Tn+lXfef7W7Xi6ZqOQZX3vzk7M8aEqGSrcxcSepcEdptk3+HhmtTSxbMYJeW A9o5D815t4JQaZIidxwl11skP/pHGeKO0xxrM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Ao+PwWen3kYMF45498QlnmXuk/RsI11q+YtiyacKcNOcZv0WIDLMCRuO5H3aWYZjPn 5lYm0nqLH2WjbrQIrcPEsjlSY/r/ZG4Sbi7Q0SH2Qw5LbyMX32NgHhalG5IgKALlPmh5 IBwXyYSdzQqsMpFrf81plTQacgenynLxl5mQg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <107833EC-0533-4674-BA61-70366DB740F6@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTi==ytzzNJyk03CMTbqH5QJO0jBViQ@xxxxxxxxxxxxxx> <1C65FCFA-B6E9-4B19-8FF3-C6AB6DD4FACA@xxxxxxxxxxx> <107833EC-0533-4674-BA61-70366DB740F6@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>