Anatomy of (another) Proxmox hypervisor reboot gone wrong
Introduction I hate Proxmox hypervisor reboots. Any hypervisor reboot is a bad thing, because at the end of the day you’ll have VMs on the
proxmox
Proxmox Mail Gateway Quick Start Guide
Introduction Writing a quick start article for an anti-spam gateway is not trivial. The fact of the matter is everyone’s idea on how to use
Proxmox Hypervisor Reboot: DMAR-IR: [Firmware Bug]: ioapic 3 has no mapping iommu, interrupt remapping will be disabled
A while ago I rebooted a Proxmox server in cluster and got this scary message: DMAR-IR: [Firmware Bug]: ioapic 3 has no mapping iommu, interrupt
Anatomy of Proxmox File Systems Crashes – stuck on `random: crng init done` again?
Proxmox disks sometimes break. It’s not supposed to, but when it happens it can be devastating. I only use defaults. Nothing fancy. Whatever the operating
Proxmox Backup Servers offline after upgrade from 3.1 to 3.2 (large drives)
On both my PBS servers this morning I’m getting the following. Both PBS server has more than 2 TB drives, which might be of relevant.
How do you determine if a Proxmox linked clone is attached to a disk?
Sometimes you want to get rid of a VM template. In doing so, you might encounter the following issue: TASK ERROR: base volume ‘nas02:base-9403-disk-0’ is
TrueNAS Scale on Proxmox VM and iSCSI with directly connected driver error
I’ve seen the below recently in our logs. The errors doesn’t stop anything from happening but it’s still concerning: Apr 28 02:00:19 hv11 QEMU[3161]: kvm:
Anatomy of a Proxmox server host’s VM storage disk crash
Introduction Every disk crash is different. The point being a disk crash should never happen, so when it does, the results and probability of recovery
Dealing with Disk I/O Error with TrueNAS Scale with Passthrough and Proxmox
NAS refuses to start up. Icon has exclamation and triangle. Hover shows I/O error. Examine /var/log/syslog, search “Error IO”. Apr 3 16:21:14 hvX kernel: [4948799.898572]
service qemu-guest-agent start timeout in Proxmox environment
TL;DR You don’t have Qemu Guest Agent enabled on the VM. The default is to have it disabled. Longer explanation At times on a new