Recent content by William Edwards

I did not read the documentation correctly! Thank you.

https://pve.proxmox.com/pve-docs/chapter-qm.html says: The `qmshutdown` task is ended after 'Shutdown timeout' (as the VM did not respond to the ACPI signal). However, unlike the documentation says, the VM is not force stopped. It still has the state `running`. The task log is attached...

On a 12-node cluster, due to a backup issue, several CT's RBD images became read-only. Issue: backups caused RBD images to become read-only On all nodes, a backup job ran at the time of the issue. The backup jobs on two nodes (`g04s01` and `g04s07`) failed. On `g04s07`, the following was...

I might use NFS for snippets and write them there. Thanks for your comments!

So I'll have to create a user-data snippet per VM. Would be useful to do this with the PVE API, as others think too: https://forum.proxmox.com/threads/creating-snippets-using-pve-api.54081/

I would like to supply custom user data for Cloud-init using `--cicustom`. I would like to re-use a single snippet for all VMs. However, the default user data contains the `hostname` key. Is it possible for Proxmox to substitute it dynamically?

I am aware, but the question is if one already exists. Building one myself is not a huge hassle, but not necessarily preferred.

Does a Cloud-init image exist for Proxmox Mail Gateway?

How do I stop PMG from removing the custom `source` line -which is supported according to the documentation- in `/etc/network/interfaces`? Context: I have some custom interfaces that PMG should not manage. `/etc/network/interfaces` says: The documentation at...

Another data point: Before last week, this issue occurred only on machines with MariaDB and Debian 11. Debian 10 machines are not affected. Last week, for the first time, the issue occurred on a Debian 11 machine without MariaDB.

Why?

VM configs (`/nodes/{node}/qemu/{vmid}/config`) contain configuration strings, such as: local-zfs:vm-100-disk-1,aio=native,cache=unsafe,discard=on,iops_rd=20,iops_rd_max=30,iops_wr=20,iops_wr_max=30,iothread=1,mbps_rd=5,mbps_rd_max=10,mbps_wr=5,mbps_wr_max=10,replicate=0,ro=1,size=20G,ssd=1...

I'm seeing this issue on two VMs: One runs Debian 11 with kernel 5.10.0. The VM was installed 13 days ago. The issue occurred only once on this VM. One runs PMG 7 (Debian 11) with kernel 5.15.53. 4 days ago, the VM was upgraded from PMG 6 to PMG 7. The issue started occurring on the 3rd day...

Virtualisation Resource Distributor 2.0 has been released. It comes with a CLI tool to manage zones and nodes, and more!

Hint: NDP/ARP