From: Sergej Proskurin <proskurin@sec.in.tum.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>,
Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: ARM: Adjusting guest memory size through xl mem-{set|max} fails
Date: Wed, 19 Jul 2017 14:16:18 +0200 [thread overview]
Message-ID: <6baeaf82-086a-093f-a45e-53fc84a35320@sec.in.tum.de> (raw)
In-Reply-To: <20170719115737.svdgccvyp4ofdjjk@citrix.com>
On 07/19/2017 01:57 PM, Wei Liu wrote:
> On Wed, Jul 19, 2017 at 01:52:08PM +0200, Sergej Proskurin wrote:
>> ---
>> root@avocet:~# xl list
>> Name ID Mem VCPUs State
>> Time(s)
>> Domain-0 0 1024 6
>> r----- 38.9
>> domu1 1 511 2
>> -b---- 0.3
>> root@avocet:~# xl mem-max 1 550m
>> root@avocet:~# xl mem-set 1 520m
>> libxl: error: libxl_mem.c:272:libxl_set_memory_target: Domain
>> 1:memory_dynamic_max must be less than or equal to memory_static_max
>>
> This is a bit strange. What is the maxmem= in your domain config?
>
> I'm not too sure if you can just use xl mem-max. It's a bit messy in
> that area.
As far as I remember, it was possible before (at least on Xen 4.7 and
4.8). I have not set the maxmem= option in the domain config at all. I
just specify the amount of memory by means of memory=.
>> cannot set domid 1 dynamic max memory to : 520m
>> ---
>>
>> According to the error messages from above, I assume this patch will not
>> fix the issues on ARMv7 yet, right?
>>
> The error you saw on ARMv7 is different from the one above afaict. Not
> sure if my patch would fix ARMv7. I'm not too familiar with the inner
> working of ARM guests.
Alright. Anyway, I will try your patch also on ARMv7; just to be sure.
But I also don't think that it'll fix the issue.
Thanks,
Sergej
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-19 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 12:04 ARM: Adjusting guest memory size through xl mem-{set|max} fails Sergej Proskurin
2017-07-17 13:53 ` Julien Grall
2017-07-17 16:19 ` Sergej Proskurin
2017-07-18 11:16 ` Wei Liu
2017-07-19 9:40 ` Sergej Proskurin
2017-07-19 10:22 ` Wei Liu
2017-07-19 11:52 ` Sergej Proskurin
2017-07-19 11:57 ` Wei Liu
2017-07-19 12:16 ` Sergej Proskurin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6baeaf82-086a-093f-a45e-53fc84a35320@sec.in.tum.de \
--to=proskurin@sec.in.tum.de \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).