Search results

  1. J

    CPU numbers assigned to CT (container) are no longer numbered from 0

    Bump. No one? Or does it make sense to install prometheus-node-exporter at all to containers? Is it possible to get all linux containers data from host?
  2. J

    Container with custom mountoptions user_xattr

    Hello, How can I mount CT volume (not rootfs but 2nd disk) with mountoptions=user_xattr? If I set mp0 like this (content is from /etc/pve/lxc/100.conf) mp0: timemachine-lvm:vm-106-disk-0,mp=/media/TimeMachine,mountoptions=user_xattr,size=900G I get error vm 100 - unable to parse value of 'mp0' -...
  3. J

    CPU numbers assigned to CT (container) are no longer numbered from 0

    Hello, I updated PVE 7 & Ubuntu CTs by apt and after reboot I can see that now CTs can see host CPU numbers. Previously, CPU numbers in CTs were starting always from 0 and continue like 1,2,3... CT with correct numbers: pveversion - pve-manager/7.3-6/723bb6ec (running kernel: 5.15.85-1-pve)...
  4. J

    Can not change CIDR param under IPSet through API using HTTP PUT

    Ah, yes. It's just a little bit confusing but now it makes sense. Especially when I take into account this part So, delete and recreate whole CIDR is the only way. Thank you and have a nice day. J.
  5. J

    Can not change CIDR param under IPSet through API using HTTP PUT

    Here. I sent URL to this page in first post also. Read the Description please. Regards, J.
  6. J

    Can not change CIDR param under IPSet through API using HTTP PUT

    It seem like that but in API viewer there is PUT method with description that you actually can update IP. It seems to me that either documentation or API implementation in this case is wrong.
  7. J

    Can not change CIDR param under IPSet through API using HTTP PUT

    Unfortunately, there is nothing like alias. Only cidr param exists directly as IP/mask which is in fact also name of the CIDR range. Check API viewer I post before. You can test it with HTTP method DELETE which you are sending directly to /cluster/firewall/ipset/management/192.168.251.0/24 And...
  8. J

    Can not change CIDR param under IPSet through API using HTTP PUT

    Hello, I searched for some time and checked docs and API viewer here: API viewer - PUT - /api2/json/cluster/firewall/ipset/{name}/{cidr} But I'm not able to change my CIDR range when already exists using HTTP PUT API call. There is no issue create CIDR range (in already created IPSet...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!