qrap.1: Clarify it takes a qemu command, not a path

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
This commit is contained in:
Stefano Brivio 2022-05-14 07:30:06 +02:00
parent 32210fb64f
commit b164d257a1

6
qrap.1
View file

@ -19,10 +19,10 @@ A running instance of \fBpasst\fR(1) is probed checking for UNIX domain sockets,
answering a dummy ARP request, with names starting from answering a dummy ARP request, with names starting from
\fI/tmp/passt_1.socket\fR up to \fI/tmp/passt_64.socket\fR. \fI/tmp/passt_1.socket\fR up to \fI/tmp/passt_64.socket\fR.
If first and second arguments are not a socket number and a path, that is, If first and second arguments are not a socket number and a command, that is,
respectively, \fIFDNUM\fR and \fIQEMU_CMD\fR, \fBqrap\fR will try to locate a respectively, \fIFDNUM\fR and \fIQEMU_CMD\fR, \fBqrap\fR will try to locate a
qemu binary and patch the command line to specify a network device and a qemu executable in \fBPATH\fR and patch the command line to specify a network
\fInetdev\fR back-end for usage with \fBpasst\fR(1). device and a \fInetdev\fR back-end for usage with \fBpasst\fR(1).
If \fBqrap\fR patches the command line, it will remove any potentially If \fBqrap\fR patches the command line, it will remove any potentially
conflicting network device, that is, any \fI-netdev\fR or \fI-net\fR option, or conflicting network device, that is, any \fI-netdev\fR or \fI-net\fR option, or