From: Xiangyu Chen <xiangyu.chen@eng.windriver.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: [meta-virtualization][PATCH 0/3] small changes on criu and lxc
Date: Sun, 7 Jan 2024 20:56:06 +0800 [thread overview]
Message-ID: <20240107125609.3502113-1-xiangyu.chen@eng.windriver.com> (raw)
From: Xiangyu Chen <xiangyu.chen@windriver.com>
Hi Bruce,
There are 3 small fix on criu and lxc package.
patch 1 and 2 related to criu, when using criu dump, it failed and report errors
due to missing sock diag features in kernel and cgroup not init correctly, so add
kernel configuration fragments to enable sock diag and add crgoup-lite to RDEPENDS.
patch 3 related to lxc ptest, some of test cases cannot fully clean the system environment
after exit, that cause lxc-test-unpriv in failure status, so adjust the lxc-test-unpriv
case order to first.
Thanks,
Br,
Xiangyu
Xiangyu Chen (3):
criu: add kernel configuration features
criu: add cgroup-lite to RDEPENDS
lxc: adjust the lxc-test-unpriv running order
recipes-containers/criu/criu_git.bb | 2 +-
recipes-containers/lxc/files/run-ptest | 25 ++++++++++++++++++-
recipes-kernel/linux/linux-yocto/criu.cfg | 8 ++++++
recipes-kernel/linux/linux-yocto/criu.scc | 4 +++
.../linux/linux-yocto_virtualization.inc | 1 +
5 files changed, 38 insertions(+), 2 deletions(-)
create mode 100644 recipes-kernel/linux/linux-yocto/criu.cfg
create mode 100644 recipes-kernel/linux/linux-yocto/criu.scc
--
2.34.1
next reply other threads:[~2024-01-07 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 12:56 Xiangyu Chen [this message]
2024-01-07 12:56 ` [meta-virtualization][PATCH 1/3] criu: add kernel configuration features Xiangyu Chen
2024-01-07 12:56 ` [meta-virtualization][PATCH 2/3] criu: add cgroup-lite to RDEPENDS Xiangyu Chen
2024-01-07 12:56 ` [meta-virtualization][PATCH 3/3] lxc: adjust the lxc-test-unpriv running order Xiangyu Chen
2024-01-15 21:49 ` [meta-virtualization][PATCH 0/3] small changes on criu and lxc Bruce Ashfield
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=20240107125609.3502113-1-xiangyu.chen@eng.windriver.com \
--to=xiangyu.chen@eng.windriver.com \
--cc=meta-virtualization@lists.yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).