From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] #10833: fix testing of wic images by testimage
Date: Fri, 17 Mar 2017 15:18:31 +0200 [thread overview]
Message-ID: <cover.1489755821.git.ed.bartosh@linux.intel.com> (raw)
Hi,
It was not possible to test wic images with testimage as this framework configured
guest networking by passing "ip=<host ip>::<guest ip>:<netmask>" to the kernel.
This approach doesn't work for wic images as kernel is run by bootloader and the
kernel command line is defined when image is built.
This patchset implements networking configuration by running commands on guests's
serial console. runqemu script was modified to output IP addresses and netmask to
be able to get these parameters from its output in testimage code.
The following changes since commit 8e9769773fd6d04402581c005bb423530a726457:
meta-yocto-bsp: bump to the latest linux stable kernel for the non-x86 BSPs (2017-03-16 22:12:07 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/oe-core/tap-networking-wic-10833
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/oe-core/tap-networking-wic-10833
Ed Bartosh (4):
runqemu: output network configuration
qemurunner: get network params from runqemu output
qemurunner: configure guest networking
bitbake.conf: add sudo to HOSTTOOLS_NONFATAL
meta/conf/bitbake.conf | 2 +-
meta/lib/oeqa/utils/qemurunner.py | 49 ++++++++++++++++++++++++++++-----------
scripts/runqemu | 4 +++-
3 files changed, 39 insertions(+), 16 deletions(-)
--
Regards,
Ed
next reply other threads:[~2017-03-17 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 13:18 Ed Bartosh [this message]
2017-03-17 13:18 ` [PATCH 1/4] runqemu: output network configuration Ed Bartosh
2017-03-17 13:18 ` [PATCH 2/4] qemurunner: get network params from runqemu output Ed Bartosh
2017-03-17 13:18 ` [PATCH 3/4] qemurunner: configure guest networking Ed Bartosh
2017-03-17 13:18 ` [PATCH 4/4] bitbake.conf: add sudo to HOSTTOOLS_NONFATAL Ed Bartosh
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=cover.1489755821.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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