From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>
Subject: [PULL 02/14] docs/system: reword the TAP notes to remove tarball ref
Date: Sun, 27 Jul 2025 09:32:41 +0100 [thread overview]
Message-ID: <20250727083254.3826585-3-alex.bennee@linaro.org> (raw)
In-Reply-To: <20250727083254.3826585-1-alex.bennee@linaro.org>
We don't ship the tarball and users should generally look to the
distribution specific packaging.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/560
Reviewed-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-ID: <20250725154517.3523095-3-alex.bennee@linaro.org>
diff --git a/docs/system/devices/net.rst b/docs/system/devices/net.rst
index 4d787c3aeb0..7d76fe88c45 100644
--- a/docs/system/devices/net.rst
+++ b/docs/system/devices/net.rst
@@ -21,11 +21,17 @@ configure it as if it was a real ethernet card.
Linux host
^^^^^^^^^^
-As an example, you can download the ``linux-test-xxx.tar.gz`` archive
-and copy the script ``qemu-ifup`` in ``/etc`` and configure properly
-``sudo`` so that the command ``ifconfig`` contained in ``qemu-ifup`` can
-be executed as root. You must verify that your host kernel supports the
-TAP network interfaces: the device ``/dev/net/tun`` must be present.
+A distribution will generally provide specific helper scripts when it
+packages QEMU. By default these are found at ``/etc/qemu-ifup`` and
+``/etc/qemu-ifdown`` and are called appropriately when QEMU wants to
+change the network state.
+
+If QEMU is being run as a non-privileged user you may need properly
+configure ``sudo`` so that network commands in the scripts can be
+executed as root.
+
+You must verify that your host kernel supports the TAP network
+interfaces: the device ``/dev/net/tun`` must be present.
See :ref:`sec_005finvocation` to have examples of command
lines using the TAP network interfaces.
--
2.47.2
next prev parent reply other threads:[~2025-07-27 8:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 8:32 [PULL for 10.1-rc1 00/14] documentation an testing updates Alex Bennée
2025-07-27 8:32 ` [PULL 01/14] docs/user: clarify user-mode expects the same OS Alex Bennée
2025-07-27 8:32 ` Alex Bennée [this message]
2025-07-27 8:32 ` [PULL 03/14] docs/user: clean up headings Alex Bennée
2025-07-27 8:32 ` [PULL 04/14] docs/user: slightly reword section on system calls Alex Bennée
2025-07-27 8:32 ` [PULL 05/14] docs/user: expand section on threading Alex Bennée
2025-07-27 8:32 ` [PULL 06/14] tests/functional: add hypervisor test for aarch64 Alex Bennée
2025-08-13 7:27 ` Philippe Mathieu-Daudé
2025-08-13 8:56 ` Alex Bennée
2025-07-27 8:32 ` [PULL 07/14] tests/tcg: skip libsyscall.so on softmmu tests Alex Bennée
2025-07-27 8:32 ` [PULL 08/14] tests/tcg: remove ADDITIONAL_PLUGINS_TESTS Alex Bennée
2025-07-27 8:32 ` [PULL 09/14] tests/tcg: don't include multiarch tests if not supported Alex Bennée
2025-07-27 8:32 ` [PULL 10/14] configure: expose PYTHON to test/tcg/config-host.mak Alex Bennée
2025-07-27 8:32 ` [PULL 11/14] tests/tcg: reduce the number of plugin tests combinations Alex Bennée
2025-07-28 19:03 ` Pierrick Bouvier
2025-07-28 20:14 ` Gustavo Romero
2025-07-31 18:58 ` Gustavo Romero
2025-07-31 19:23 ` Pierrick Bouvier
2025-07-31 19:34 ` Gustavo Romero
2025-08-01 0:29 ` Gustavo Romero
2025-08-01 0:33 ` Gustavo Romero
2025-07-30 7:25 ` Pierrick Bouvier
2025-08-04 8:39 ` Alex Bennée
2025-08-04 16:24 ` Pierrick Bouvier
2025-07-27 8:32 ` [PULL 12/14] tests/docker: add --arch-only to qemu deps for all-test-cross Alex Bennée
2025-07-27 8:32 ` [PULL 13/14] tests/docker: handle host-arch selection " Alex Bennée
2025-07-27 8:32 ` [PULL 14/14] tests/functional: expose sys.argv to unittest.main Alex Bennée
2025-07-28 15:20 ` [PULL for 10.1-rc1 00/14] documentation an testing updates Stefan Hajnoczi
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=20250727083254.3826585-3-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=manos.pitsidianakis@linaro.org \
--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).