Required components
To support virtual filesystems in a QNX Hypervisor system, you must have certain components in your guest and host images, and configure the virtio-fs vdev in the guest's VM.
Host components
To share host directories with guests through virtual filesystems, your hypervisor host buildfile must include the following components in the host image:
- the shared object for the virtual filesystem vdev, virtio-fs.so
- for each VM that hosts a guest that wants to access host directories, you must include the virtio-fs vdev. For information on configuring this vdev, see vdev virtio-fs.
- the path to the configuration file (*.qvmconf file) for each VM
- the FUSE filesystem daemon, passthrough, and the supporting protocol library, libfuse3.so
- the utility for launching this daemon, fuselauncher. This utility must be launched at host startup by the virtio-fs vdev, so the virtual filesystem is available when the guest's VM starts.
Configurationsection of the QNX Hypervisor User's Guide.
Guest components
The virtio-fs vdev is a para-virtualized device. It runs in a hypervisor VM, but it doesn't emulate a physical device that stores files. Instead, it provides the filesystem functionality that an OS would provide in a nonvirtualized environment.
Because the vdev is a para-virtualized device, the guest must know that it is running in a virtualized environment and
add the VirtIO filesystem kernel driver (e.g., virtio-fs.ko for an Android or Linux guest) to its image.
See Building guests
in the QNX Hypervisor User's Guide for more guidelines.
