From: Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com>
To: qemu-devel@nongnu.org
Cc: philmd@redhat.com, dovgaluk@ispras.ru, pavel.dovgaluk@ispras.ru,
crosa@redhat.com, pbonzini@redhat.com, alex.bennee@linaro.org
Subject: [PATCH 7/9] tests/acceptance: add record/replay test for m68k
Date: Mon, 25 May 2020 14:19:41 +0300 [thread overview]
Message-ID: <159040558183.2615.5681444460877087880.stgit@pasha-ThinkPad-X280> (raw)
In-Reply-To: <159040554265.2615.8993443700754452381.stgit@pasha-ThinkPad-X280>
This patch adds a test for record/replay of the kernel
image boot for m68k platform.
Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
---
tests/acceptance/replay_kernel.py | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/tests/acceptance/replay_kernel.py b/tests/acceptance/replay_kernel.py
index 9931f87bd5..4c786b1565 100644
--- a/tests/acceptance/replay_kernel.py
+++ b/tests/acceptance/replay_kernel.py
@@ -173,3 +173,21 @@ class ReplayKernel(Test):
kernel_command_line = self.KERNEL_COMMON_COMMAND_LINE + 'console=hvc0'
console_pattern = 'Kernel command line: %s' % kernel_command_line
self.run_rr(kernel_path, kernel_command_line, console_pattern)
+
+ def test_m68k_q800(self):
+ """
+ :avocado: tags=arch:m68k
+ :avocado: tags=machine:q800
+ """
+ deb_url = ('https://snapshot.debian.org/archive/debian-ports'
+ '/20191021T083923Z/pool-m68k/main'
+ '/l/linux/kernel-image-5.3.0-1-m68k-di_5.3.7-1_m68k.udeb')
+ deb_hash = '044954bb9be4160a3ce81f8bc1b5e856b75cccd1'
+ deb_path = self.fetch_asset(deb_url, asset_hash=deb_hash)
+ kernel_path = self.extract_from_deb(deb_path,
+ '/boot/vmlinux-5.3.0-1-m68k')
+
+ kernel_command_line = (self.KERNEL_COMMON_COMMAND_LINE +
+ 'console=ttyS0 vga=off')
+ console_pattern = 'No filesystem could mount root'
+ self.run_rr(kernel_path, kernel_command_line, console_pattern)
next prev parent reply other threads:[~2020-05-25 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 11:19 [PATCH 0/9] Record/replay acceptance tests Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 1/9] tests/acceptance: allow console interaction with specific VMs Pavel Dovgalyuk
2020-05-26 20:48 ` Willian Rampazzo
2020-05-25 11:19 ` [PATCH 2/9] tests/acceptance: add base class record/replay kernel tests Pavel Dovgalyuk
2020-05-26 20:46 ` Willian Rampazzo
2020-05-25 11:19 ` [PATCH 3/9] tests/acceptance: add kernel record/replay test for x86_64 Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 4/9] tests/acceptance: add record/replay test for aarch64 Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 5/9] tests/acceptance: add record/replay test for arm Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 6/9] tests/acceptance: add record/replay test for ppc64 Pavel Dovgalyuk
2020-05-25 11:19 ` Pavel Dovgalyuk [this message]
2020-05-25 11:19 ` [PATCH 8/9] tests/acceptance: record/replay tests with advcal images Pavel Dovgalyuk
2020-05-26 19:22 ` Willian Rampazzo
2020-05-25 11:19 ` [PATCH 9/9] tests/acceptance: Linux boot test for record/replay Pavel Dovgalyuk
2020-05-26 19:06 ` Willian Rampazzo
2020-05-26 19:52 ` Willian Rampazzo
2020-05-25 17:03 ` [PATCH 0/9] Record/replay acceptance tests no-reply
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=159040558183.2615.5681444460877087880.stgit@pasha-ThinkPad-X280 \
--to=pavel.dovgaluk@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=dovgaluk@ispras.ru \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).