Whilst using qm importdisk you might experience the following problem: root@hv:~# qm importdisk 123 clients-disk.vmdk nas03 importing disk ‘clients-disk.vmdk’ to VM 123 … iscsiadm: No
# pvesm list nasX Volid Format Type Size VMID nasX:base-9000-disk-0 raw images 3758096384 9000 nasX:vm-112-disk-0 raw images 214748364800 112 nasX:vm-125-disk-0 raw images 268435456000 125 nasX:vm-137-disk-0
Woke up this morning to this after enlarging a big disk yesterday: The computer then tries to boot but fails with a Kernel panic: Doing
Whilst trying to restore a normal backup job from one node to another in another part of the cluster, the following is experienced: Warning: volblocksize
Yep, this is apparently normal, mostly if you had data on the drive before, see: https://forum.proxmox.com/threads/proxmox-installation-stuck-on-3-creating-lvs-please-help-guys.94650/
Introduction Proxmox VE hypervisors need to be monitored. Some of the key items you could monitor are: Disk I/O Wait time CPU temperature Smart Status
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
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
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
This is easy. Just install UTM then select your Debian ISO. UTM: https://mac.getutm.app/ Debian: https://cdimage.debian.org/debian-cd/current/arm64/iso-cd/ Install Cinnamon sudo apt -y install cinnamon Install SSH sudo
Copyright 2024 © All rights Reserved