aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSilvio Rhatto <rhatto@riseup.net>2024-08-01 23:46:58 -0300
committerSilvio Rhatto <rhatto@riseup.net>2024-08-01 23:46:58 -0300
commitbe9923a4c91b914f963e653fe7132d752745480d (patch)
treede7ef30eb1e53482018fa8092268d865a8cc85b0
parentbe3a1a035daa438bac8226ef3303f4dea269ac5f (diff)
downloadkvmx-be9923a4c91b914f963e653fe7132d752745480d.tar.gz
kvmx-be9923a4c91b914f963e653fe7132d752745480d.tar.bz2
Docs: updates
-rw-r--r--DOCS.md63
1 files changed, 37 insertions, 26 deletions
diff --git a/DOCS.md b/DOCS.md
index 145f9f2..893eaf2 100644
--- a/DOCS.md
+++ b/DOCS.md
@@ -46,42 +46,49 @@ Misc documentation on kvmx and QEMU.
Nowadays this can be done with `kvmx growpart <device> <partition> <additional_size>`, but
here goes some manual procedures if needed.
-* Image resize action, doing something like this, thanks to
- https://ahelpme.com/linux/online-resize-of-a-root-ext4-file-system-increase-the-space/
+Image resize can be manually done with a procedure like this thanks to [these docs][]:
- # poweroff
- kvmx poweroff $guest
+ # poweroff
+ kvmx poweroff $guest
- # resize image
- qemu-img resize `kvmx list_image $guest` +5G
+ # resize image
+ qemu-img resize `kvmx list_image $guest` +5G
- # power up
- kvmx up $guest
+ # power up
+ kvmx up $guest
- # ensure parted is installed
- #sudo apt-get install -y parted
- kvmx ssh $guest sudo apt-get install -y cloud-guest-utils
+ # ensure parted is installed
+ #sudo apt-get install -y parted
+ kvmx ssh $guest sudo apt-get install -y cloud-guest-utils
- # resize virtual machine root fs - while the partition is mounted!
- # this parted command currently need to be done manually
- #echo resizepart 2 -1 | kvmx ssh $guest sudo parted /dev/vda
+ # resize virtual machine root fs - while the partition is mounted!
+ # this parted command currently need to be done manually
+ #echo resizepart 2 -1 | kvmx ssh $guest sudo parted /dev/vda
- # See https://unix.stackexchange.com/questions/373063/auto-expand-last-partition-to-use-all-unallocated-space-using-parted-in-batch-m
- # https://unix.stackexchange.com/questions/190317/gnu-parted-resizepart-in-script#202872
- # https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1270203
- # https://techtitbits.com/2018/12/using-parteds-resizepart-non-interactively-on-a-busy-partition/
- # https://serverfault.com/questions/870594/resize-partition-to-maximum-using-parted-in-non-interactive-mode
- #kvmx ssh $guest sudo parted /dev/vda resizepart 2 -1 Yes
- kvmx ssh $guest sudo growpart /dev/vda 2
+ # See https://unix.stackexchange.com/questions/373063/auto-expand-last-partition-to-use-all-unallocated-space-using-parted-in-batch-m
+ # https://unix.stackexchange.com/questions/190317/gnu-parted-resizepart-in-script#202872
+ # https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1270203
+ # https://techtitbits.com/2018/12/using-parteds-resizepart-non-interactively-on-a-busy-partition/
+ # https://serverfault.com/questions/870594/resize-partition-to-maximum-using-parted-in-non-interactive-mode
+ #kvmx ssh $guest sudo parted /dev/vda resizepart 2 -1 Yes
+ kvmx ssh $guest sudo growpart /dev/vda 2
- kvmx ssh $guest sudo resize2fs /dev/vda2
- kvmx ssh $guest sudo touch /forcefsck
- kvmx restart $guest
+ kvmx ssh $guest sudo resize2fs /dev/vda2
+ kvmx ssh $guest sudo touch /forcefsck
+ kvmx restart $guest
+
+[these docs]: https://ahelpme.com/linux/online-resize-of-a-root-ext4-file-system-increase-the-space/
## Folder sharing
### With virtio and 9p
+* Status: works on kvmx.
+* Limitations: performance is low on Linux (as of 2024-08-01), due to a
+ limitation in the kernel.
+
+#### About
+
References on virtio:
* [Virtio on Linux — The Linux Kernel documentation](https://www.kernel.org/doc/html/v6.8/driver-api/virtio/virtio.html)
@@ -95,11 +102,15 @@ Some references on 9p folder sharing:
* [Documentation/9psetup - QEMU](https://wiki.qemu.org/Documentation/9psetup)
* [v9fs · GitHub](https://github.com/v9fs)
+#### Performance
+
Performance limitations:
* [linux/net/9p/trans_virtio.c at master · torvalds/linux · GitHub](https://github.com/torvalds/linux/blob/master/net/9p/trans_virtio.c)
- * [linux/net/9p/trans_virtio.c at master - L803 · torvalds/linux · GitHub](https://github.com/torvalds/linux/blob/master/net/9p/trans_virtio.c#L803)
- * [History for net/9p/trans_virtio.c - torvalds/linux · GitHub](https://github.com/torvalds/linux/commits/master/net/9p/trans_virtio.c)
+ * Limits still present at `trans_virtio.c` (as of 2024-08-01)
+ [linux/net/9p/trans_virtio.c at master - L803 · torvalds/linux ·
+ GitHub](https://github.com/torvalds/linux/blob/master/net/9p/trans_virtio.c#L803)
+ * [History for net/9p/trans_virtio.c - torvalds/linux · GitHub](https://github.com/torvalds/linux/commits/master/net/9p/trans_virtio.c)
* [Can not set high msize with virtio-9p (Was: Re: virtiofs vs 9p performan](https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06343.html)
* [Re: Can not set high msize with virtio-9p (Was: Re: virtiofs vs 9p perfo](https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06850.html)