Search results

I'm encountering the same issue today: # pveam download local debian-13-standard_13.1-2_amd64.tar.zst downloading http://download.proxmox.com/images/system/debian-13-standard_13.1-2_amd64.tar.zst to /var/lib/vz/template/cache/debian-13-standard_13.1-2_amd64.tar.zst --2025-10-24 22:42:32--...

Sorry if I may not fully understand your meaning, but: Yes. Once power is restored, all components start simultaneously, including the switch, router, WAN gateway, and the three nodes. To the best of my understanding the switch takes some time to start to forward the ethernet packets. But, once...

Thank you, Fabian, for the valuable information. I have now a better understanding of the startup process. Indeed, the C node does not have any guests. It is a less powerful node (I3 13100T with 8GB RAM) primarily designated for backups (PBS) and as a third witness for Corosync. I might...

I had 2 power outages in the last days. In both of them one or more LXC containters failed to start. I don't intend to keep restarting the cluster, but I want the assurance that all services will come back online after a power failure. Adding a delay seems to be a workaround. I wish to bring...

I have a 3-node cluster running PVE 8.2.4 and recently observed an intermittent issue that occurs infrequently. SOMETIMES after a power outage, SOME LXC containers with "Start at Boot=Yes" fail to start. Upon reviewing the logs, in a task called "Bulk start VMs and Containers", I encountered...

For anyone else interested in this topic, I've put a quick example of how to set up an OpenWRT LXC instance here: https://github.com/fdcastel/Proxmox-Automation?tab=readme-ov-file#openwrt

@shodan. You can use https://gist.github.com to avoid these annoyances. ;) One example. As a bonus, it also has the benefit of maintaining a history of revisions, allowing you to track your progress throughout your coding journey. Keep going with your excellent work in the finest tradition...

I can't think of a better one than Reading The Fine Manual: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_emulated_devices_and_paravirtualized_devices

For those interested, I have compiled a set of instructions and scripts to address this problem, available here: https://github.com/fdcastel/Hyper-V-Automation#windows-prepare-a-vhdx-for-qemu-migration The provided scripts automate the process of taking a VHDX file, installing VirtIO drivers...

For now, I'm using a daily cron job: cat > /etc/cron.daily/update-pbs-certificates <<'EOF' #!/bin/bash diff /etc/pve/nodes/$HOSTNAME/pveproxy-ssl.pem /etc/proxmox-backup/proxy.pem if [ $? -ne 1 ]; then cp /etc/pve/nodes/$HOSTNAME/pveproxy-ssl.pem /etc/proxmox-backup/proxy.pem cp...

This didn't work. I tried with: NODE=$(hostname) ln -sf /etc/pve/nodes/${NODE}/pveproxy-ssl.pem /etc/proxmox-backup/proxy.pem ln -sf /etc/pve/nodes/${NODE}/pveproxy-ssl.key /etc/proxmox-backup/proxy.key chgrp -h backup /etc/proxmox-backup/proxy.key /etc/proxmox-backup/proxy.pem systemctl reload...

Cool! But if you are using Proxmox, you may want to look into ZFS. I've been using it for years and have never looked back. Tip: When building a new system, always keep a record of every command you use (at least, the ones that worked ;)). It may seem like a daunting task at first, but it...

Your changes replaced the 'local-zfs' storage with 'local.' I don't have an equivalent system here to test it, but it seems okay to me. This is the expected behavior. The script uses cloud-init to initialize the VM. And then it uses cloud-init Power State Change module to reboot after all...

Sorry, Carl. Up until now, I've only used Proxmox VE with ZFS filesystems. From the error message, I presume you're using something different? LVM, maybe?

Coming late to the party, but for whoever is interested, I've been keeping some useful scripts here: https://github.com/fdcastel/Proxmox-Automation

For future reference: # List all backup jobs pvesh ls /cluster/backup # Create a daily backup at 20:00 for VMs 213,214 and 215 to storage MY-PBS pvesh create /cluster/backup --id backup-daily --schedule 20:00 --storage MY-PBS --vmid 213,214,215 # Get the configuration of a backup job pvesh...

Studying the code, to the best of my understanding: - There is a pve-daily-update.service; - Which runs the script /usr/bin/pveupdate (once a day, around 1AM, with a randomized offset of 5h); - Which may or may not request an ACME certificate renew, based on elapsed days since the last renew...

Or, as an alternative solution, can I create a symlink between /etc/pve/nodes/${NODE}/pveproxy-ssl.{pem|key} and /etc/proxmox-backup/proxy.{pem|key} ?

Short version: I have ACME certificates configured in my Proxmox. And everything is working perfectly. Now, how can I run a custom script when the certificate is renewed? Long version: In PBS documentation, we learn that we can use: NODE=$(hostname) cp...

Just being picky. You know... The less, the better. :) Changing a system just to query a single option seems excessive. That's why I'm interested in alternative ways to get this.