All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
	tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v2 2/8] tools: arm: report an error if the guest RAM is too large
Date: Fri, 25 Apr 2014 13:01:55 +0100	[thread overview]
Message-ID: <535A4EB3.1050903@linaro.org> (raw)
In-Reply-To: <1398426699.18537.433.camel@kazak.uk.xensource.com>



On 25/04/14 12:51, Ian Campbell wrote:
> On Fri, 2014-04-25 at 12:50 +0100, Julien Grall wrote:
>> Hi Ian,
>>
>> On 25/04/14 12:22, Ian Campbell wrote:
>>> Due to the layout of the guest physical address space we cannot support more
>>> than 768M of RAM before overrunning the area set aside for the grant table. Due
>>> to the presence of the magic pages at the end of the RAM region guests are
>>> actually limited to 767M.
>>>
>>> Catch this case during domain build and fail gracefully instead of obscurely
>>> later on.
>>>
>>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>>> ---
>>> This is the only patch in this series which I consider to be suitable for
>>> backporting to Xen 4.4
>>
>> I agree with you. Without this the guest can crash with weird error.
> 
> I've found that it just hangs silently, which is even more frustrating.

When I try to create a domain with 800M of RAM I get some error from libxl:
libxl: notice: libxl_numa.c:494:libxl__get_numa_candidate: NUMA placement failed, performance might be affected
libxl: error: libxl_device.c:934:device_backend_callback: unable to add device with path /local/domain/0/backend/vbd/5/51712
libxl: error: libxl_create.c:1062:domcreate_launch_dm: unable to add disk devices
libxl: error: libxl_device.c:934:device_backend_callback: unable to remove device with path /local/domain/0/backend/vbd/5/51712
libxl: error: libxl.c:1470:devices_destroy_cb: libxl__devices_destroy failed for 5


-- 
Julien Grall

  reply	other threads:[~2014-04-25 12:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 11:22 [PATCH v2 0/8] xen: arm: support up to (almost) 1TB of guest RAM Ian Campbell
2014-04-25 11:22 ` [PATCH v2 1/8] tools: libxl: use uint64_t not unsigned long long for addresses Ian Campbell
2014-04-25 11:42   ` Julien Grall
2014-04-30 15:12   ` Ian Jackson
2014-04-30 15:49     ` Ian Campbell
2014-05-02 10:03       ` Ian Campbell
2014-04-25 11:22 ` [PATCH v2 2/8] tools: arm: report an error if the guest RAM is too large Ian Campbell
2014-04-25 11:50   ` Julien Grall
2014-04-25 11:51     ` Ian Campbell
2014-04-25 12:01       ` Julien Grall [this message]
2014-04-25 12:04         ` Ian Campbell
2014-04-25 11:22 ` [PATCH v2 3/8] tools: arm: move magic pfns out of guest RAM region Ian Campbell
2014-04-25 12:09   ` Julien Grall
2014-04-25 12:22     ` Ian Campbell
2014-04-25 13:10       ` Ian Campbell
2014-04-25 11:22 ` [PATCH v2 4/8] tools: arm: rearrange guest physical address space to increase max RAM Ian Campbell
2014-04-25 12:14   ` Julien Grall
2014-04-25 11:22 ` [PATCH v2 5/8] tools: arm: prepare for multiple banks of guest RAM Ian Campbell
2014-04-25 12:19   ` Julien Grall
2014-04-25 12:23     ` Ian Campbell
2014-04-25 12:34       ` Julien Grall
2014-04-25 11:22 ` [PATCH v2 6/8] tools: arm: refactor code to setup guest p2m and fill it with RAM Ian Campbell
2014-04-25 12:51   ` Julien Grall
2014-04-25 12:59     ` Ian Campbell
2014-04-25 13:12       ` Julien Grall
2014-04-25 13:22         ` Ian Campbell
2014-04-25 13:28           ` Julien Grall
2014-04-25 11:22 ` [PATCH v2 7/8] tools: arm: support up to (almost) 1TB of guest RAM Ian Campbell
2014-04-25 13:29   ` Julien Grall
2014-04-25 11:22 ` [PATCH v2 8/8] tools: arm: increase size of region set aside for guest grant table Ian Campbell
2014-04-25 12:59   ` Julien Grall

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=535A4EB3.1050903@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.