diff options
| author | Jasper Ras <jras@hostnet.nl> | 2025-03-20 11:07:49 +0100 |
|---|---|---|
| committer | Jasper Ras <jras@hostnet.nl> | 2025-03-20 11:07:49 +0100 |
| commit | 80ccf68f55dbb70d7e5ed52ee95b3c9d1b6ce264 (patch) | |
| tree | 93e28e85ab70052aa6f577998ec7dc1f413b40c0 /0 Inbox/Virtual block device per QEMU.md | |
| parent | 9642cd7ae24f0ba79ce5647c709b35ae8f06a285 (diff) | |
vault backup: 2025-03-20 11:07:48
Diffstat (limited to '0 Inbox/Virtual block device per QEMU.md')
| -rw-r--r-- | 0 Inbox/Virtual block device per QEMU.md | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/0 Inbox/Virtual block device per QEMU.md b/0 Inbox/Virtual block device per QEMU.md deleted file mode 100644 index 6e612d6..0000000 --- a/0 Inbox/Virtual block device per QEMU.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -tags: - - linux - - filesystem -references: - - https://wiki.qemu.org/Documentation/9p_root_fs ---- -**Transparency and Shared File Access**: The classical way to deploy a virtualized OS (a.k.a. "guest") on a physical machine (a.k.a. "host") is to create a virtual block device (i.e. one huge file on host's filesystem) and leave it to the guest OS to format and maintain a filesystem ontop of that virtualized block device. As that filesystem would be managed by the guest OS, shared file access by host and guest simultaniously is usually cumbersome and problematic, if not even dangerous. A 9p passthrough-filesystem instead allows convenient file access by both host and guest simultaniously as the filesystem is just a regular subdirectory somewhere inside host's own filesystem.
\ No newline at end of file |