Alright, set xvif(4) syntax once and for all. Tested with ipf(4) under

XEN3_DOM0 amd64.

Fixes PR misc/39376.

See http://mail-index.netbsd.org/port-xen/2011/04/06/msg006603.html
This commit is contained in:
jym 2011-04-06 23:51:55 +00:00
parent 962e9ad63f
commit d833e65927
2 changed files with 8 additions and 8 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: xvif.4,v 1.3 2011/04/03 23:44:46 jym Exp $
.\" $NetBSD: xvif.4,v 1.4 2011/04/06 23:51:56 jym Exp $
.\"
.\" Copyright (c) 2011 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -27,7 +27,7 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd April 4, 2011
.Dd April 7, 2011
.Dt XVIF 4 xen
.Os
.Sh NAME
@ -62,7 +62,7 @@ entries.
All
.Nm
interfaces follow the
.Dq xvifX-Y
.Dq xvifXiY
naming convention, where
.Sq X
represents the guest domain identifier, and
@ -80,12 +80,12 @@ Conceptually, frontends and backends drivers are
similar to two Ethernet cards connected via a crossover cable.
.Sh DIAGNOSTICS
.Bl -diag
.It "xvif%d-%d: can't read %s/mac: %d"
.It "xvif%di%d: can't read %s/mac: %d"
The MAC address for this interface could not be read from XenStore.
.It "xvif%d-%d: %s is not a valid mac address"
.It "xvif%di%d: %s is not a valid mac address"
The MAC address specified in the configuration file of the newly
created guest domain is invalid.
.It "xvif%d-%d: Ethernet address %s"
.It "xvif%di%d: Ethernet address %s"
MAC address of the
.Nm
interface.

View File

@ -1,4 +1,4 @@
/* $NetBSD: xennetback_xenbus.c,v 1.39 2011/04/03 23:21:37 jym Exp $ */
/* $NetBSD: xennetback_xenbus.c,v 1.40 2011/04/06 23:51:55 jym Exp $ */
/*
* Copyright (c) 2006 Manuel Bouyer.
@ -271,7 +271,7 @@ xennetback_xenbus_create(struct xenbus_device *xbusd)
ifp = &xneti->xni_if;
ifp->if_softc = xneti;
snprintf(ifp->if_xname, IFNAMSIZ, "xvif%d-%d",
snprintf(ifp->if_xname, IFNAMSIZ, "xvif%di%d",
(int)domid, (int)handle);
/* read mac address */