* [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
@ 2018-05-30 18:41 ` Cleber Rosa
2018-05-30 21:19 ` Philippe Mathieu-Daudé
2018-05-31 10:55 ` Stefan Hajnoczi
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 2/5] scripts/qemu.py: allow adding to the list of extra arguments Cleber Rosa
` (5 subsequent siblings)
6 siblings, 2 replies; 19+ messages in thread
From: Cleber Rosa @ 2018-05-30 18:41 UTC (permalink / raw)
To: qemu-devel
Cc: Eduardo Habkost, Philippe Mathieu-Daudé, Stefan Hajnoczi,
Fam Zheng, Amador Pahim, Cleber Rosa
This patch adds the very minimum infrastructure necessary for writing
and running functional/acceptance tests, including:
* Documentation
* The avocado_qemu.Test base test class
* One example tests (version.py)
Additional functionality is expected to be added along the tests that
require them.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
---
docs/devel/testing.rst | 192 ++++++++++++++++++++++
tests/acceptance/README.rst | 10 ++
tests/acceptance/avocado_qemu/__init__.py | 54 ++++++
tests/acceptance/version.py | 24 +++
4 files changed, 280 insertions(+)
create mode 100644 tests/acceptance/README.rst
create mode 100644 tests/acceptance/avocado_qemu/__init__.py
create mode 100644 tests/acceptance/version.py
diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
index 0ca1a2d4b5..6cc04c6d78 100644
--- a/docs/devel/testing.rst
+++ b/docs/devel/testing.rst
@@ -484,3 +484,195 @@ supported. To start the fuzzer, run
Alternatively, some command different from "qemu-img info" can be tested, by
changing the ``-c`` option.
+
+Acceptance tests using the Avocado Framework
+============================================
+
+The ``tests/acceptance`` directory hosts functional tests, also known
+as acceptance level tests. They're usually higher level tests, and
+may interact with external resources and with various guest operating
+systems.
+
+These tests are written using the Avocado Testing Framework (which must
+be installed separately) in conjunction with a the ``avocado_qemu.Test``
+class, implemented at ``tests/acceptance/avocado_qemu``.
+
+Tests based on ``avocado_qemu.Test`` can easily:
+
+ * Customize the command line arguments given to the convenience
+ ``self.vm`` attribute (a QEMUMachine instance)
+
+ * Interact with the QEMU monitor, send QMP commands and check
+ their results
+
+ * Interact with the guest OS, using the convenience console device
+ (which may be useful to assert the effectiveness and correctness of
+ command line arguments or QMP commands)
+
+ * Interact with external data files that accompany the test itself
+ (see ``self.get_data()``)
+
+ * Donwload (and cache) remote data files, such as firmware and kernel
+ images
+
+ * Have access to a library of guest OS images (by means of the
+ ``avocado.utils.vmimage`` library)
+
+ * Make use of various other test related utilities available at the
+ test class itself and at the utility library:
+
+ - http://avocado-framework.readthedocs.io/en/latest/api/test/avocado.html#avocado.Test
+ - http://avocado-framework.readthedocs.io/en/latest/api/utils/avocado.utils.html
+
+Installation
+------------
+
+To install Avocado and its dependencies, run:
+
+.. code::
+
+ pip install --user avocado-framework
+
+Alternatively, follow the instructions on this link:
+
+ http://avocado-framework.readthedocs.io/en/latest/GetStartedGuide.html#installing-avocado
+
+Overview
+--------
+
+This directory provides the ``avocado_qemu`` Python module, containing
+the ``avocado_qemu.Test`` class. Here's a simple usage example:
+
+.. code::
+
+ from avocado_qemu import Test
+
+
+ class Version(Test):
+ """
+ :avocado: enable
+ :avocado: tags=quick
+ """
+ def test_qmp_human_info_version(self):
+ self.vm.launch()
+ res = self.vm.command('human-monitor-command',
+ command_line='info version')
+ self.assertRegexpMatches(res, r'^(\d+\.\d+\.\d)')
+
+To execute your test, run:
+
+.. code::
+
+ avocado run version.py
+
+Tests may be classified according to a convention by using docstring
+directives such as ``:avocado: tags=TAG1,TAG2``. To run all tests
+in the current directory, tagged as "quick", run:
+
+.. code::
+
+ avocado run -t quick .
+
+The ``avocado_qemu.Test`` base test class
+-----------------------------------------
+
+The ``avocado_qemu.Test`` class has a number of characteristics that
+are worth being mentioned right away.
+
+First of all, it attempts to give each test a ready to use QEMUMachine
+instance, available at ``self.vm``. Because many tests will tweak the
+QEMU command line, launching the QEMUMachine (by using ``self.vm.launch()``)
+is left to the test writer.
+
+At test "tear down", ``avocado_qemu.Test`` handles the QEMUMachine
+shutdown.
+
+QEMUMachine
+~~~~~~~~~~~
+
+The QEMUMachine API is already widely used in the Python iotests,
+device-crash-test and other Python scripts. It's a wrapper around the
+execution of a QEMU binary, giving its users:
+
+ * the ability to set command line arguments to be given to the QEMU
+ binary
+
+ * a ready to use QMP connection and interface, which can be used to
+ send commands and inspect its results, as well as asynchronous
+ events
+
+ * convenience methods to set commonly used command line arguments in
+ a more succinct and intuitive way
+
+QEMU binary selection
+~~~~~~~~~~~~~~~~~~~~~
+
+The QEMU binary used for the ``self.vm`` QEMUMachine instance will
+primarily depend on the value of the ``qemu_bin`` parameter. If it's
+not explicitly set, its default value will be the result of a dynamic
+probe in the same source tree. A suitable binary will be one that
+targets the architecture matching host machine.
+
+Based on this description, test writers will usually rely on one of
+the following approaches:
+
+1) Set ``qemu_bin``, and use the given binary
+
+2) Do not set ``qemu_bin``, and use a QEMU binary named like
+ "${arch}-softmmu/qemu-system-${arch}", either in the current
+ working directory, or in the current source tree.
+
+The resulting ``qemu_bin`` value will be preserved in the
+``avocado_qemu.Test`` as an attribute with the same name.
+
+Attribute reference
+-------------------
+
+Besides the attributes and methods that are part of the base
+``avocado.Test`` class, the following attributes are available on any
+``avocado_qemu.Test`` instance.
+
+vm
+~~
+
+A QEMUMachine instance, initially configured according to the given
+``qemu_bin`` parameter.
+
+qemu_bin
+~~~~~~~~
+
+The preserved value of the ``qemu_bin`` parameter or the result of the
+dynamic probe for a QEMU binary in the current working directory or
+source tree.
+
+Parameter reference
+-------------------
+
+To understand how Avocado parameters are accessed by tests, and how
+they can be passed to tests, please refer to::
+
+ http://avocado-framework.readthedocs.io/en/latest/WritingTests.html#accessing-test-parameters
+
+Parameter values can be easily seen in the log files, and will look
+like the following:
+
+.. code::
+
+ PARAMS (key=qemu_bin, path=*, default=x86_64-softmmu/qemu-system-x86_64) => 'x86_64-softmmu/qemu-system-x86_64
+
+qemu_bin
+~~~~~~~~
+
+The exact QEMU binary to be used on QEMUMachine.
+
+Uninstalling Avocado
+--------------------
+
+If you've followed the installation instructions above, you can easily
+uninstall Avocado. Start by listing the packages you have installed::
+
+ pip list --user
+
+And remove any package you want with::
+
+ pip uninstall <package_name>
diff --git a/tests/acceptance/README.rst b/tests/acceptance/README.rst
new file mode 100644
index 0000000000..89260faed6
--- /dev/null
+++ b/tests/acceptance/README.rst
@@ -0,0 +1,10 @@
+============================================
+Acceptance tests using the Avocado Framework
+============================================
+
+This directory contains functional tests, also known as acceptance
+level tests. They're usually higher level, and may interact with
+external resources and with various guest operating systems.
+
+For more information, please refer to ``docs/devel/testing.rst``,
+section "Acceptance tests using the Avocado Framework".
diff --git a/tests/acceptance/avocado_qemu/__init__.py b/tests/acceptance/avocado_qemu/__init__.py
new file mode 100644
index 0000000000..1e54fd5932
--- /dev/null
+++ b/tests/acceptance/avocado_qemu/__init__.py
@@ -0,0 +1,54 @@
+# Test class and utilities for functional tests
+#
+# Copyright (c) 2018 Red Hat, Inc.
+#
+# Author:
+# Cleber Rosa <crosa@redhat.com>
+#
+# This work is licensed under the terms of the GNU GPL, version 2 or
+# later. See the COPYING file in the top-level directory.
+
+import os
+import sys
+
+import avocado
+
+SRC_ROOT_DIR = os.path.dirname(os.path.dirname(os.path.dirname(__file__)))
+SRC_ROOT_DIR = os.path.abspath(os.path.dirname(SRC_ROOT_DIR))
+sys.path.append(os.path.join(SRC_ROOT_DIR, 'scripts'))
+
+from qemu import QEMUMachine
+
+def is_readable_executable_file(path):
+ return os.path.isfile(path) and os.access(path, os.R_OK | os.X_OK)
+
+
+def pick_default_qemu_bin():
+ """
+ Picks the path of a QEMU binary, starting either in the current working
+ directory or in the source tree root directory.
+ """
+ arch = os.uname()[4]
+ qemu_bin_relative_path = os.path.join("%s-softmmu" % arch,
+ "qemu-system-%s" % arch)
+ if is_readable_executable_file(qemu_bin_relative_path):
+ return qemu_bin_relative_path
+
+ qemu_bin_from_src_dir_path = os.path.join(SRC_ROOT_DIR,
+ qemu_bin_relative_path)
+ if is_readable_executable_file(qemu_bin_from_src_dir_path):
+ return qemu_bin_from_src_dir_path
+
+
+class Test(avocado.Test):
+ def setUp(self):
+ self.vm = None
+ self.qemu_bin = self.params.get('qemu_bin',
+ default=pick_default_qemu_bin())
+ if self.qemu_bin is None:
+ self.cancel("No QEMU binary defined or found in the source tree")
+ self.vm = QEMUMachine(self.qemu_bin)
+
+ def tearDown(self):
+ if self.vm is not None:
+ self.vm.shutdown()
diff --git a/tests/acceptance/version.py b/tests/acceptance/version.py
new file mode 100644
index 0000000000..13b0a7440d
--- /dev/null
+++ b/tests/acceptance/version.py
@@ -0,0 +1,24 @@
+# Version check example test
+#
+# Copyright (c) 2018 Red Hat, Inc.
+#
+# Author:
+# Cleber Rosa <crosa@redhat.com>
+#
+# This work is licensed under the terms of the GNU GPL, version 2 or
+# later. See the COPYING file in the top-level directory.
+
+
+from avocado_qemu import Test
+
+
+class Version(Test):
+ """
+ :avocado: enable
+ :avocado: tags=quick
+ """
+ def test_qmp_human_info_version(self):
+ self.vm.launch()
+ res = self.vm.command('human-monitor-command',
+ command_line='info version')
+ self.assertRegexpMatches(res, r'^(\d+\.\d+\.\d)')
--
2.17.0
^ permalink raw reply related [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure Cleber Rosa
@ 2018-05-30 21:19 ` Philippe Mathieu-Daudé
2018-05-31 10:55 ` Stefan Hajnoczi
1 sibling, 0 replies; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-05-30 21:19 UTC (permalink / raw)
To: Cleber Rosa, qemu-devel
Cc: Eduardo Habkost, Stefan Hajnoczi, Fam Zheng, Amador Pahim
Hi Cleber,
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> This patch adds the very minimum infrastructure necessary for writing
> and running functional/acceptance tests, including:
>
> * Documentation
> * The avocado_qemu.Test base test class
> * One example tests (version.py)
>
> Additional functionality is expected to be added along the tests that
> require them.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> ---
> docs/devel/testing.rst | 192 ++++++++++++++++++++++
> tests/acceptance/README.rst | 10 ++
> tests/acceptance/avocado_qemu/__init__.py | 54 ++++++
> tests/acceptance/version.py | 24 +++
> 4 files changed, 280 insertions(+)
> create mode 100644 tests/acceptance/README.rst
> create mode 100644 tests/acceptance/avocado_qemu/__init__.py
> create mode 100644 tests/acceptance/version.py
>
> diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
> index 0ca1a2d4b5..6cc04c6d78 100644
> --- a/docs/devel/testing.rst
> +++ b/docs/devel/testing.rst
> @@ -484,3 +484,195 @@ supported. To start the fuzzer, run
>
> Alternatively, some command different from "qemu-img info" can be tested, by
> changing the ``-c`` option.
> +
> +Acceptance tests using the Avocado Framework
> +============================================
> +
> +The ``tests/acceptance`` directory hosts functional tests, also known
> +as acceptance level tests. They're usually higher level tests, and
> +may interact with external resources and with various guest operating
> +systems.
> +
> +These tests are written using the Avocado Testing Framework (which must
> +be installed separately) in conjunction with a the ``avocado_qemu.Test``
> +class, implemented at ``tests/acceptance/avocado_qemu``.
> +
> +Tests based on ``avocado_qemu.Test`` can easily:
> +
> + * Customize the command line arguments given to the convenience
> + ``self.vm`` attribute (a QEMUMachine instance)
> +
> + * Interact with the QEMU monitor, send QMP commands and check
> + their results
> +
> + * Interact with the guest OS, using the convenience console device
> + (which may be useful to assert the effectiveness and correctness of
> + command line arguments or QMP commands)
> +
> + * Interact with external data files that accompany the test itself
> + (see ``self.get_data()``)
> +
> + * Donwload (and cache) remote data files, such as firmware and kernel
> + images
> +
> + * Have access to a library of guest OS images (by means of the
> + ``avocado.utils.vmimage`` library)
> +
> + * Make use of various other test related utilities available at the
> + test class itself and at the utility library:
> +
> + - http://avocado-framework.readthedocs.io/en/latest/api/test/avocado.html#avocado.Test
> + - http://avocado-framework.readthedocs.io/en/latest/api/utils/avocado.utils.html
> +
> +Installation
> +------------
> +
> +To install Avocado and its dependencies, run:
> +
> +.. code::
> +
> + pip install --user avocado-framework
> +
> +Alternatively, follow the instructions on this link:
> +
> + http://avocado-framework.readthedocs.io/en/latest/GetStartedGuide.html#installing-avocado
> +
> +Overview
> +--------
> +
> +This directory provides the ``avocado_qemu`` Python module, containing
> +the ``avocado_qemu.Test`` class. Here's a simple usage example:
> +
> +.. code::
> +
> + from avocado_qemu import Test
> +
> +
> + class Version(Test):
> + """
> + :avocado: enable
> + :avocado: tags=quick
> + """
> + def test_qmp_human_info_version(self):
> + self.vm.launch()
> + res = self.vm.command('human-monitor-command',
> + command_line='info version')
> + self.assertRegexpMatches(res, r'^(\d+\.\d+\.\d)')
> +
> +To execute your test, run:
> +
> +.. code::
> +
> + avocado run version.py
> +
> +Tests may be classified according to a convention by using docstring
> +directives such as ``:avocado: tags=TAG1,TAG2``. To run all tests
> +in the current directory, tagged as "quick", run:
> +
> +.. code::
> +
> + avocado run -t quick .
> +
> +The ``avocado_qemu.Test`` base test class
> +-----------------------------------------
> +
> +The ``avocado_qemu.Test`` class has a number of characteristics that
> +are worth being mentioned right away.
> +
> +First of all, it attempts to give each test a ready to use QEMUMachine
> +instance, available at ``self.vm``. Because many tests will tweak the
> +QEMU command line, launching the QEMUMachine (by using ``self.vm.launch()``)
> +is left to the test writer.
> +
> +At test "tear down", ``avocado_qemu.Test`` handles the QEMUMachine
> +shutdown.
> +
> +QEMUMachine
> +~~~~~~~~~~~
> +
> +The QEMUMachine API is already widely used in the Python iotests,
> +device-crash-test and other Python scripts. It's a wrapper around the
> +execution of a QEMU binary, giving its users:
> +
> + * the ability to set command line arguments to be given to the QEMU
> + binary
> +
> + * a ready to use QMP connection and interface, which can be used to
> + send commands and inspect its results, as well as asynchronous
> + events
> +
> + * convenience methods to set commonly used command line arguments in
> + a more succinct and intuitive way
> +
> +QEMU binary selection
> +~~~~~~~~~~~~~~~~~~~~~
> +
> +The QEMU binary used for the ``self.vm`` QEMUMachine instance will
> +primarily depend on the value of the ``qemu_bin`` parameter. If it's
> +not explicitly set, its default value will be the result of a dynamic
> +probe in the same source tree. A suitable binary will be one that
> +targets the architecture matching host machine.
> +
> +Based on this description, test writers will usually rely on one of
> +the following approaches:
> +
> +1) Set ``qemu_bin``, and use the given binary
This didn't work well for me. I suppose I didn't understood correctly
the doc and messed in how to set qemu_bin from command line.
Is this possible to set it from command line anyway?
I first tried setting the env var QTEST_QEMU_BINARY like C qtests, but
it didn't work, then I used the QEMU env var like in vm.BaseVM but this
didn't work neither, then I dig with 'git grep' and noticed we can not
set env var.
To understand how Avocado parameters are accessed by tests, and how
they can be passed to tests, please refer to::
http://avocado-framework.readthedocs.io/en/latest/WritingTests.html#accessing-test-parameters
I read this which led me to
http://avocado-framework.readthedocs.io/en/latest/TestParameters.html
I understood I have to use a mux via YAML file ... so I bailed out :P
I just wanted to run:
$ avocado run --param qemu_bin=/tmp/qemu.elf
tests/acceptance/boot_linux_console.py
> +
> +2) Do not set ``qemu_bin``, and use a QEMU binary named like
> + "${arch}-softmmu/qemu-system-${arch}", either in the current
> + working directory, or in the current source tree.
This worked fine.
> +
> +The resulting ``qemu_bin`` value will be preserved in the
> +``avocado_qemu.Test`` as an attribute with the same name.
> +
> +Attribute reference
> +-------------------
> +
> +Besides the attributes and methods that are part of the base
> +``avocado.Test`` class, the following attributes are available on any
> +``avocado_qemu.Test`` instance.
> +
> +vm
> +~~
> +
> +A QEMUMachine instance, initially configured according to the given
> +``qemu_bin`` parameter.
> +
> +qemu_bin
> +~~~~~~~~
> +
> +The preserved value of the ``qemu_bin`` parameter or the result of the
> +dynamic probe for a QEMU binary in the current working directory or
> +source tree.
> +
> +Parameter reference
> +-------------------
> +
> +To understand how Avocado parameters are accessed by tests, and how
> +they can be passed to tests, please refer to::
> +
> + http://avocado-framework.readthedocs.io/en/latest/WritingTests.html#accessing-test-parameters
> +
> +Parameter values can be easily seen in the log files, and will look
> +like the following:
> +
> +.. code::
> +
> + PARAMS (key=qemu_bin, path=*, default=x86_64-softmmu/qemu-system-x86_64) => 'x86_64-softmmu/qemu-system-x86_64
> +
> +qemu_bin
> +~~~~~~~~
> +
> +The exact QEMU binary to be used on QEMUMachine.
> +
> +Uninstalling Avocado
> +--------------------
> +
> +If you've followed the installation instructions above, you can easily
> +uninstall Avocado. Start by listing the packages you have installed::
> +
> + pip list --user
> +
> +And remove any package you want with::
> +
> + pip uninstall <package_name>
> diff --git a/tests/acceptance/README.rst b/tests/acceptance/README.rst
> new file mode 100644
> index 0000000000..89260faed6
> --- /dev/null
> +++ b/tests/acceptance/README.rst
> @@ -0,0 +1,10 @@
> +============================================
> +Acceptance tests using the Avocado Framework
> +============================================
> +
> +This directory contains functional tests, also known as acceptance
> +level tests. They're usually higher level, and may interact with
> +external resources and with various guest operating systems.
> +
> +For more information, please refer to ``docs/devel/testing.rst``,
> +section "Acceptance tests using the Avocado Framework".
> diff --git a/tests/acceptance/avocado_qemu/__init__.py b/tests/acceptance/avocado_qemu/__init__.py
> new file mode 100644
> index 0000000000..1e54fd5932
> --- /dev/null
> +++ b/tests/acceptance/avocado_qemu/__init__.py
> @@ -0,0 +1,54 @@
> +# Test class and utilities for functional tests
> +#
> +# Copyright (c) 2018 Red Hat, Inc.
> +#
> +# Author:
> +# Cleber Rosa <crosa@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or
> +# later. See the COPYING file in the top-level directory.
> +
> +import os
> +import sys
> +
> +import avocado
> +
> +SRC_ROOT_DIR = os.path.dirname(os.path.dirname(os.path.dirname(__file__)))
> +SRC_ROOT_DIR = os.path.abspath(os.path.dirname(SRC_ROOT_DIR))
> +sys.path.append(os.path.join(SRC_ROOT_DIR, 'scripts'))
> +
> +from qemu import QEMUMachine
> +
> +def is_readable_executable_file(path):
> + return os.path.isfile(path) and os.access(path, os.R_OK | os.X_OK)
> +
> +
> +def pick_default_qemu_bin():
> + """
> + Picks the path of a QEMU binary, starting either in the current working
> + directory or in the source tree root directory.
> + """
> + arch = os.uname()[4]
> + qemu_bin_relative_path = os.path.join("%s-softmmu" % arch,
> + "qemu-system-%s" % arch)
> + if is_readable_executable_file(qemu_bin_relative_path):
> + return qemu_bin_relative_path
> +
> + qemu_bin_from_src_dir_path = os.path.join(SRC_ROOT_DIR,
> + qemu_bin_relative_path)
> + if is_readable_executable_file(qemu_bin_from_src_dir_path):
> + return qemu_bin_from_src_dir_path
> +
> +
> +class Test(avocado.Test):
> + def setUp(self):
> + self.vm = None
> + self.qemu_bin = self.params.get('qemu_bin',
> + default=pick_default_qemu_bin())
> + if self.qemu_bin is None:
> + self.cancel("No QEMU binary defined or found in the source tree")
> + self.vm = QEMUMachine(self.qemu_bin)
> +
> + def tearDown(self):
> + if self.vm is not None:
> + self.vm.shutdown()
> diff --git a/tests/acceptance/version.py b/tests/acceptance/version.py
> new file mode 100644
> index 0000000000..13b0a7440d
> --- /dev/null
> +++ b/tests/acceptance/version.py
> @@ -0,0 +1,24 @@
> +# Version check example test
> +#
> +# Copyright (c) 2018 Red Hat, Inc.
> +#
> +# Author:
> +# Cleber Rosa <crosa@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or
> +# later. See the COPYING file in the top-level directory.
> +
> +
> +from avocado_qemu import Test
> +
> +
> +class Version(Test):
> + """
> + :avocado: enable
> + :avocado: tags=quick
> + """
> + def test_qmp_human_info_version(self):
> + self.vm.launch()
> + res = self.vm.command('human-monitor-command',
> + command_line='info version')
> + self.assertRegexpMatches(res, r'^(\d+\.\d+\.\d)')
>
Good example test :) Tiny and effective.
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Regards,
Phil.
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure Cleber Rosa
2018-05-30 21:19 ` Philippe Mathieu-Daudé
@ 2018-05-31 10:55 ` Stefan Hajnoczi
1 sibling, 0 replies; 19+ messages in thread
From: Stefan Hajnoczi @ 2018-05-31 10:55 UTC (permalink / raw)
To: Cleber Rosa
Cc: qemu-devel, Eduardo Habkost, Philippe Mathieu-Daudé,
Fam Zheng, Amador Pahim
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
On Wed, May 30, 2018 at 02:41:52PM -0400, Cleber Rosa wrote:
> + * Donwload (and cache) remote data files, such as firmware and kernel
s/Donwload/Download/
Aside from that:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [PATCH v4 2/5] scripts/qemu.py: allow adding to the list of extra arguments
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure Cleber Rosa
@ 2018-05-30 18:41 ` Cleber Rosa
2018-05-30 21:20 ` Philippe Mathieu-Daudé
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 3/5] Acceptance tests: add quick VNC tests Cleber Rosa
` (4 subsequent siblings)
6 siblings, 1 reply; 19+ messages in thread
From: Cleber Rosa @ 2018-05-30 18:41 UTC (permalink / raw)
To: qemu-devel
Cc: Eduardo Habkost, Philippe Mathieu-Daudé, Stefan Hajnoczi,
Fam Zheng, Amador Pahim, Cleber Rosa
Tests will often need to add extra arguments to QEMU command
line arguments.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
---
scripts/qemu.py | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/qemu.py b/scripts/qemu.py
index 08a3e9af5a..7cd8193df8 100644
--- a/scripts/qemu.py
+++ b/scripts/qemu.py
@@ -359,3 +359,9 @@ class QEMUMachine(object):
of the qemu process.
'''
return self._iolog
+
+ def add_args(self, *args):
+ '''
+ Adds to the list of extra arguments to be given to the QEMU binary
+ '''
+ self._args.extend(args)
--
2.17.0
^ permalink raw reply related [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 2/5] scripts/qemu.py: allow adding to the list of extra arguments
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 2/5] scripts/qemu.py: allow adding to the list of extra arguments Cleber Rosa
@ 2018-05-30 21:20 ` Philippe Mathieu-Daudé
0 siblings, 0 replies; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-05-30 21:20 UTC (permalink / raw)
To: Cleber Rosa, qemu-devel
Cc: Eduardo Habkost, Stefan Hajnoczi, Fam Zheng, Amador Pahim
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> Tests will often need to add extra arguments to QEMU command
> line arguments.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> scripts/qemu.py | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/scripts/qemu.py b/scripts/qemu.py
> index 08a3e9af5a..7cd8193df8 100644
> --- a/scripts/qemu.py
> +++ b/scripts/qemu.py
> @@ -359,3 +359,9 @@ class QEMUMachine(object):
> of the qemu process.
> '''
> return self._iolog
> +
> + def add_args(self, *args):
> + '''
> + Adds to the list of extra arguments to be given to the QEMU binary
> + '''
> + self._args.extend(args)
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [PATCH v4 3/5] Acceptance tests: add quick VNC tests
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 1/5] Add functional/acceptance tests infrastructure Cleber Rosa
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 2/5] scripts/qemu.py: allow adding to the list of extra arguments Cleber Rosa
@ 2018-05-30 18:41 ` Cleber Rosa
2018-05-30 21:21 ` Philippe Mathieu-Daudé
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method Cleber Rosa
` (3 subsequent siblings)
6 siblings, 1 reply; 19+ messages in thread
From: Cleber Rosa @ 2018-05-30 18:41 UTC (permalink / raw)
To: qemu-devel
Cc: Eduardo Habkost, Philippe Mathieu-Daudé, Stefan Hajnoczi,
Fam Zheng, Amador Pahim, Cleber Rosa
This patch adds a few simple behavior tests for VNC.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
---
tests/acceptance/vnc.py | 60 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 60 insertions(+)
create mode 100644 tests/acceptance/vnc.py
diff --git a/tests/acceptance/vnc.py b/tests/acceptance/vnc.py
new file mode 100644
index 0000000000..b1ef9d71b1
--- /dev/null
+++ b/tests/acceptance/vnc.py
@@ -0,0 +1,60 @@
+# Simple functional tests for VNC functionality
+#
+# Copyright (c) 2018 Red Hat, Inc.
+#
+# Author:
+# Cleber Rosa <crosa@redhat.com>
+#
+# This work is licensed under the terms of the GNU GPL, version 2 or
+# later. See the COPYING file in the top-level directory.
+
+from avocado_qemu import Test
+
+
+class Vnc(Test):
+ """
+ :avocado: enable
+ :avocado: tags=vnc,quick
+ """
+ def test_no_vnc(self):
+ self.vm.add_args('-nodefaults', '-S')
+ self.vm.launch()
+ self.assertFalse(self.vm.qmp('query-vnc')['return']['enabled'])
+
+ def test_no_vnc_change_password(self):
+ self.vm.add_args('-nodefaults', '-S')
+ self.vm.launch()
+ self.assertFalse(self.vm.qmp('query-vnc')['return']['enabled'])
+ set_password_response = self.vm.qmp('change',
+ device='vnc',
+ target='password',
+ arg='new_password')
+ self.assertIn('error', set_password_response)
+ self.assertEqual(set_password_response['error']['class'],
+ 'GenericError')
+ self.assertEqual(set_password_response['error']['desc'],
+ 'Could not set password')
+
+ def test_vnc_change_password_requires_a_password(self):
+ self.vm.add_args('-nodefaults', '-S', '-vnc', ':0')
+ self.vm.launch()
+ self.assertTrue(self.vm.qmp('query-vnc')['return']['enabled'])
+ set_password_response = self.vm.qmp('change',
+ device='vnc',
+ target='password',
+ arg='new_password')
+ self.assertIn('error', set_password_response)
+ self.assertEqual(set_password_response['error']['class'],
+ 'GenericError')
+ self.assertEqual(set_password_response['error']['desc'],
+ 'Could not set password')
+
+ def test_vnc_change_password(self):
+ self.vm.add_args('-nodefaults', '-S', '-vnc', ':0,password')
+ self.vm.launch()
+ self.assertTrue(self.vm.qmp('query-vnc')['return']['enabled'])
+ set_password_response = self.vm.qmp('change',
+ device='vnc',
+ target='password',
+ arg='new_password')
+ self.assertEqual(set_password_response['return'], {})
--
2.17.0
^ permalink raw reply related [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 3/5] Acceptance tests: add quick VNC tests
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 3/5] Acceptance tests: add quick VNC tests Cleber Rosa
@ 2018-05-30 21:21 ` Philippe Mathieu-Daudé
0 siblings, 0 replies; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-05-30 21:21 UTC (permalink / raw)
To: Cleber Rosa, qemu-devel
Cc: Eduardo Habkost, Stefan Hajnoczi, Fam Zheng, Amador Pahim
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> This patch adds a few simple behavior tests for VNC.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> tests/acceptance/vnc.py | 60 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 tests/acceptance/vnc.py
>
> diff --git a/tests/acceptance/vnc.py b/tests/acceptance/vnc.py
> new file mode 100644
> index 0000000000..b1ef9d71b1
> --- /dev/null
> +++ b/tests/acceptance/vnc.py
> @@ -0,0 +1,60 @@
> +# Simple functional tests for VNC functionality
> +#
> +# Copyright (c) 2018 Red Hat, Inc.
> +#
> +# Author:
> +# Cleber Rosa <crosa@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or
> +# later. See the COPYING file in the top-level directory.
> +
> +from avocado_qemu import Test
> +
> +
> +class Vnc(Test):
> + """
> + :avocado: enable
> + :avocado: tags=vnc,quick
> + """
> + def test_no_vnc(self):
> + self.vm.add_args('-nodefaults', '-S')
> + self.vm.launch()
> + self.assertFalse(self.vm.qmp('query-vnc')['return']['enabled'])
> +
> + def test_no_vnc_change_password(self):
> + self.vm.add_args('-nodefaults', '-S')
> + self.vm.launch()
> + self.assertFalse(self.vm.qmp('query-vnc')['return']['enabled'])
> + set_password_response = self.vm.qmp('change',
> + device='vnc',
> + target='password',
> + arg='new_password')
> + self.assertIn('error', set_password_response)
> + self.assertEqual(set_password_response['error']['class'],
> + 'GenericError')
> + self.assertEqual(set_password_response['error']['desc'],
> + 'Could not set password')
> +
> + def test_vnc_change_password_requires_a_password(self):
> + self.vm.add_args('-nodefaults', '-S', '-vnc', ':0')
> + self.vm.launch()
> + self.assertTrue(self.vm.qmp('query-vnc')['return']['enabled'])
> + set_password_response = self.vm.qmp('change',
> + device='vnc',
> + target='password',
> + arg='new_password')
> + self.assertIn('error', set_password_response)
> + self.assertEqual(set_password_response['error']['class'],
> + 'GenericError')
> + self.assertEqual(set_password_response['error']['desc'],
> + 'Could not set password')
> +
> + def test_vnc_change_password(self):
> + self.vm.add_args('-nodefaults', '-S', '-vnc', ':0,password')
> + self.vm.launch()
> + self.assertTrue(self.vm.qmp('query-vnc')['return']['enabled'])
> + set_password_response = self.vm.qmp('change',
> + device='vnc',
> + target='password',
> + arg='new_password')
> + self.assertEqual(set_password_response['return'], {})
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
` (2 preceding siblings ...)
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 3/5] Acceptance tests: add quick VNC tests Cleber Rosa
@ 2018-05-30 18:41 ` Cleber Rosa
2018-05-30 21:22 ` Philippe Mathieu-Daudé
2018-05-31 10:55 ` Stefan Hajnoczi
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test Cleber Rosa
` (2 subsequent siblings)
6 siblings, 2 replies; 19+ messages in thread
From: Cleber Rosa @ 2018-05-30 18:41 UTC (permalink / raw)
To: qemu-devel
Cc: Eduardo Habkost, Philippe Mathieu-Daudé, Stefan Hajnoczi,
Fam Zheng, Amador Pahim, Cleber Rosa
The set_console() method is intended to ease higher level use cases
that require a console device.
The amount of intelligence is limited on purpose, requiring either the
device type explicitly, or the existence of a machine (pattern)
definition.
Because of the console device type selection criteria (by machine
type), users should also be able to define that. It'll then be used
for both '-machine' and for the console device type selection.
Users of the set_console() method will certainly be interested in
accessing the console device, and for that a console_socket property
has been added.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
---
scripts/qemu.py | 97 ++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 96 insertions(+), 1 deletion(-)
diff --git a/scripts/qemu.py b/scripts/qemu.py
index 7cd8193df8..f099ce7278 100644
--- a/scripts/qemu.py
+++ b/scripts/qemu.py
@@ -17,19 +17,41 @@ import logging
import os
import subprocess
import qmp.qmp
+import re
import shutil
+import socket
import tempfile
LOG = logging.getLogger(__name__)
+#: Maps machine types to the preferred console device types
+CONSOLE_DEV_TYPES = {
+ r'^clipper$': 'isa-serial',
+ r'^malta': 'isa-serial',
+ r'^(pc.*|q35.*|isapc)$': 'isa-serial',
+ r'^(40p|powernv|prep)$': 'isa-serial',
+ r'^pseries.*': 'spapr-vty',
+ r'^s390-ccw-virtio.*': 'sclpconsole',
+ }
+
+
class QEMUMachineError(Exception):
"""
Exception called when an error in QEMUMachine happens.
"""
+class QEMUMachineAddDeviceError(QEMUMachineError):
+ """
+ Exception raised when a request to add a device can not be fulfilled
+
+ The failures are caused by limitations, lack of information or conflicting
+ requests on the QEMUMachine methods. This exception does not represent
+ failures reported by the QEMU binary itself.
+ """
+
class MonitorResponseError(qmp.qmp.QMPError):
'''
Represents erroneous QMP monitor reply
@@ -91,6 +113,10 @@ class QEMUMachine(object):
self._test_dir = test_dir
self._temp_dir = None
self._launched = False
+ self._machine = None
+ self._console_device_type = None
+ self._console_address = None
+ self._console_socket = None
# just in case logging wasn't configured by the main script:
logging.basicConfig()
@@ -175,9 +201,19 @@ class QEMUMachine(object):
self._monitor_address[1])
else:
moncdev = 'socket,id=mon,path=%s' % self._vm_monitor
- return ['-chardev', moncdev,
+ args = ['-chardev', moncdev,
'-mon', 'chardev=mon,mode=control',
'-display', 'none', '-vga', 'none']
+ if self._machine is not None:
+ args.extend(['-machine', self._machine])
+ if self._console_device_type is not None:
+ self._console_address = os.path.join(self._temp_dir,
+ self._name + "-console.sock")
+ chardev = ('socket,id=console,path=%s,server,nowait' %
+ self._console_address)
+ device = '%s,chardev=console' % self._console_device_type
+ args.extend(['-chardev', chardev, '-device', device])
+ return args
def _pre_launch(self):
self._temp_dir = tempfile.mkdtemp(dir=self._test_dir)
@@ -202,6 +238,10 @@ class QEMUMachine(object):
self._qemu_log_path = None
+ if self._console_socket is not None:
+ self._console_socket.close()
+ self._console_socket = None
+
if self._temp_dir is not None:
shutil.rmtree(self._temp_dir)
self._temp_dir = None
@@ -365,3 +405,58 @@ class QEMUMachine(object):
Adds to the list of extra arguments to be given to the QEMU binary
'''
self._args.extend(args)
+
+ def set_machine(self, machine_type):
+ '''
+ Sets the machine type
+
+ If set, the machine type will be added to the base arguments
+ of the resulting QEMU command line.
+ '''
+ self._machine = machine_type
+
+ def set_console(self, device_type=None):
+ '''
+ Sets the device type for a console device
+
+ If set, the console device and a backing character device will
+ be added to the base arguments of the resulting QEMU command
+ line.
+
+ This is a convenience method that will either use the provided
+ device type, of if not given, it will used the device type set
+ on CONSOLE_DEV_TYPES.
+
+ The actual setting of command line arguments will be be done at
+ machine launch time, as it depends on the temporary directory
+ to be created.
+
+ @param device_type: the device type, such as "isa-serial"
+ @raises: QEMUMachineAddDeviceError if the device type is not given
+ and can not be determined.
+ '''
+ if device_type is None:
+ if self._machine is None:
+ raise QEMUMachineAddDeviceError("Can not add a console device:"
+ " QEMU instance without a "
+ "defined machine type")
+ for regex, device in CONSOLE_DEV_TYPES.items():
+ if re.match(regex, self._machine):
+ device_type = device
+ break
+ if device_type is None:
+ raise QEMUMachineAddDeviceError("Can not add a console device:"
+ " no matching console device "
+ "type definition")
+ self._console_device_type = device_type
+
+ @property
+ def console_socket(self):
+ """
+ Returns a socket connected to the console
+ """
+ if self._console_socket is None:
+ self._console_socket = socket.socket(socket.AF_UNIX,
+ socket.SOCK_STREAM)
+ self._console_socket.connect(self._console_address)
+ return self._console_socket
--
2.17.0
^ permalink raw reply related [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method Cleber Rosa
@ 2018-05-30 21:22 ` Philippe Mathieu-Daudé
2018-05-31 10:55 ` Stefan Hajnoczi
1 sibling, 0 replies; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-05-30 21:22 UTC (permalink / raw)
To: Cleber Rosa, qemu-devel
Cc: Eduardo Habkost, Stefan Hajnoczi, Fam Zheng, Amador Pahim
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> The set_console() method is intended to ease higher level use cases
> that require a console device.
>
> The amount of intelligence is limited on purpose, requiring either the
> device type explicitly, or the existence of a machine (pattern)
> definition.
>
> Because of the console device type selection criteria (by machine
> type), users should also be able to define that. It'll then be used
> for both '-machine' and for the console device type selection.
>
> Users of the set_console() method will certainly be interested in
> accessing the console device, and for that a console_socket property
> has been added.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> scripts/qemu.py | 97 ++++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 96 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/qemu.py b/scripts/qemu.py
> index 7cd8193df8..f099ce7278 100644
> --- a/scripts/qemu.py
> +++ b/scripts/qemu.py
> @@ -17,19 +17,41 @@ import logging
> import os
> import subprocess
> import qmp.qmp
> +import re
> import shutil
> +import socket
> import tempfile
>
>
> LOG = logging.getLogger(__name__)
>
>
> +#: Maps machine types to the preferred console device types
> +CONSOLE_DEV_TYPES = {
> + r'^clipper$': 'isa-serial',
> + r'^malta': 'isa-serial',
> + r'^(pc.*|q35.*|isapc)$': 'isa-serial',
> + r'^(40p|powernv|prep)$': 'isa-serial',
> + r'^pseries.*': 'spapr-vty',
> + r'^s390-ccw-virtio.*': 'sclpconsole',
> + }
> +
> +
> class QEMUMachineError(Exception):
> """
> Exception called when an error in QEMUMachine happens.
> """
>
>
> +class QEMUMachineAddDeviceError(QEMUMachineError):
> + """
> + Exception raised when a request to add a device can not be fulfilled
> +
> + The failures are caused by limitations, lack of information or conflicting
> + requests on the QEMUMachine methods. This exception does not represent
> + failures reported by the QEMU binary itself.
> + """
> +
> class MonitorResponseError(qmp.qmp.QMPError):
> '''
> Represents erroneous QMP monitor reply
> @@ -91,6 +113,10 @@ class QEMUMachine(object):
> self._test_dir = test_dir
> self._temp_dir = None
> self._launched = False
> + self._machine = None
> + self._console_device_type = None
> + self._console_address = None
> + self._console_socket = None
>
> # just in case logging wasn't configured by the main script:
> logging.basicConfig()
> @@ -175,9 +201,19 @@ class QEMUMachine(object):
> self._monitor_address[1])
> else:
> moncdev = 'socket,id=mon,path=%s' % self._vm_monitor
> - return ['-chardev', moncdev,
> + args = ['-chardev', moncdev,
> '-mon', 'chardev=mon,mode=control',
> '-display', 'none', '-vga', 'none']
> + if self._machine is not None:
> + args.extend(['-machine', self._machine])
> + if self._console_device_type is not None:
> + self._console_address = os.path.join(self._temp_dir,
> + self._name + "-console.sock")
> + chardev = ('socket,id=console,path=%s,server,nowait' %
> + self._console_address)
> + device = '%s,chardev=console' % self._console_device_type
> + args.extend(['-chardev', chardev, '-device', device])
> + return args
>
> def _pre_launch(self):
> self._temp_dir = tempfile.mkdtemp(dir=self._test_dir)
> @@ -202,6 +238,10 @@ class QEMUMachine(object):
>
> self._qemu_log_path = None
>
> + if self._console_socket is not None:
> + self._console_socket.close()
> + self._console_socket = None
> +
> if self._temp_dir is not None:
> shutil.rmtree(self._temp_dir)
> self._temp_dir = None
> @@ -365,3 +405,58 @@ class QEMUMachine(object):
> Adds to the list of extra arguments to be given to the QEMU binary
> '''
> self._args.extend(args)
> +
> + def set_machine(self, machine_type):
> + '''
> + Sets the machine type
> +
> + If set, the machine type will be added to the base arguments
> + of the resulting QEMU command line.
> + '''
> + self._machine = machine_type
> +
> + def set_console(self, device_type=None):
> + '''
> + Sets the device type for a console device
> +
> + If set, the console device and a backing character device will
> + be added to the base arguments of the resulting QEMU command
> + line.
> +
> + This is a convenience method that will either use the provided
> + device type, of if not given, it will used the device type set
> + on CONSOLE_DEV_TYPES.
> +
> + The actual setting of command line arguments will be be done at
> + machine launch time, as it depends on the temporary directory
> + to be created.
> +
> + @param device_type: the device type, such as "isa-serial"
> + @raises: QEMUMachineAddDeviceError if the device type is not given
> + and can not be determined.
> + '''
> + if device_type is None:
> + if self._machine is None:
> + raise QEMUMachineAddDeviceError("Can not add a console device:"
> + " QEMU instance without a "
> + "defined machine type")
> + for regex, device in CONSOLE_DEV_TYPES.items():
> + if re.match(regex, self._machine):
> + device_type = device
> + break
> + if device_type is None:
> + raise QEMUMachineAddDeviceError("Can not add a console device:"
> + " no matching console device "
> + "type definition")
> + self._console_device_type = device_type
> +
> + @property
> + def console_socket(self):
> + """
> + Returns a socket connected to the console
> + """
> + if self._console_socket is None:
> + self._console_socket = socket.socket(socket.AF_UNIX,
> + socket.SOCK_STREAM)
> + self._console_socket.connect(self._console_address)
> + return self._console_socket
>
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method Cleber Rosa
2018-05-30 21:22 ` Philippe Mathieu-Daudé
@ 2018-05-31 10:55 ` Stefan Hajnoczi
1 sibling, 0 replies; 19+ messages in thread
From: Stefan Hajnoczi @ 2018-05-31 10:55 UTC (permalink / raw)
To: Cleber Rosa
Cc: qemu-devel, Eduardo Habkost, Philippe Mathieu-Daudé,
Fam Zheng, Amador Pahim
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Wed, May 30, 2018 at 02:41:55PM -0400, Cleber Rosa wrote:
> The set_console() method is intended to ease higher level use cases
> that require a console device.
>
> The amount of intelligence is limited on purpose, requiring either the
> device type explicitly, or the existence of a machine (pattern)
> definition.
>
> Because of the console device type selection criteria (by machine
> type), users should also be able to define that. It'll then be used
> for both '-machine' and for the console device type selection.
>
> Users of the set_console() method will certainly be interested in
> accessing the console device, and for that a console_socket property
> has been added.
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> ---
> scripts/qemu.py | 97 ++++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 96 insertions(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
` (3 preceding siblings ...)
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 4/5] scripts/qemu.py: introduce set_console() method Cleber Rosa
@ 2018-05-30 18:41 ` Cleber Rosa
2018-05-30 20:57 ` Philippe Mathieu-Daudé
2018-05-31 10:56 ` Stefan Hajnoczi
2018-06-05 14:49 ` [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Philippe Mathieu-Daudé
2018-06-13 18:29 ` Eduardo Habkost
6 siblings, 2 replies; 19+ messages in thread
From: Cleber Rosa @ 2018-05-30 18:41 UTC (permalink / raw)
To: qemu-devel
Cc: Eduardo Habkost, Philippe Mathieu-Daudé, Stefan Hajnoczi,
Fam Zheng, Amador Pahim, Cleber Rosa
This test boots a Linux kernel, and checks that the given command
line was effective in two ways:
* It makes the kernel use the set "console device" as a console
* The kernel records the command line as expected in the console
Given that way too many error conditions may occur, and detecting the
kernel boot progress status may not be trivial, this test relies on a
timeout to handle unexpected situations. Also, it's *not* tagged as a
quick test for obvious reasons.
It may be useful, while interactively running/debugging this test, or
tests similar to this one, to show some of the logging channels.
Example:
$ avocado --show=QMP,console run boot_linux_console.py
Signed-off-by: Cleber Rosa <crosa@redhat.com>
---
tests/acceptance/boot_linux_console.py | 47 ++++++++++++++++++++++++++
1 file changed, 47 insertions(+)
create mode 100644 tests/acceptance/boot_linux_console.py
diff --git a/tests/acceptance/boot_linux_console.py b/tests/acceptance/boot_linux_console.py
new file mode 100644
index 0000000000..98324f7591
--- /dev/null
+++ b/tests/acceptance/boot_linux_console.py
@@ -0,0 +1,47 @@
+# Functional test that boots a Linux kernel and checks the console
+#
+# Copyright (c) 2018 Red Hat, Inc.
+#
+# Author:
+# Cleber Rosa <crosa@redhat.com>
+#
+# This work is licensed under the terms of the GNU GPL, version 2 or
+# later. See the COPYING file in the top-level directory.
+
+import logging
+
+from avocado_qemu import Test
+
+
+class BootLinuxConsole(Test):
+ """
+ Boots a x86_64 Linux kernel and checks that the console is operational
+ and the kernel command line is properly passed from QEMU to the kernel
+
+ :avocado: enable
+ :avocado: tags=x86_64
+ """
+
+ timeout = 60
+
+ def test(self):
+ kernel_url = ('https://mirrors.kernel.org/fedora/releases/28/'
+ 'Everything/x86_64/os/images/pxeboot/vmlinuz')
+ kernel_hash = '238e083e114c48200f80d889f7e32eeb2793e02a'
+ kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
+
+ self.vm.set_machine('pc')
+ self.vm.set_console()
+ kernel_command_line = 'console=ttyS0'
+ self.vm.add_args('-kernel', kernel_path,
+ '-append', kernel_command_line)
+ self.vm.launch()
+ console = self.vm.console_socket.makefile()
+ console_logger = logging.getLogger('console')
+ while True:
+ msg = console.readline()
+ console_logger.debug(msg.strip())
+ if 'Kernel command line: %s' % kernel_command_line in msg:
+ break
+ if 'Kernel panic - not syncing' in msg:
+ self.fail("Kernel panic reached")
--
2.17.0
^ permalink raw reply related [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test Cleber Rosa
@ 2018-05-30 20:57 ` Philippe Mathieu-Daudé
2018-06-13 18:30 ` Eduardo Habkost
2018-05-31 10:56 ` Stefan Hajnoczi
1 sibling, 1 reply; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-05-30 20:57 UTC (permalink / raw)
To: Cleber Rosa, qemu-devel
Cc: Eduardo Habkost, Stefan Hajnoczi, Fam Zheng, Amador Pahim
Hi Cleber,
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> This test boots a Linux kernel, and checks that the given command
> line was effective in two ways:
>
> * It makes the kernel use the set "console device" as a console
> * The kernel records the command line as expected in the console
>
> Given that way too many error conditions may occur, and detecting the
> kernel boot progress status may not be trivial, this test relies on a
> timeout to handle unexpected situations. Also, it's *not* tagged as a
> quick test for obvious reasons.
>
> It may be useful, while interactively running/debugging this test, or
> tests similar to this one, to show some of the logging channels.
> Example:
>
> $ avocado --show=QMP,console run boot_linux_console.py
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> ---
> tests/acceptance/boot_linux_console.py | 47 ++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 tests/acceptance/boot_linux_console.py
>
> diff --git a/tests/acceptance/boot_linux_console.py b/tests/acceptance/boot_linux_console.py
> new file mode 100644
> index 0000000000..98324f7591
> --- /dev/null
> +++ b/tests/acceptance/boot_linux_console.py
> @@ -0,0 +1,47 @@
> +# Functional test that boots a Linux kernel and checks the console
> +#
> +# Copyright (c) 2018 Red Hat, Inc.
> +#
> +# Author:
> +# Cleber Rosa <crosa@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or
> +# later. See the COPYING file in the top-level directory.
> +
> +import logging
> +
> +from avocado_qemu import Test
> +
> +
> +class BootLinuxConsole(Test):
> + """
> + Boots a x86_64 Linux kernel and checks that the console is operational
> + and the kernel command line is properly passed from QEMU to the kernel
> +
> + :avocado: enable
> + :avocado: tags=x86_64
Can you move tags=x86_64 to the test() method?
> + """
> +
> + timeout = 60
> +
> + def test(self):
Can we rename this test_fedora28_x86_64_pc()?
> + kernel_url = ('https://mirrors.kernel.org/fedora/releases/28/'
> + 'Everything/x86_64/os/images/pxeboot/vmlinuz')
> + kernel_hash = '238e083e114c48200f80d889f7e32eeb2793e02a'
> + kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
Not related to this patch, but while trying to extend your test, I
noticed fetch_asset() use the url filename as cache filename, so all
further tests (other arch) keep overwriting the same file and no caching
is done.
This is in particular why I used the hashed url as the filename in my
first dirty attempt.
https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg03082.html
> +
> + self.vm.set_machine('pc')
> + self.vm.set_console()
> + kernel_command_line = 'console=ttyS0'
> + self.vm.add_args('-kernel', kernel_path,
> + '-append', kernel_command_line)
> + self.vm.launch()
> + console = self.vm.console_socket.makefile()
> + console_logger = logging.getLogger('console')
> + while True:
> + msg = console.readline()
> + console_logger.debug(msg.strip())
> + if 'Kernel command line: %s' % kernel_command_line in msg:
> + break
> + if 'Kernel panic - not syncing' in msg:
> + self.fail("Kernel panic reached")
>
Thanks for cleaning/fixing this test =)
Moving the :avocado: tag:
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Regards,
Phil.
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test
2018-05-30 20:57 ` Philippe Mathieu-Daudé
@ 2018-06-13 18:30 ` Eduardo Habkost
2018-06-13 18:41 ` Philippe Mathieu-Daudé
0 siblings, 1 reply; 19+ messages in thread
From: Eduardo Habkost @ 2018-06-13 18:30 UTC (permalink / raw)
To: Philippe Mathieu-Daudé
Cc: Cleber Rosa, qemu-devel, Fam Zheng, Stefan Hajnoczi, Amador Pahim
On Wed, May 30, 2018 at 05:57:52PM -0300, Philippe Mathieu-Daudé wrote:
[...]
> > +class BootLinuxConsole(Test):
> > + """
> > + Boots a x86_64 Linux kernel and checks that the console is operational
> > + and the kernel command line is properly passed from QEMU to the kernel
> > +
> > + :avocado: enable
> > + :avocado: tags=x86_64
>
> Can you move tags=x86_64 to the test() method?
I'm queueing this patch as is, as the tag here seems harmless. A
follow-up patch will be required if you want to move the tag.
--
Eduardo
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test
2018-06-13 18:30 ` Eduardo Habkost
@ 2018-06-13 18:41 ` Philippe Mathieu-Daudé
0 siblings, 0 replies; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-06-13 18:41 UTC (permalink / raw)
To: Eduardo Habkost
Cc: Cleber Rosa, qemu-devel, Fam Zheng, Stefan Hajnoczi, Amador Pahim
On 06/13/2018 03:30 PM, Eduardo Habkost wrote:
> On Wed, May 30, 2018 at 05:57:52PM -0300, Philippe Mathieu-Daudé wrote:
> [...]
>>> +class BootLinuxConsole(Test):
>>> + """
>>> + Boots a x86_64 Linux kernel and checks that the console is operational
>>> + and the kernel command line is properly passed from QEMU to the kernel
>>> +
>>> + :avocado: enable
>>> + :avocado: tags=x86_64
>>
>> Can you move tags=x86_64 to the test() method?
>
> I'm queueing this patch as is, as the tag here seems harmless. A
> follow-up patch will be required if you want to move the tag.
No problem!
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test Cleber Rosa
2018-05-30 20:57 ` Philippe Mathieu-Daudé
@ 2018-05-31 10:56 ` Stefan Hajnoczi
1 sibling, 0 replies; 19+ messages in thread
From: Stefan Hajnoczi @ 2018-05-31 10:56 UTC (permalink / raw)
To: Cleber Rosa
Cc: qemu-devel, Eduardo Habkost, Philippe Mathieu-Daudé,
Fam Zheng, Amador Pahim
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Wed, May 30, 2018 at 02:41:56PM -0400, Cleber Rosa wrote:
> This test boots a Linux kernel, and checks that the given command
> line was effective in two ways:
>
> * It makes the kernel use the set "console device" as a console
> * The kernel records the command line as expected in the console
>
> Given that way too many error conditions may occur, and detecting the
> kernel boot progress status may not be trivial, this test relies on a
> timeout to handle unexpected situations. Also, it's *not* tagged as a
> quick test for obvious reasons.
>
> It may be useful, while interactively running/debugging this test, or
> tests similar to this one, to show some of the logging channels.
> Example:
>
> $ avocado --show=QMP,console run boot_linux_console.py
>
> Signed-off-by: Cleber Rosa <crosa@redhat.com>
> ---
> tests/acceptance/boot_linux_console.py | 47 ++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 tests/acceptance/boot_linux_console.py
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
` (4 preceding siblings ...)
2018-05-30 18:41 ` [Qemu-devel] [PATCH v4 5/5] Acceptance tests: add Linux kernel boot and console checking test Cleber Rosa
@ 2018-06-05 14:49 ` Philippe Mathieu-Daudé
2018-06-06 19:26 ` Eduardo Habkost
2018-06-13 18:29 ` Eduardo Habkost
6 siblings, 1 reply; 19+ messages in thread
From: Philippe Mathieu-Daudé @ 2018-06-05 14:49 UTC (permalink / raw)
To: Eduardo Habkost, Fam Zheng
Cc: Cleber Rosa, qemu-devel, Stefan Hajnoczi, Amador Pahim
Hi Eduardo,
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> TL;DR
> =====
>
> Another version, with a minimalist approach, of the acceptance tests
> infrastructure for QEMU, based on the Avocado Testing Framework.
What do you think of this series?
Are you OK to take it via your tree, or should it goes via Fam's "Build
and test automation"?
Thanks,
Phil.
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests
2018-06-05 14:49 ` [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Philippe Mathieu-Daudé
@ 2018-06-06 19:26 ` Eduardo Habkost
0 siblings, 0 replies; 19+ messages in thread
From: Eduardo Habkost @ 2018-06-06 19:26 UTC (permalink / raw)
To: Philippe Mathieu-Daudé
Cc: Fam Zheng, Cleber Rosa, qemu-devel, Stefan Hajnoczi, Amador Pahim
On Tue, Jun 05, 2018 at 11:49:07AM -0300, Philippe Mathieu-Daudé wrote:
> Hi Eduardo,
>
> On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> > TL;DR
> > =====
> >
> > Another version, with a minimalist approach, of the acceptance tests
> > infrastructure for QEMU, based on the Avocado Testing Framework.
>
> What do you think of this series?
>
> Are you OK to take it via your tree, or should it goes via Fam's "Build
> and test automation"?
I can take it via my tree, I just couldn't reserve the time to
check the existing review comments and finish reviewing it.
But if Fam or other maintainer already thinks the series look
good and can be merged, please don't delay this because of me.
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
--
Eduardo
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests
2018-05-30 18:41 [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Cleber Rosa
` (5 preceding siblings ...)
2018-06-05 14:49 ` [Qemu-devel] [PATCH v4 0/5] Acceptance/functional tests Philippe Mathieu-Daudé
@ 2018-06-13 18:29 ` Eduardo Habkost
6 siblings, 0 replies; 19+ messages in thread
From: Eduardo Habkost @ 2018-06-13 18:29 UTC (permalink / raw)
To: Cleber Rosa
Cc: qemu-devel, Amador Pahim, Fam Zheng, Stefan Hajnoczi,
Philippe Mathieu-Daudé
On Wed, May 30, 2018 at 02:41:51PM -0400, Cleber Rosa wrote:
> TL;DR
> =====
>
> Another version, with a minimalist approach, of the acceptance tests
> infrastructure for QEMU, based on the Avocado Testing Framework.
Queued on python-next. Thank you very much, and sorry for taking
so long to queue this.
--
Eduardo
^ permalink raw reply [flat|nested] 19+ messages in thread