meta data for this page
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
vm:proxmox:kvm:linux [2024/05/31 13:46] – created niziak | vm:proxmox:kvm:linux [2025/03/04 15:20] (current) – niziak | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Linux Guests ====== | ====== Linux Guests ====== | ||
+ | |||
+ | ===== Filesystem ===== | ||
+ | |||
+ | If ZFS is used on host (CoW filesystem) using CoW filesystem on guest generates overhead. Better is to use simple XFS or Ext4 if BTRFS snapshot and subvolumes functionality is not needed in guest. | ||
Linux Guest on BTRFS: | Linux Guest on BTRFS: | ||
+ | |||
* BTRFS with single copy of meta, system and data | * BTRFS with single copy of meta, system and data | ||
* I/O is better on modern guest Kernel 6.1 (vs 5.10) | * I/O is better on modern guest Kernel 6.1 (vs 5.10) | ||
* I/O is better whem VM storage is "no cache" | * I/O is better whem VM storage is "no cache" | ||
- | | + | |
- | * With " | + | * With " |
+ | |||
+ | Block sizes: | ||
+ | |||
+ | * Default '' | ||
+ | * Latest Proxmox creates '' | ||
+ | |||
+ | So it is best to fit guest block sizes into ZFS block (16k) sizes: | ||
+ | |||
+ | * mkfs.btfs options: –nodesize 16k | ||
+ | * btrfs mount options: -o noatime | ||
+ | * mkfs.ext4 options: -b 4096 -E stride=4, | ||
+ | * ext4 mount options: -o noatime, | ||