infra-proxmox-qemu-windows-storagelisted

Use when a Windows VM on Proxmox with QEMU and ZFS zvol storage is slow, wastes pool space, or will not boot after a disk change - moving a boot disk to virtio-scsi without INACCESSIBLE_BOOT_DEVICE 0x7B or recovery 0xc0000001, choosing virtio-scsi over SATA/AHCI, sizing volblocksize against the guest's write size, discard and ssd emulation, why TRIM frees nothing while a snapshot exists, why BitLocker makes ZFS compression useless, and iothreads. Covers QEMU/KVM guests only, not OpenVMM. Prefer this over reasoning from read-modify-write or hand-rolling a diskspd run.
bitranox/bitranox-skills · ★ 1 · AI & Automation · score 57

Install: claude install-skill bitranox/bitranox-skills

# Windows guest storage on Proxmox, QEMU and ZFS Scoped to **QEMU/KVM** guests. Proxmox can also run OpenVMM guests, which present storvsc, NVMe and virtio-blk instead, so the controller half of this does not transfer: | Applies to | Transfers to OpenVMM | |---------------------------------------------------------------------------------------------------|-----------------------------| | Controller choice, `scsihw`, scsi-index-to-PCI-address mapping, `vioscsi`, AHCI, `iothread` | No - different device model | | `volblocksize`, `discard`/TRIM, snapshots pinning trimmed blocks, BitLocker, the benchmark method | Yes - ZFS and guest side | Numbers below are measurements on a single-vdev NVMe pool, `ashift=12`, QEMU 11, DiskSpd 2.2, 16 threads at QD8, ARC evicted cold, three interleaved reps. Treat them as directions with an order of magnitude, not as constants. ## The false signals | Symptom | Obvious reading | What it usually is | |--------------------------------------------------|-----------------------------|---------------------------------------------------------| | 0x7B / 0xc0000001 after moving to virtio-scsi | driver not installed | driver fine; the target scsi INDEX was never enumerated | | `vioscsi Start=0`, controller Status OK | ready to move the boot di