Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vmx(4) [freebsd man page]

VMX(4)							   BSD Kernel Interfaces Manual 						    VMX(4)

NAME
vmx -- VMware VMXNET3 Virtual Interface Controller device SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device vmx Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_vmx_load="YES" DESCRIPTION
The vmx driver provides support for the VMXNET3 virtual NIC available in virtual machines by VMware. It appears as a simple Ethernet device but is actually a virtual network interface to the underlying host operating system. This driver supports the VMXNET3 driver protocol, as an alternative to the emulated pcn(4), em(4) interfaces also available in the VMware environment. The vmx driver is optimized for the virtual machine, it can provide advanced capabilities depending on the underlying host operating system and the physical network interface controller of the host. The vmx driver supports features like multiqueue support, IPv6 checksum offloading, MSI/MSI-X support and hardware VLAN tagging in VMware's VLAN Guest Tagging (VGT) mode. The vmx driver supports VMXNET3 VMware virtual NICs provided by the virtual machine hardware version 7 or newer, as provided by the following products: o VMware ESX/ESXi 4.0 and newer o VMware Server 2.0 and newer o VMware Workstation 6.5 and newer o VMware Fusion 2.0 and newer For more information on configuring this device, see ifconfig(8). MULTIPLE QUEUES
The vmx driver supports multiple transmit and receive queues. Multiple queues are only supported by certain VMware products, such as ESXi. The number of queues allocated depends on the presence of MSI-X, the number of configured CPUs, and the tunables listed below. FreeBSD does not enable MSI-X support on VMware by default. The hw.pci.honor_msi_blacklist tunable must be disabled to enable MSI-X support. LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.vmx.txnqueue hw.vmx.X.txnqueue Maximum number of transmit queues allocated by default by the driver. The default value is 8. The maximum supported by the VMXNET3 virtual NIC is 8. hw.vmx.rxnqueue hw.vmx.X.rxnqueue Maximum number of receive queues allocated by default by the driver. The default value is 8. The maximum supported by the VMXNET3 virtual NIC is 16. hw.vmx.txndesc hw.vmx.X.txndesc Number of transmit descriptors allocated by the driver. The default value is 512. The value must be a multiple of 32, and the maxi- mum is 4096. hw.vmx.rxndesc hw.vmx.X.rxndesc Number of receive descriptors per ring allocated by the driver. The default value is 256. The value must be a multiple of 32, and the maximum is 2048. There are two rings so the actual usage is doubled. EXAMPLES
The following entry must be added to the VMware configuration file to provide the vmx device: ethernet0.virtualDev = "vmxnet3" SEE ALSO
altq(4), arp(4), em(4), netintro(4), ng_ether(4), pcn(4), vlan(4), ifconfig(8) AUTHORS
The vmx driver was ported from OpenBSD and significantly rewritten by Bryan Venteicher <bryanv@freebsd.org>. The OpenBSD driver was written by Tsubai Masanari. BSD
March 17, 2014 BSD

Check Out this Related Man Page

VTNET(4)						   BSD Kernel Interfaces Manual 						  VTNET(4)

NAME
vtnet -- VirtIO Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device vtnet Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_vtnet_load="YES" DESCRIPTION
The vtnet device driver provides support for VirtIO Ethernet devices. If the hypervisor advertises the appreciate features, the vtnet driver supports TCP/UDP checksum offload for both transmit and receive, TCP segmentation offload (TSO), TCP large receive offload (LRO), and hardware VLAN tag stripping/insertion features, as well as a multicast hash filter, as well as Jumbo Frames (up to 9216 bytes), which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. For more information on configuring this device, see ifconfig(8). LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.vtnet.csum_disable hw.vtnet.X.csum_disable This tunable disables receive and send checksum offload. The default value is 0. hw.vtnet.tso_disable hw.vtnet.X.tso_disable This tunable disables TSO. The default value is 0. hw.vtnet.lro_disable hw.vtnet.X.lro_disable This tunable disables LRO. The default value is 0. hw.vtnet.mq_disable hw.vtnet.X.mq_disable This tunable disables multiqueue. The default value is 0. hw.vtnet.mq_max_pairs hw.vtnet.X.mq_max_pairs This tunable sets the maximum number of transmit and receive queue pairs. Multiple queues are only supported when the Multiqueue feature is negotiated. This driver supports a maximum of 8 queue pairs. The number of queue pairs used is the lesser of the maximum supported by the driver and the hypervisor, the number of CPUs present in the guest, and this tunable if not zero. The default value is 0. SEE ALSO
arp(4), netintro(4), ng_ether(4), virtio(4), vlan(4), ifconfig(8) HISTORY
The vtnet driver was written by Bryan Venteicher <bryanv@FreeBSD.org>. It first appeared in FreeBSD 9.0. CAVEATS
The vtnet driver only supports LRO when the hypervisor advertises the mergeable buffer feature. BSD
January 22, 2012 BSD
Man Page