Re: [Xen-devel] ARM: Adjusting guest memory size through xl mem-{set|max} fails

[Julien Grall <julien.grall@xxxxxxx>]

(+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.

Cheers,

> The domu is created with the following parameters:
>
> ---
> kernel= "/boot/zImage"
> name = "domu"
> memory = 512
> vcpus = 2
> disk=[ 'phy:/dev/vg0/VG0, xvda,w' ]
> extra = 'console=hvc0 xencons=tty root=/dev/xvda rw'
> ---
>
> My Kernel versions have CONFIG_XEN_BALLOON flag set (see ARMv7 example
> Linux .config below).
>
> ---
> $ cat .config | grep -i XEN
> CONFIG_XEN_DOM0=y
> CONFIG_XEN=y
> CONFIG_XEN_BLKDEV_FRONTEND=y
> CONFIG_XEN_BLKDEV_BACKEND=y
> # CONFIG_XEN_SCSI_FRONTEND is not set
> CONFIG_XEN_NETDEV_FRONTEND=y
> CONFIG_XEN_NETDEV_BACKEND=y
> CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y
> CONFIG_HVC_XEN=y
> CONFIG_HVC_XEN_FRONTEND=y
> # CONFIG_TCG_XEN is not set
> # CONFIG_XEN_WDT is not set
> CONFIG_XEN_FBDEV_FRONTEND=y
> # Xen driver support
> CONFIG_XEN_BALLOON=y
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_DEV_EVTCHN=y
> CONFIG_XEN_BACKEND=y
> CONFIG_XENFS=y
> CONFIG_XEN_COMPAT_XENFS=y
> CONFIG_XEN_SYS_HYPERVISOR=y
> CONFIG_XEN_XENBUS_FRONTEND=y
> CONFIG_XEN_GNTDEV=m
> CONFIG_XEN_GRANT_DEV_ALLOC=m
> CONFIG_SWIOTLB_XEN=y
> CONFIG_XEN_PRIVCMD=y
> CONFIG_XEN_AUTO_XLATE=y
> ---
>
> Besides, I can see in the dmesg output that the balloon driver gets
> initialized:
>
> ---
> # dmesg | grep -i balloon
> [    0.180942] xen:balloon: Initialising balloon driver
> [    0.187103] xen_balloon: Initialising balloon driver
> ---
>
> It would be great if someone would help me to resolve this issue as I am
> obviously missing something. Thank you very much in advance.
>
> Best regards,
> ~Sergej
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> https://lists.xen.org/xen-devel
--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel