@@ -139,13 +139,13 @@ At the moment, `urunc` is available on GNU/Linux for x86\_64 and arm64 architect
 In addition, the following table provides an overview of the currently
 supported VM/Sandbox monitors and unikernels:
 
-| Unikernel  | VM/Sandbox Monitor         | Arch         | Storage                       |
-|----------- |--------------------------- |------------- |------------------------------ |
-| Rumprun    | Solo5-hvt, Solo5-spt       | x86,aarch64  | Block/Devmapper               |
-| Unikraft   | QEMU, Firecracker          | x86          | Initrd, 9pfs                  |
-| MirageOS   | QEMU, Solo5-hvt, Solo5-spt | x86,aarch64  | Block/Devmapper               |
-| Mewz       | QEMU                       | x86          | In-memory                     |
-| Linux      | QEMU, Firecracker          | x86          | Initrd, Block/Devmapper, 9pfs |
+| Unikernel  | VM/Sandbox Monitor         | Arch         | Storage                                 |
+|----------- |--------------------------- |------------- |------------------------------           |
+| Rumprun    | Solo5-hvt, Solo5-spt       | x86,aarch64  | Block/Devmapper                         |
+| Unikraft   | QEMU, Firecracker          | x86          | Initrd, 9pfs                            |
+| MirageOS   | QEMU, Solo5-hvt, Solo5-spt | x86,aarch64  | Block/Devmapper                         |
+| Mewz       | QEMU                       | x86          | In-memory                               |
+| Linux      | QEMU, Firecracker          | x86          | Initrd, Block/Devmapper, 9pfs, Virtiofs |
 
 We plan to add support for more unikernel frameworks and other platforms too.
 Feel free to [contact](#Contact) us for a specific unikernel framework or similar
 
@@ -53,7 +53,7 @@ device. In addition, `urunc` can leverage [Qemu](https://www.qemu.org/)'s
 initrd option in order to provide the Unikernel with an initial RamFS
 (initramfs). However, [Qemu](https://www.qemu.org/) supports various ways to
 provide storage in VMs such as block devices through virtio-blk,
-shared-fs through 9p and virtio-fs and initramfs.
+shared-fs through 9pfs, virtiofs and initramfs.
 
 We plan to add support for all the above options, but as previously mentioned
 only Initramfs is supported for the time being.
 
@@ -59,7 +59,7 @@ Sandbox monitors, along with the unikernels that can run on top of them.
 | [Unikraft](./unikernel-support#unikraft)| [Qemu](./hypervisor-support#qemu), [Firecracker](./hypervisor-support#aws-firecracker) | x86          | Initrd, 9pfs |
 | [MirageOS](./unikernel-support#mirage)| [Qemu](./hypervisor-support#qemu), [Solo5-hvt](./hypervisor-support#solo5-hvt), [Solo5-spt](./hypervisor-support#solo5-spt) | x86, aarch64          | Block/Devmapper |
 | [Mewz](./unikernel-support#mewz)| [Qemu](./hypervisor-support#qemu) | x86 | In-memory |
-| [Linux](./unikernel-support#linux)| [Qemu](./hypervisor-support#qemu), [Firecracker](./hypervisor-support#aws-firecracker) | x86, aarch64 | Initrd, Block/Devmapper, 9pfs |
+| [Linux](./unikernel-support#linux)| [Qemu](./hypervisor-support#qemu), [Firecracker](./hypervisor-support#aws-firecracker) | x86, aarch64 | Initrd, Block/Devmapper, 9pfs, Virtiofs |
 
 <!-- ## urunc and the CNCF -->
 
 
@@ -12,6 +12,7 @@ We will be installing and setting up:
 - [CNI plugins](https://github.com/containernetworking/plugins)
 - [nerdctl](https://github.com/containerd/nerdctl)
 - [devmapper](https://docs.docker.com/storage/storagedriver/device-mapper-driver/) or [blockfile](https://github.com/containerd/containerd/blob/main/docs/snapshotters/blockfile.md)
+- [virtiofs](https://virtio-fs.gitlab.io/)
 - [Go [[ versions.go ]]](https://go.dev/doc/install)
 - [urunc](https://github.com/urunc-dev/urunc)
 - [solo5-{hvt|spt}](https://github.com/Solo5/solo5)
@@ -206,7 +207,6 @@ sudo ctr plugin ls | grep devmapper
 io.containerd.snapshotter.v1              devmapper                linux/amd64    ok
 ```
 
-
 ### Option 2: Blockfile
 #### Using blockfile snapshotter (alternative to devmapper)
 
@@ -289,6 +289,20 @@ sudo containerd config migrate > /etc/containerd/config.toml
    io.containerd.snapshotter.v1           blockfile               linux/amd64    ok
    ```
 
+## Install virtiofs
+
+As an alternative to 9pfs, `urunc` is able to spawn guests using virtiofs. For that
+purpose, we need to install virtiofsd under `/usr/libexec` where `urunc` expects to find
+the statically linked binary of `virtiofsd`. For easier installation, we have uploaded
+the respective binary in `https://s3.nbfc.io/nbfc-assets/github/urunc/bin/virtiofsd`.
+Therefore, the installation can easily take place with the following instructions:
+
+```
+wget https://s3.nbfc.io/nbfc-assets/github/urunc/bin/virtiofsd
+chmod +x virtiofsd
+sudo cp virtiofsd /usr/libexec/
+```
+
 ## Install urunc
 
 ### Option 1: Build from source
 
@@ -93,7 +93,7 @@ rootfs. For this scenario we can use both
 [bunny](https://github.com/nubificus/bunny) and
 [bunix](https://github.com/nubificus/bunix).
 
-> **NOTE**: In case the unikernel does not supports shared-fs (e.g. 9pfs), we
+> **NOTE**: In case the unikernel does not supports shared-fs (e.g. 9pfs/virtiofs), we
 > can only use block devices and for that reason we need to create the unikernel
 > container using devmapper as a snapshotter. In that way,`urunc` will use the
 > snapshot of the container's image and directly attach it to the unikernel as  a
 
@@ -92,7 +92,7 @@ Another important aspect is preparing the root filesystem (rootfs). Since we're
 booting a full Linux virtual machine, a proper rootfs must be provided. There
 are three main ways to do this:
 
-1. Using directly the rootfs of the container's image (requires devmapper or 9pfs).
+1. Using directly the rootfs of the container's image (requires either a block based snapshotter or 9pfs/Virtiofs).
 2. Creating a block image out of a container's image rootfs.
 3. Creating a initrd.
 
 
@@ -35,7 +35,7 @@ supports [Qemu](https://www.qemu.org/) and [AWS
 Firecracker](https://github.com/firecracker-microvm/firecracker). In both
 cases, it gets network access through virtio-net. In the case of storage, to
 the best of our knowledge [Unikraft](https://unikraft.org/) supports two
-options: a) 9pFS sharing a directory between the host and the unikernel and b)
+options: a) 9pfs sharing a directory between the host and the unikernel and b)
 initrd and therefore an initial RamFS.
 
 ### Unikraft and `urunc`
@@ -314,13 +314,13 @@ Focusing on the single-application notion of using the
 both [Qemu](https://qemu.org) and
 [Firecracker](https://github.com/firecracker-microvm/firecracker). For network,
 `urunc` will make use of virtio-net either through PCI or MMIO, depending on
-the monitor. In the case of storage, `urunc` can use initrd, virtio-block or 9pfs. In
-particular, `urunc` takes advantage of the extensive filesystem support of
-[Linux](https://github.com/torvalds/linux) and can directly mount containerd's
-snapshot directly to a [Linux](https://github.com/torvalds/linux) VM. This is
-only possible using devmapper as a snapshotter in containerd. For more
-information on setting up devmapper, please take a look on our [installation
-guide](../installation#setup-thinpool-devmapper).
+the monitor. In the case of storage, `urunc` can use initrd, virtio-block ,9pfs
+or Virtiofs. In particular, `urunc` takes advantage of the extensive filesystem
+support of [Linux](https://github.com/torvalds/linux) and can directly mount
+containerd's snapshot directly to a [Linux](https://github.com/torvalds/linux)
+VM. This is only possible using devmapper as a snapshotter in containerd. For
+more information on setting up devmapper, please take a look on our
+[installation guide](../installation#setup-thinpool-devmapper).
 
 For more information on packaging applications and executing them on top of
 [Linux](https://github.com/torvalds/linux) with `urunc` take a look at our