From d0d70d4aa60a009b29ff5a0b96486e6d4db4daa1 Mon Sep 17 00:00:00 2001 From: Eric Chan Date: Wed, 7 Feb 2024 18:54:11 +1100 Subject: [PATCH] clarify where virtio blk device is mounted to --- examples/virtio_blk/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/virtio_blk/README.md b/examples/virtio_blk/README.md index b0324e77..e4fc1fda 100644 --- a/examples/virtio_blk/README.md +++ b/examples/virtio_blk/README.md @@ -32,7 +32,7 @@ This example consist of a guest linux client VM that talks virtIO with a backend When you boot the example, you will see different coloured output for each guest. The block driver VM in red will boot first. When it is ready, the client VM in green will boot. -After the block client VM boots it will attempt to mount the virtIO block device `/dev/vda`. The block device contains an ext4 filesystem allowing us to test it using block benchmark programs like `postmark`, which has been included in `/root`. +After the block client VM boots it will attempt to mount the virtIO block device `/dev/vda` into `/mnt`. The block device contains an ext4 filesystem allowing us to test it using block benchmark programs like `postmark`, which has been included in `/root`. Client VM requests to the virtIO block device will print out debugging messages. ```