The following describes a configuration for a virtio-net vdev for a node in a guest communicating with a devnp-vdevpeer.so driver in the hypervisor host.
The figure below illustrates a peer-to-peer connection using a virtio-net vdev in a guest and the devnp-vdevpeer.so io-pkt-* driver running in the hypervisor host (see devnp-vdevpeer.so in the Utilities and Drivers Reference chapter).
The following shows the virtio-net vdev configuration in the *.qvmconf file for the VM (qvm process instance) hosting the guest, along with the vdevpeer driver startup options that will enable the hypervisor host to connect to a node in the guest, and the instructions to enable the interface.
For an QNX Neutrino 7.0 guest on an ARM board, configure a virtio-net vdev in the VM as follows:
system qnx7-arm-guest ... # The loc and intr gic options are for ARM only. The guest # will see the virtio-net vdev as a memory-mapped I/O device # at the specified location. vdev virtio-net loc 0x1c0c0000 intr gic:40 mac aa:aa:aa:aa:aa:aa name p2p peer /dev/vdevpeers/vp0
where:
Start io-pkt-* in the host, specifying the following for the vdevpeer driver:
io-pkt-v6-hc \ -d vdevpeer peer=/dev/qvm/qnx7-arm-guest/p2p,bind=/dev/vdevpeers/vp0,mac=a0b0c0d0e0f0
where:
Finally, assuming that you have already enabled an interface on the host. For example:
ifconfig vp0 up ifconfig vp0 192.168.1.1
you must now enable the interface on the guest and assign it a static IP address in the same subnet as the host. For example, for a QNX Neutrino OS guest:
ifconfig vt0 192.168.1.2
where vt0 is the name of the interface on the guest, vp0 is the peer-to-peer interface on the host, and 192.168.1.2 is an address in the same subnet as the host.
For a Linux guest:
sudo ifconfig enp0s3f0 up sudo ifconfig enp0s3f0 192.168.1.2
where enp0s3f0 is the peer-to-peer interface, and 192.168.1.2 is an address in the same subnet as the host.