From: Wei Liu <wei.liu2@citrix.com>
To: Sergej Proskurin <proskurin@sec.in.tum.de>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: ARM: Adjusting guest memory size through xl mem-{set|max} fails
Date: Tue, 18 Jul 2017 12:16:53 +0100 [thread overview]
Message-ID: <20170718111653.pg2o4xn4clqobjlc@citrix.com> (raw)
In-Reply-To: <34585b3b-9984-b1c8-18de-02a27fad899e@sec.in.tum.de>
On Mon, Jul 17, 2017 at 06:19:09PM +0200, Sergej Proskurin wrote:
> Hi Julien,
>
>
> On 07/17/2017 03:53 PM, Julien Grall wrote:
> > (+Wei and Ian)
> >
> > Hi Sergej
> >
> > On 17/07/17 13:04, Sergej Proskurin wrote:
> >> Hi all,
> >>
> >> My setup comprises an ARMv7 (Arndale, Linux kernel v4.11.6) and an ARMv8
> >> (LeMaker HiKey, Linux kernel v4.9.0) development board. On both boards,
> >> I have Xen version 4.10-unstable running with the associated tools to
> >> manage a domu.
> >>
> >> Currently, I am trying to get xl mem-{set|max} to work on both
> >> architectures. Unfortunately, both command invocations fail with the
> >> following message (I remember using xl mem-{set|max} on ARMv7 before
> >> with Xen version 4.7 and 4.8):
> >>
> >> ---
> >> xl: libxl.c:339: libxl_defbool_val: Assertion
> >> `!libxl_defbool_is_default(db)' failed.
> >> Aborted
> >> ---
> >
> > I haven't myself tried to use xl mem-{set|max}. Looking at the assert,
> > you hit because a boolean is not initialized. It would be interesting
> > to know which one.
> >
> > I have CCed the tools maintainers to get more feedback.
> >
Can you provide a backtrace?
$ ulimit -c unlimited
$ xl mem-set
That should generate a coredump, on which you can use gdb to get a
backtrace.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-18 11:46 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 [this message]
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
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=20170718111653.pg2o4xn4clqobjlc@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=proskurin@sec.in.tum.de \
--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).