diff options
| author | Anthony Wang | 2024-12-11 14:02:56 -0500 |
|---|---|---|
| committer | Anthony Wang | 2024-12-11 14:02:56 -0500 |
| commit | 27f5a0cf4b65e73a5edb7838f66746ad025bba3f (patch) | |
| tree | 9b9f1a9af47064e50cfffa786d2131567107e02a | |
| parent | fb32540b9a9c56a8c4b310d0c938d00d227bcc59 (diff) | |
Suggest using XVM for Caddy and cgit
| -rw-r--r-- | content/posts/inessential-xvm.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/content/posts/inessential-xvm.md b/content/posts/inessential-xvm.md index b33570f..f0653ce 100644 --- a/content/posts/inessential-xvm.md +++ b/content/posts/inessential-xvm.md @@ -42,6 +42,8 @@ Your VM on XVM might feel suffocatingly small due to the RAM limitations, but yo Similarly, the XVM disk is pretty small and slow, but again, compression to the rescue! Btrfs with zstd compression can improve disk speeds slightly, at the expense of more CPU usage. +I'm running Caddy and cgit on my VM and they both work incredibly well with limited RAM. + ## And now time for something cursed! Before I wrote this guide, I wanted to make a VM on XVM but the VNC console was broken due to some expired TLS certificates. Thus, only the autoinstallers worked, since the broken VNC console made it basically impossible to interact with HVMs booted from the boot CDs (although you could still use the legacy Java version of the VNC console, which I didn't try). Instead, I came up with a different (cursed!) method: interrupt the autoinstaller and make it write a different OS to the VM's disk. Here's how it goes. |