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 3/9] tests/acceptance: add kernel record/replay test for x86_64
Date: Mon, 25 May 2020 14:19:19 +0300 [thread overview]
Message-ID: <159040555939.2615.15017741446489098332.stgit@pasha-ThinkPad-X280> (raw)
In-Reply-To: <159040554265.2615.8993443700754452381.stgit@pasha-ThinkPad-X280>
This patch adds a test for record/replay an execution of x86_64 machine.
Execution scenario includes simple kernel boot, which allows testing
basic hardware interaction in RR mode.
Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
---
tests/acceptance/replay_kernel.py | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/tests/acceptance/replay_kernel.py b/tests/acceptance/replay_kernel.py
index 3208179789..00abe1e872 100644
--- a/tests/acceptance/replay_kernel.py
+++ b/tests/acceptance/replay_kernel.py
@@ -78,3 +78,19 @@ class ReplayKernel(Test):
def run_rr(self, kernel_path, kernel_command_line, console_pattern, shift=7, args=()):
self.run_vm(kernel_path, kernel_command_line, console_pattern, True, shift, args)
self.run_vm(kernel_path, kernel_command_line, console_pattern, False, shift, args)
+
+ def test_x86_64_pc(self):
+ """
+ :avocado: tags=arch:x86_64
+ :avocado: tags=machine:pc
+ """
+ kernel_url = ('https://archives.fedoraproject.org/pub/archive/fedora'
+ '/linux/releases/29/Everything/x86_64/os/images/pxeboot'
+ '/vmlinuz')
+ kernel_hash = '23bebd2680757891cf7adedb033532163a792495'
+ kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
+
+ kernel_command_line = self.KERNEL_COMMON_COMMAND_LINE + 'console=ttyS0'
+ console_pattern = 'Kernel command line: %s' % kernel_command_line
+
+ self.run_rr(kernel_path, kernel_command_line, console_pattern)
next prev parent reply other threads:[~2020-05-25 11:20 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 ` Pavel Dovgalyuk [this message]
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 ` [PATCH 7/9] tests/acceptance: add record/replay test for m68k Pavel Dovgalyuk
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=159040555939.2615.15017741446489098332.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).