Updated: October 28, 2024 |
io-pkt-* driver that provides the hypervisor host with a network interface to connect to a guest's virtio-net vdev
io-pkt-v4-hc -d vdevpeer-net [peer=path,option[,option...] [,peer=path,option,[,option...]...]] io-pkt-v6-hc ...
QNX Neutrino
The default behavior is to assume that the peer is compliant with VIRTIO 1.0 or later, or is VIRTIO 0.9.5-compliant and has negotiated VIRTIO_NET_F_MRG_RXBUF.
The devnp-vdevpeer-net.so driver enables an io-pkt-* networking manager running in the host to communicate with virtual network devices configured for guests. The driver works with both the io-pkt-v4-hc and io-pkt-v6-hc stack variants. It is used for peer-to-peer communication between the hypervisor host and guests, and can be used to facilitate communication between guests and the outside world, by enabling a bridge running in the host's networking manager to connect guests to the outside world.
To use the devnp-vdevpeer-net.so driver to set up peer-to-peer communication in a hypervisor system and with the outside world:
In the hypervisor host, start io-pkt-*, specifying the devnp-vdevpeer-net.so driver, and using the driver options to configure the node in the hypervisor host: the connection path, the MAC address, the path to the node in the guest, and, optionally, a name for the node. For example:
io-pkt-v6-hc -d vdevpeer-net \ peer=/dev/qvm/vt1,bind=/pkt/vp0,mac=a0b0c0d0e0f0
where /dev/qvm/vt1 is the path of the peer to communicate with, /pkt/vp0 is the path to the peer node (the guest), and a0b0c0d0e0f0 is this peer node's MAC address.
ifconfig vp0 192.0.2.1
where vp0 is the peer node, and 192.0.2.1 is its IP address.
For more information about setting up peer-to-peer communications, see Networking in the Using a QNX Hypervisor System chapter.