From: Manuel Bouyer <bouyer@netbsd.org>
To: xen-devel@lists.xenproject.org
Cc: Manuel Bouyer <bouyer@netbsd.org>, Wei Liu <wl@xen.org>,
Ian Jackson <iwj@xenproject.org>
Subject: [PATCH v3] Document qemu-ifup on NetBSD
Date: Wed, 3 Feb 2021 17:54:20 +0100 [thread overview]
Message-ID: <20210203165421.1550-3-bouyer@netbsd.org> (raw)
In-Reply-To: <20210203165421.1550-1-bouyer@netbsd.org>
Document that on NetBSD, the tap interface will be configured by the
qemu-ifup script.
Signed-off-by: Manuel Bouyer <bouyer@netbsd.org>
Release-Acked-by: Ian Jackson <iwj@xenproject.org>
---
docs/man/xl-network-configuration.5.pod | 3 +++
1 file changed, 3 insertions(+)
diff --git a/docs/man/xl-network-configuration.5.pod b/docs/man/xl-network-configuration.5.pod
index af058d4d3c..8e5fd909fa 100644
--- a/docs/man/xl-network-configuration.5.pod
+++ b/docs/man/xl-network-configuration.5.pod
@@ -172,6 +172,9 @@ add it to the relevant bridge). Defaults to
C<XEN_SCRIPT_DIR/vif-bridge> but can be set to any script. Some example
scripts are installed in C<XEN_SCRIPT_DIR>.
+Note on NetBSD HVM guests will ignore the script option for tap
+(emulated) interfaces and always use
+C<XEN_SCRIPT_DIR/qemu-ifup> to configure the interface in bridged mode.
=head2 ip
--
2.29.2
next prev parent reply other threads:[~2021-02-03 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 16:54 [PATCH] add a qemu-ifup script on NetBSD Manuel Bouyer
2021-02-03 16:54 ` [PATCH] xenstored: close socket connections on error Manuel Bouyer
2021-02-03 17:24 ` Ian Jackson
2021-02-03 17:38 ` Ian Jackson
2021-02-03 17:48 ` Manuel Bouyer
2021-02-04 11:11 ` Jürgen Groß
2021-02-04 11:16 ` Manuel Bouyer
2021-02-04 11:18 ` Jürgen Groß
2021-02-04 11:42 ` Ian Jackson
2021-02-03 16:54 ` Manuel Bouyer [this message]
2021-02-03 16:54 ` [PATCH v3] NetBSD: use system-provided headers Manuel Bouyer
2021-02-03 17:26 ` Ian Jackson
2021-02-03 18:27 ` Roger Pau Monné
2021-02-03 17:19 ` [PATCH] add a qemu-ifup script on NetBSD Ian Jackson
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=20210203165421.1550-3-bouyer@netbsd.org \
--to=bouyer@netbsd.org \
--cc=iwj@xenproject.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.