From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id 086A86BDD2 for ; Mon, 29 Jul 2019 02:12:53 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id x6T2Cqgb005098 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 28 Jul 2019 19:12:52 -0700 (PDT) Received: from [128.224.162.179] (128.224.162.179) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.468.0; Sun, 28 Jul 2019 19:12:51 -0700 To: Alexander Kanavin References: <20190726092342.37231-1-kai.kang@windriver.com> <607380CA-E78F-40F5-A77B-AE5DE1E42E59@gmail.com> From: Kang Kai Message-ID: Date: Mon, 29 Jul 2019 10:11:38 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <607380CA-E78F-40F5-A77B-AE5DE1E42E59@gmail.com> Cc: OE-core Subject: Re: [PATCH] core-image-sato-sdk: test image with 512M memory X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2019 02:12:54 -0000 Content-Type: multipart/alternative; boundary="------------F7800898ECCE31036CA84438" Content-Language: en-US --------------F7800898ECCE31036CA84438 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit On 2019/7/27 下午4:35, Alexander Kanavin wrote: > I think you need to re-generate the image first (it goes to qemuboot > config file). It is already used in ptest images, so it’s good to be > consistent. Thank. It works for testimage with setting QB_MEM. For the other 2 images which has been set QB_MEM are ptest images just as you said (core-image-sato-ptest-fast and core-image-sato-sdk-ptest). But for core-image-sato-sdk, it affects runqemu beyond testiamge. I just wonder is that acceptable? Regards, Kai > > Alex > > On 27 Jul 2019, at 4.35, Kang Kai > wrote: > >> On 2019/7/26 下午6:11, Alexander Kanavin wrote: >>> I think you need to use QB_MEM here. >> >> Used TEST_QEMUPARAMS because I found the following line in >> testimage.bbclass: >> >> # TEST_QEMUPARAMS can be used to pass extra parameters to qemu, e.g. >> "-m 1024" for setting the amount o f ram to 1 GB. >> >> >> And it seems QB_MEM is not used when boot the qemu during testimage. >> >> >>> >>> Also, maybe we should just bump the 256M default? >> >> I hope so. >> >> >> Regards, >> Kai >> >> >>> >>> Alex >>> >>> On Fri, 26 Jul 2019 at 12:24, >> > wrote: >>> >>> From: Kai Kang >> > >>> >>> When run do_testimage for core-image-sato-sdk, it fails to pass test >>> case: >>> >>> | RESULTS - systemd.SystemdBasicTests.test_systemd_failed: >>> FAILED (0.43s) >>> >>> It is OOM issue and daemon rpc.statd is killed: >>> >>> |  [  531.306146] Out of memory: Kill process 193 (rpc.statd) >>> score 200 or sacrifice child >>> >>> Increase the memory of qemu to 512M to avoid such OOM issue. >>> >>> Signed-off-by: Kai Kang >> > >>> --- >>>  meta/recipes-sato/images/core-image-sato-sdk.bb >>> | 1 + >>>  1 file changed, 1 insertion(+) >>> >>> diff --git a/meta/recipes-sato/images/core-image-sato-sdk.bb >>> >>> b/meta/recipes-sato/images/core-image-sato-sdk.bb >>> >>> index d7cc52b52b..f7963d018e 100644 >>> --- a/meta/recipes-sato/images/core-image-sato-sdk.bb >>> >>> +++ b/meta/recipes-sato/images/core-image-sato-sdk.bb >>> >>> @@ -9,3 +9,4 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \ >>> >>>  IMAGE_INSTALL += "kernel-devsrc" >>> >>> +TEST_QEMUPARAMS = "-m 512" >>> -- >>> 2.20.0 >>> >>> -- >>> _______________________________________________ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org >>> >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >>> >> >> -- >> Kai Kang -- Kai Kang --------------F7800898ECCE31036CA84438 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit
On 2019/7/27 下午4:35, Alexander Kanavin wrote:
I think you need to re-generate the image first (it goes to qemuboot config file). It is already used in ptest images, so it’s good to be consistent.

Thank. It works for testimage with setting QB_MEM. For the other 2 images which has been set QB_MEM are ptest images just as you said
(core-image-sato-ptest-fast and core-image-sato-sdk-ptest). But for core-image-sato-sdk, it affects runqemu beyond testiamge. I just wonder
is that acceptable?

Regards,
Kai


Alex

On 27 Jul 2019, at 4.35, Kang Kai <Kai.Kang@windriver.com> wrote:

On 2019/7/26 下午6:11, Alexander Kanavin wrote:
I think you need to use QB_MEM here.

Used TEST_QEMUPARAMS because I found the following line in testimage.bbclass:

# TEST_QEMUPARAMS can be used to pass extra parameters to qemu, e.g. "-m 1024" for setting the amount o f ram to 1 GB.


And it seems QB_MEM is not used when boot the qemu during testimage.



Also, maybe we should just bump the 256M default?

I hope so.


Regards,
Kai



Alex

On Fri, 26 Jul 2019 at 12:24, <kai.kang@windriver.com> wrote:
From: Kai Kang <kai.kang@windriver.com>

When run do_testimage for core-image-sato-sdk, it fails to pass test
case:

| RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED (0.43s)

It is OOM issue and daemon rpc.statd is killed:

|  [  531.306146] Out of memory: Kill process 193 (rpc.statd) score 200 or sacrifice child

Increase the memory of qemu to 512M to avoid such OOM issue.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
 meta/recipes-sato/images/core-image-sato-sdk.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-sato/images/core-image-sato-sdk.bb b/meta/recipes-sato/images/core-image-sato-sdk.bb
index d7cc52b52b..f7963d018e 100644
--- a/meta/recipes-sato/images/core-image-sato-sdk.bb
+++ b/meta/recipes-sato/images/core-image-sato-sdk.bb
@@ -9,3 +9,4 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \

 IMAGE_INSTALL += "kernel-devsrc"

+TEST_QEMUPARAMS = "-m 512"
--
2.20.0

--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
Kai Kang


-- 
Kai Kang
--------------F7800898ECCE31036CA84438--