Search results

Ah, my bad, misunderstood you there. Yes, it's the third argument of the hook call, so $3 is the correct approach. First argument is the phase (job-start, job-end or job-abort), second the mode (stop, suspend or snapshot), and third one the vmid. Please also notice the usage of environment...

You can get the list of your containers with "pct list", the first column is the ID. In the web interface it's also the number that is displayed next to the name in the overview. Hope that helps :)

Have you installed the required Build-Dependencies? Working with a Debian package is usually done through build tools like debuild, dpkg-buildpackage or pbuilder/cowbuilder, and they check the set Build-Dependencies that you can find noted down in the debian/control file. Some documentation to...

Please check your sources.list entries, you seem to have configured the enterprise repository. Specifically that is probably within the /etc/apt/sources.list.d/pve-enterprise.list config file. See https://pve.proxmox.com/wiki/Package_Repositories how to adjust those entries for the...

Out of curiosity, do you remember what you googled with? Maybe we can try to improve on that grounds. And thanks for sending patches in already. :)

Please read the help of "qm help resize". For a start, there is no argument seperator supported through the double dash, and secondly, "Shrinking disk size is not supported." Please also read the documentation on Resize Disks in our wiki for that: https://pve.proxmox.com/wiki/Resize_disks

I take it that you've read our documentation on Cloud-Init Support? https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_cloud_init But ... public source code actually is available, see the git link in the footer of the forum pages. :) It's part of the qemu-server package. In general if you want...

Are you running a cluster? That message might be related to that the corosync between the nodes has communication issues. Can you check with `journalctl -u corosync` whether there are messages in there, and potentially restart corosync on the nodes?

Did you do a checksum check on the ISO you used? That sounds like you are using a corrupt image.

Mailinglists are known to deliver to multiple people, and thus seeing a list header decreases the score intentionally, not increase it. But yes, spammers are picking that up, they very often use spamassassin themself to see how they can "improve" their mails so that they get through easier. If...

Just to be on the safe side: Can you check the output of "pvecm status" and send that along?

You are running into the IFNAMSIZ limit of 16 characters here. There are two possibilities to get to a lower length: One easy one might be going with three digit vlan IDs here (because it's only a single character that you are too long). Or to tweak the network interface name. See the manpage...

It's noted down in the manpage of pvesh: There is a switch --output-format which takes an argument, including json or json-pretty. :) Hope that helps! Rhonda

I tried to reproduce this but the rules look fine. How did you test that it's still open from the internet? Is maybe routing coming through 172.16.0.0/16 via NAT? Notice that this just filters incoming traffic. Also depending on your environment, often REJECT rules are more helpful than DROP...