meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| vm:proxmox:kvm:linux [2025/01/06 21:27] – niziak | vm:proxmox:kvm:linux [2026/07/08 20:55] (current) – niziak | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Linux Guests ====== | ====== Linux Guests ====== | ||
| + | |||
| + | Enable WriteBack to group small writes into batches. | ||
| + | |||
| + | ===== 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 | ||
| + | * metada chunk is 16kb ('' | ||
| * 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: | Block sizes: | ||
| - | * Default '' | + | * Default '' |
| - | * Latest Proxmox creates '' | + | * Latest Proxmox creates '' |
| So it is best to fit guest block sizes into ZFS block (16k) sizes: | 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, | + | * btrfs mount options: |
| - | * ext4 mount options: -o noatime, | + | |
| + | | ||
| + | * volblocksize=16kB '' | ||
| + | * volblocksize=64kB '' | ||
| + | * volblocksize=128kB '' | ||
| + | | ||
| + | * xfs: | ||
| + | * mkfs.xfs options: '''' | ||
| + | * xfs mount options: '' | ||