xref: /freebsd/usr.sbin/bhyve/bhyve_config.5 (revision 12e0d316644a4f80f5f1f78cf07bd93def43b1ca)
1.\" SPDX-License-Identifier: BSD-2-Clause
2.\"
3.\" Copyright (c) 2021 John H. Baldwin <jhb@FreeBSD.org>
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\"
14.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
24.\" SUCH DAMAGE.
25.\"
26.Dd August 13, 2024
27.Dt BHYVE_CONFIG 5
28.Os
29.Sh NAME
30.Nm bhyve_config
31.Nd "bhyve configuration variables"
32.Sh DESCRIPTION
33.Xr bhyve 8
34uses a hierarchical tree of configuration variables to describe global and
35per-device settings.
36Internal nodes in this tree do not have a value,
37only leaf nodes have values.
38This manual describes the configuration variables understood by
39.Xr bhyve 8 .
40If additional variables are defined,
41.Xr bhyve 8
42will ignore them and will not emit errors for unknown variables.
43However, these additional variables can be referenced by other
44variables as described below.
45.Sh VARIABLE VALUES
46Configuration variable values are stored as strings.
47A configuration variable value may refer to one or more other
48configuration values by name.
49Instances of the pattern
50.Sq % Ns Pq Ar var
51are replaced by the value of the configuration variable
52.Va var .
53To avoid unwanted expansion,
54.Sq %
55characters can be escaped by a leading
56.Sq % .
57For example,
58if a configuration variable
59.Va disk
60uses the value
61.Pa /dev/zvol/bhyve/%(name) ,
62then the final value of the
63.Va disk
64variable will be set to the path of a ZFS volume whose name matches
65the name of the virtual machine on the pool
66.Pa bhyve .
67.Pp
68Some configuration variables may be interpreted as a boolean value.
69For those variables the following case-insensitive values may be used to
70indicate true:
71.Pp
72.Bl -bullet -offset indent -compact
73.It
74true
75.It
76on
77.It
78yes
79.It
801
81.El
82.Pp
83The following values may be used to indicate false:
84.Pp
85.Bl -bullet -offset indent -compact
86.It
87false
88.It
89off
90.It
91no
92.It
930
94.El
95.Pp
96Some configuration variables may be interperted as an integer.
97For those variables,
98any syntax supported by
99.Xr strtol 3
100may be used.
101.Sh GLOBAL SETTINGS
102.Ss Architecture Neutral Settings
103.Bl -column "memory.guest_in_core" "integer" "Default"
104.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
105.It Va name Ta string Ta Ta
106The name of the VM.
107.It Va cpus Ta integer Ta 1 Ta
108The total number of virtual CPUs.
109.It Va cores Ta integer Ta 1 Ta
110The number of virtual cores in each virtual socket.
111.It Va threads Ta integer Ta 1 Ta
112The number of virtual CPUs in each virtual core.
113.It Va sockets Ta integer Ta 1 Ta
114The number of virtual sockets.
115.It Va memory.guest_in_core Ta bool Ta false Ta
116Include guest memory in core file.
117.It Va memory.size Ta string Ta 256M Ta
118Guest physical memory size in bytes.
119The value must be formatted as described in
120.Xr expand_number 3 .
121.It Va memory.wired Ta bool Ta false Ta
122Wire guest memory.
123.It Va bootrom Ta path Ta Ta
124Path to a boot ROM.
125During initialization of the guest, the contents of this file are copied into
126the guest's memory.
127If a boot ROM is present, a firmware interface device is
128also enabled for use by the boot ROM.
129.It Va bootvars Ta path Ta Ta
130Path to boot VARS.
131The contents of this file are copied beneath the boot ROM.
132Firmware can write to it to save variables.
133All variables will be persistent even on reboots of the guest.
134.It Va acpi_tables Ta bool Ta true Ta
135Generate ACPI tables.
136.It Va acpi_tables_in_memory Ta bool Ta true Ta
137.Xr bhyve 8
138always exposes ACPI tables by FwCfg.
139For backward compatibility bhyve copies them into the guest memory as well.
140This can cause problems if the guest uses the in-memory version, since certain
141advanced features, such as TPM emulation, are exposed only via FwCfg.
142Therefore, it is recommended to set this flag to false when running Windows guests.
143.It Va destroy_on_poweroff Ta bool Ta false Ta
144Destroy the VM on guest-initiated power-off.
145.It Va gdb.address Ta string Ta localhost Ta
146Hostname, IP address, or IPv6 address for the debug server.
147.It Va gdb.port Ta integer Ta 0 Ta
148TCP port number for the debug server.
149If this is set to a non-zero value, a debug server
150will listen for connections on this port.
151.It Va gdb.wait Ta bool Ta false Ta
152If the debug server is enabled, wait for a debugger to connect
153before starting the guest.
154.It Va keyboard.layout Ta string Ta Ta
155Specify the keyboard layout name with the file name in
156.Ar /usr/share/bhyve/kbdlayout .
157This value only works when loaded with UEFI mode for VNC, and
158used a VNC client that don't support QEMU Extended Key Event
159Message (e.g. TightVNC).
160.It Va pci.enable_bars Ta bool Ta Ta
161Enable and map PCI BARs before executing any guest code.
162This setting is false by default when using a boot ROM and true otherwise.
163.It Va tpm.path Ta string Ta Ta
164Path to the host TPM device.
165This is typically /dev/tpm0.
166.It Va tpm.type Ta string Ta Ta
167Type of the TPM device passed to the guest.
168Currently, only "passthru" is supported.
169.It Va tpm.version Ta string Ta 2.0 Ta
170Version of the TPM device according to the TCG specification.
171Currently, only version 2.0 is supported.
172.It Va rtc.use_localtime Ta bool Ta true Ta
173The real time clock uses the local time of the host.
174If this is set to false, the real time clock uses UTC.
175.It Va uuid Ta string Ta Ta
176The universally unique identifier (UUID) to use in the guest's
177System Management BIOS System Information structure.
178If an explicit value is not set, a valid UUID is generated from
179the host's hostname and the VM name.
180.It Va virtio_msix Ta bool Ta true Ta
181Use MSI-X interrupts for PCI VirtIO devices.
182If set to false, MSI interrupts are used instead.
183.It Va config.dump Ta bool Ta false Ta
184If this value is set to true after
185.Xr bhyve 8
186has finished parsing command line options,
187then
188.Xr bhyve 8
189will write all of its configuration variables to stdout and exit.
190No VM will be started.
191.It Va bios.vendor Ta string Ta BHYVE Ta
192This value is used for the guest's System Management BIOS System Information structure.
193.It Va bios.version Ta string Ta 14.0 Ta
194This value is used for the guest's System Management BIOS System Information structure.
195.It Va bios.release_date Ta string Ta 10/17/2021 Ta
196This value is used for the guest's System Management BIOS System Information structure.
197.It Va system.family_name Ta string Ta Virtual Machine Ta
198Family the computer belongs to.
199This value is used for the guest's System Management BIOS System Information structure.
200.It Va system.manufacturer Ta string Ta FreeBSD Ta
201This value is used for the guest's System Management BIOS System Information structure.
202.It Va system.product_name Ta string Ta BHYVE Ta
203This value is used for the guest's System Management BIOS System Information structure.
204.It Va system.serial_number Ta string Ta None Ta
205This value is used for the guest's System Management BIOS System Information structure.
206.It Va system.sku Ta string Ta None Ta
207Stock keeping unit of the computer.
208It's also called product ID or purchase order number.
209This value is used for the guest's System Management BIOS System Information structure.
210.It Va system.version Ta string Ta 1.0 Ta
211This value is used for the guest's System Management BIOS System Information structure.
212.It Va board.manufacturer Ta string Ta FreeBSD Ta
213This value is used for the guest's System Management BIOS System Information structure.
214.It Va board.product_name Ta string Ta BHYVE Ta
215This value is used for the guest's System Management BIOS System Information structure.
216.It Va board.version Ta string Ta 1.0 Ta
217This value is used for the guest's System Management BIOS System Information structure.
218.It Va board.serial_number Ta string Ta None Ta
219This value is used for the guest's System Management BIOS System Information structure.
220.It Va board.asset_tag Ta string Ta None Ta
221This value is used for the guest's System Management BIOS System Information structure.
222.It Va board.location Ta string Ta None Ta
223Describes the board's location within the chassis.
224This value is used for the guest's System Management BIOS System Information structure.
225.It Va chassis.manufacturer Ta string Ta FreeBSD Ta
226This value is used for the guest's System Management BIOS System Information structure.
227.It Va chassis.version Ta string Ta 1.0 Ta
228This value is used for the guest's System Management BIOS System Information structure.
229.It Va chassis.serial_number Ta string Ta None Ta
230This value is used for the guest's System Management BIOS System Information structure.
231.It Va chassis.asset_tag Ta string Ta None Ta
232This value is used for the guest's System Management BIOS System Information structure.
233.It Va chassis.sku Ta string Ta None Ta
234Stock keeping unit of the chassis.
235It's also called product ID or purchase order number.
236This value is used for the guest's System Management BIOS System Information structure.
237.El
238.Ss x86-Specific Settings
239.Bl -column "x86.vmexit_on_pause" "integer" "Default"
240.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
241.It Va x86.mptable Ta bool Ta true Ta
242Generate an MPTable.
243.It Va x86.x2apic Ta bool Ta false Ta
244Configure guest's local APICs in x2APIC mode.
245.It Va x86.strictio Ta bool Ta false Ta
246Exit if a guest accesses an I/O port that is not emulated.
247By default, writes are ignored and reads return all bits set.
248.It Va x86.strictmsr Ta bool Ta true Ta
249Inject a general protection fault if a guest accesses a Model Specific
250Register (MSR) that is not emulated.
251If this is false, writes are ignored and reads return zero.
252.It Va x86.vmexit_on_hlt Ta bool Ta false Ta
253Force a VM exit when a guest CPU executes the
254.Dv HLT
255instruction.
256This allows idle guest CPUs to yield the host CPU.
257.It Va x86.vmexit_on_pause Ta bool Ta false Ta
258Force a VM exit when a guest CPU executes the
259.Dv PAUSE
260instruction.
261.El
262.Sh DEVICE SETTINGS
263Device settings are stored under a device node.
264The device node's name is set by the parent bus of the device.
265.Ss PCI Device Settings
266PCI devices are described by a device node named
267.Dq pci . Ns Ar bus . Ns Ar slot . Ns Ar function
268where each of
269.Ar bus ,
270.Ar slot ,
271and
272.Ar function
273are formatted as decimal values with no padding.
274All PCI device nodes must contain a configuration variable named
275.Dq device
276which specifies the device model to use.
277The following PCI device models are supported:
278.Bl -tag -indent
279.It Li hostbridge
280Provide a simple PCI-Host bridge device.
281This is usually configured at pci0:0:0 and is required by most guest
282operating systems.
283.It Li ahci
284AHCI storage controller.
285.It Li e1000
286Intel e82545 network interface.
287.It Li fbuf
288VGA framebuffer device attached to VNC server.
289.It Li lpc
290LPC PCI-ISA bridge with COM1-COM4 16550 serial ports,
291a boot ROM,
292an optional fwcfg type,
293and an optional debug/test device.
294This device must be configured on bus 0.
295.It Li hda
296High Definition audio controller.
297.It Li nvme
298NVM Express (NVMe) controller.
299.It Li passthru
300PCI pass-through device.
301.It Li uart
302PCI 16550 serial device.
303.It Li virtio-9p
304VirtIO 9p (VirtFS) interface.
305.It Li virtio-blk
306VirtIO block storage interface.
307.It Li virtio-console
308VirtIO console interface.
309.It Li virtio-input
310VirtIO input interface.
311.It Li virtio-net
312VirtIO network interface.
313.It Li virtio-rnd
314VirtIO RNG interface.
315.It Li virtio-scsi
316VirtIO SCSI interface.
317.It Li xhci
318Extensible Host Controller Interface (XHCI) USB controller.
319.El
320.Ss USB Device Settings
321USB controller devices contain zero or more child USB devices
322attached to slots.
323Each USB device stores its settings in a node named
324.Dq slot. Ns Va N
325under the controller's device node.
326.Va N
327is the number of the slot to which the USB device is attached.
328Note that USB slot numbers begin at 1.
329All USB device nodes must contain a configuration variable named
330.Dq device
331which specifies the device model to use.
332The following USB device models are supported:
333.Bl -tag -indent
334.It Li tablet
335A USB tablet device which provides precise cursor synchronization
336when using VNC.
337.El
338.Ss Block Device Settings
339Block devices use the following settings to configure their backing store.
340These settings are stored in the configuration node of the respective device.
341.Bl -column "sectorsize" "logical[/physical]" "Default"
342.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
343.It path Ta string Ta Ta
344The path of the file or disk device to use as the backing store.
345.It nocache Ta bool Ta false Ta
346Disable caching on the backing file by opening the backing file with
347.Dv O_DIRECT .
348.It nodelete Ta bool Ta false Ta
349Disable emulation of guest trim requests via
350.Dv DIOCGDELETE
351requests.
352.It sync Ta bool Ta false Ta
353Write changes to the backing file with synchronous writes.
354.It direct Ta bool Ta false Ta
355An alias for
356.Va sync .
357.It ro Ta bool Ta false Ta
358Disable writes to the backing file.
359.It sectorsize Ta Va logical Ns Op / Ns Va physical Ta Ta
360Specify the logical and physical sector size of the emulated disk.
361If the physical size is not specified,
362it is equal to the logical size.
363.El
364.Ss Network Backend Settings
365Network devices use the following settings to configure their backend.
366The backend is responsible for passing packets between the device model
367and a desired destination.
368Configuring a backend requires setting the
369.Va backend
370variable.
371The type of a backend can either be set explicitly via the
372.Va type
373variable
374or it can be inferred from the value of
375.Va backend .
376.Pp
377The following types of backends are supported:
378.Bl -tag -width "netgraph"
379.It tap
380Use the
381.Xr tap 4
382interface named in
383.Va backend
384as the backend.
385.It netgraph
386Use a
387.Xr netgraph 4
388socket hook as the backend.
389This backend uses the following additional variables:
390.Bl -column "peerhook" "Format" "Default"
391.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
392.It Va path Ta string Ta Ta
393The name of the
394.Xr netgraph 4
395destination node.
396.It Va peerhook Ta string Ta Ta
397The name of the destination hook.
398.It Va socket Ta string Ta Ta
399The name of the created
400.Xr ng_socket 4
401node.
402.It Va hook Ta string Ta vmlink Ta
403The name of the source hook on the created
404.Xr ng_socket 4
405node.
406.El
407.It netmap
408Use
409.Xr netmap 4
410either on a network interface or a port on a
411.Xr vale 4
412bridge as the backend.
413The value of
414.Va backend
415is passed to
416.Xr nm_open
417to connect to a netmap port.
418.It slirp
419Use the slirp backend to provide a userspace network stack.
420The
421.Va hostfwd
422variable is used to configure how packets from the host are translated
423before being sent to the guest.
424.Bl -column "peerhook" "Format" "Default"
425.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
426.It Va hostfwd Ta string Ta Ta
427A semicolon-separated list of host forwarding rules, each of the form
428.Ar proto:haddr:hport-gaddr:gport ,
429where
430.Ar proto
431is either
432.Ql tcp
433or
434.Ql udp .
435If the guest address is equal to the empty string, packets will be
436forwarded to the first DHCP-assigned address in the guest.
437.El
438.El
439.Pp
440If
441.Va type
442is not specified explicitly, then it is inferred from
443.Va backend
444based on the following patterns:
445.Bl -column -offset indent "valuebridge:port"
446.It Sy Pattern Ta Sy Type
447.It tap Ns Va N Ta tap
448.It vmnet Ns Va N Ta tap
449.It netgraph Ta netgraph
450.It netmap: Ns Va interface Ta netmap
451.It vale Ns Va bridge : Ns Va port Ta netmap
452.El
453.Ss UART Device Settings
454.Bl -column "Name" "Format" "Default"
455.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
456.It Va path Ta path Ta Ta
457Backend device for the serial port.
458Either the pathname of a character device or
459.Dq stdio
460to use standard input and output of the
461.Xr bhyve 8
462process.
463.El
464.Ss Host Bridge Settings
465.Bl -column "pcireg.*" "integer" "Default"
466.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
467.It Va pcireg.* Ta integer Ta Ta
468Values of PCI register.
469.Bl -column "device" "Default"
470.It Sy Name Ta Sy Default
471.It Va vendor Ta integer Ta 0x1275 Ta
472.It Va device Ta integer Ta 0x1275 Ta
473.El
474.El
475.Ss AHCI Controller Settings
476AHCI controller devices contain zero or more ports each of which
477provides a storage device.
478Each port stores its settings in a node named
479.Dq port. Ns Va N
480under the controller's device node.
481The
482.Va N
483values are formatted as successive decimal values starting with 0.
484In addition to the block device settings described above, each
485port supports the following settings:
486.Bl -column "model" "integer" "generated"
487.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
488.It Va type Ta string Ta Ta
489The type of storage device to emulate.
490Must be set to either
491.Dq cd
492or
493.Dq hd .
494.It Va nmrr Ta integer Ta 0 Ta
495Nominal Media Rotation Rate, also known as RPM.
496A value 1 of indicates a device with no rate such as a Solid State Disk.
497.It Va ser Ta string Ta generated Ta
498Serial number of up to twenty characters.
499A default serial number is generated using a hash of the backing
500store's pathname.
501.It Va rev Ta string Ta 001 Ta
502Revision number of up to eight characters.
503.It Va model Ta string Ta Ta
504Model number of up to forty characters.
505Separate default model strings are used for
506.Dq cd
507and
508.Dq hd
509device types.
510.El
511.Ss e1000 Settings
512In addition to the network backend settings,
513Intel e82545 network interfaces support the following variables:
514.Bl -column "Name" "MAC address" "generated"
515.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
516.It Va mac Ta MAC address Ta generated Ta
517MAC address.
518If an explicit address is not provided,
519a MAC address is generated from a hash of the device's PCI address.
520.El
521.Ss Frame Buffer Settings
522.Bl -column "password" "[IP:]port" "127.0.0.1:5900"
523.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
524.It Va wait Ta bool Ta false Ta
525Wait for a remote connection before starting the VM.
526.It Va rfb Ta Oo Ar IP Ns : Oc Ns Ar port Ta 127.0.0.1:5900 Ta
527TCP address to listen on for remote connections.
528The IP address must be given as a numeric address.
529IPv6 addresses must be enclosed in square brackets and
530support scoped identifiers as described in
531.Xr getaddrinfo 3 .
532A bare port number may be given in which case the IPv4
533localhost address is used.
534.It Va vga Ta string Ta io Ta
535VGA configuration.
536More details are provided in
537.Xr bhyve 8 .
538.It Va w Ta integer Ta 1024 Ta
539Frame buffer width in pixels.
540.It Va h Ta integer Ta 768 Ta
541Frame buffer height in pixels.
542.It Va password Ta string Ta Ta
543Password to use for VNC authentication.
544This type of authentication is known to be cryptographically weak and is not
545intended for use on untrusted networks.
546.El
547.Ss High Definition Audio Settings
548.Bl -column "Name" "Format" "Default"
549.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
550.It Va play Ta path Ta Ta
551Host playback device,
552typically
553.Pa /dev/dsp0 .
554.It Va rec Ta path Ta Ta
555Host recording device,
556typically
557.Pa /dev/dsp0 .
558.El
559.Ss LPC Device Settings
560The LPC bridge stores its configuration under a top-level
561.Va lpc
562node rather than under the PCI LPC device's node.
563The following nodes are available under
564.Va lpc :
565.Bl -column "pc-testdev" "Format" "Default"
566.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
567.It Va com1 Ta node Ta Ta
568Settings for the COM1 serial port device.
569.It Va com2 Ta node Ta Ta
570Settings for the COM2 serial port device.
571.It Va com3 Ta node Ta Ta
572Settings for the COM3 serial port device.
573.It Va com4 Ta node Ta Ta
574Settings for the COM4 serial port device.
575.It Va fwcfg Ta string Ta bhyve Ta
576The fwcfg type to be used.
577Supported values are
578.Dq bhyve
579for fwctl and
580.Dq qemu
581for fwcfg.
582.It Va pc-testdev Ta bool Ta false Ta
583Enable the PC debug/test device.
584.It Va pcireg.* Ta integer Ta Ta
585Values of PCI register.
586It also accepts the value
587.Ar host
588to use the pci id of the host system.
589This value is required for the Intel GOP driver to work properly.
590.Bl -column "subvendor" "Default"
591.It Sy Name Ta Sy Default
592.It Va vendor Ta 0x8086
593.It Va device Ta 0x7000
594.It Va revid Ta 0
595.It Va subvendor Ta 0
596.It Va subdevice Ta 0
597.El
598.El
599.Ss NVMe Controller Settings
600Each NVMe controller supports a single storage device.
601The device can be backed either by a memory disk described by the
602.Va ram
603variable, or a block device using the block device settings described above.
604In addition, each controller supports the following settings:
605.Bl -column "ioslots" "Format" "Default"
606.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
607.It Va maxq Ta integer Ta 16 Ta
608Maximum number of I/O submission and completion queue pairs.
609.It Va qsz Ta integer Ta 2058 Ta
610Number of elements in each I/O queue.
611.It Va ioslots Ta integer Ta 8 Ta
612Maximum number of concurrent I/O requests.
613.It Va sectsz Ta integer Ta Ta
614Sector size.
615Can be one of 512, 4096, or 8192.
616Devices backed by a memory disk use 4096 as the default.
617Devices backed by a block device use the block device's sector size
618as the default.
619.It Va ser Ta string Ta Ta
620Serial number of up to twenty characters.
621A default serial number is generated using a hash of the device's PCI address.
622.It Va eui64 Ta integer Ta Ta
623IEEE Extended Unique Identifier.
624If an EUI is not provided, a default is generated using a checksum of the
625device's PCI address.
626.It Va dsm Ta string Ta auto Ta
627Whether or not to advertise DataSet Management support.
628One of
629.Dq auto ,
630.Dq enable ,
631or
632.Dq disable .
633The
634.Dq auto
635setting only advertises support if the backing store supports
636resource freeing, for example via TRIM.
637.It Va ram Ta integer Ta Ta
638If set, allocate a memory disk as the backing store.
639The value of this variable is the size of the memory disk in megabytes.
640.El
641.Ss PCI Passthrough Settings
642The
643.Xr ppt 4
644device driver must be attached to the
645PCI device being passed through.
646The device to pass through can be identified either by name or its
647host PCI bus location.
648.Bl -column "Name" "integer" "Default"
649.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
650.It Va bus Ta integer Ta Ta
651Host PCI bus address of device to pass through.
652.It Va slot Ta integer Ta Ta
653Host PCI slot address of device to pass through.
654.It Va func Ta integer Ta Ta
655Host PCI function address of device to pass through.
656.It Va pptdev Ta string Ta Ta
657Name of a
658.Xr ppt 4
659device to pass through.
660.It Va rom Ta path Ta Ta
661ROM file of the device which will be executed by OVMF to init the device.
662.El
663.Ss VirtIO 9p Settings
664Each VirtIO 9p device exposes a single filesystem from a host path.
665.Bl -column "sharename" "Format" "Default"
666.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
667.It Va sharename Ta string Ta Ta
668The share name exposed to the guest.
669.It Va path Ta path Ta Ta
670The path of a directory on the host to export to the guest.
671.It Va ro Ta bool Ta false Ta
672If true, the guest filesystem is read-only.
673.El
674.Ss VirtIO Block Device Settings
675In addition to the block device settings described above, each
676VirtIO block device supports the following settings:
677.Bl -column "model" "integer" "generated"
678.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
679.It Va ser Ta string Ta generated Ta
680Serial number of up to twenty characters.
681A default serial number is generated using a hash of the backing
682store's pathname.
683.El
684.Ss VirtIO Console Device Settings
685Each VirtIO Console device contains one or more console ports.
686Each port stores its settings in a node named
687.Dq port. Ns Va N
688under the controller's device node.
689The
690.Va N
691values are formatted as successive decimal values starting with 0.
692Each port supports the following settings:
693.Bl -column "Name" "Format" "Default"
694.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
695.It Va name Ta string Ta Ta
696The name of the port exposed to the guest.
697.It Va path Ta path Ta Ta
698The path of a UNIX domain socket providing the host connection for the port.
699.El
700.Ss VirtIO Input Interface Settings
701Each VirtIO Input device contains one input event device.
702All input events of the input event device are send to the guest by VirtIO Input interface.
703VirtIO Input Interfaces support the following variables:
704.Bl -column "Name" "Format" "Default"
705.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
706.It Va path Ta path Ta Ta
707The path of the input event device exposed to the guest
708.El
709.Ss VirtIO Network Interface Settings
710In addition to the network backend settings,
711VirtIO network interfaces support the following variables:
712.Bl -column "Name" "MAC address" "generated"
713.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
714.It Va mac Ta MAC address Ta generated Ta
715MAC address.
716If an explicit address is not provided,
717a MAC address is generated from a hash of the device's PCI address.
718.It Va mtu Ta integer Ta 1500 Ta
719The largest supported MTU advertised to the guest.
720.El
721.Ss VirtIO SCSI Settings
722.Bl -column "Name" "integer" "Default"
723.It Sy Name Ta Sy Format Ta Sy Default Ta Sy Description
724.It Va dev Ta path Ta Ta
725The path of a CAM target layer (CTL) device to export:
726.Pa /dev/cam/ctl Ns Oo Ar pp . Ns Ar vp Oc .
727.It Va iid Ta integer Ta 0 Ta
728Initiator ID to use when sending requests to the CTL port.
729.El
730.Sh SEE ALSO
731.Xr expand_number 3 ,
732.Xr getaddrinfo 3 ,
733.Xr strtol 3 ,
734.Xr netgraph 4 ,
735.Xr netmap 4 ,
736.Xr ng_socket 4 ,
737.Xr tap 4 ,
738.Xr vale 4 ,
739.Xr vmnet 4 ,
740.Xr bhyve 8
741