Search results

  1. E

    Proxmox VE 8.2 released!

    Yes you are right, missed in between lots of other stuff to read. Anyhow better would be that it shall automatically update the /etc/network/interface files over a reboot to reflect the changes (if possible)
  2. E

    Proxmox VE 8.2 released!

    There is an issue with the upgrade. Post upgrade network interfaces names have change pre upgrade ens4f0 Post upgrade ens4f0np0 This has caused all user created bonds to go down Needs to modify the network config file to bring up the nodes
  3. E

    Ha not working proxmox 8.0.3

    After restarting pve-ha-lrm ha service is working
  4. E

    Ha not working proxmox 8.0.3

    Vm configured in ha is not starting but when I remove the configuration from ha and then run it manually, vm is running
  5. E

    Network down after upgrade to proxmox 8 beta

    Issue is resolved deleting ntpsec file from if-up.d folder solved it
  6. E

    Network down after upgrade to proxmox 8 beta

    Dear All, We have upgraded our servers to proxmox 8 beta version and after installation everything was working fine and once we have rebooted the hardware It was showing cleaning orphan node and was stuck there for quite long Initially we thought filesystem is corrupted and it will clean and...
  7. E

    Invalid/wrong statistics during migration

    If that is the case, the word "of" in the sentence is misleading 147Gb of 97Gb Stating clearly is better I believe Memory state is lagging, transfered:147GB, Actual Required: 96GB
  8. E

    Invalid/wrong statistics during migration

    I know the reason, why it is happening, I am only asking why it is showing wrong transferred 147.2 GiB of 96.1 GiB VM-state, 274.3 MiB/s 147 out 96 is not possible
  9. E

    Invalid/wrong statistics during migration

    2022-09-05 08:07:51 migration active, transferred 146.3 GiB of 96.1 GiB VM-state, 412.7 MiB/s 2022-09-05 08:07:52 migration active, transferred 146.7 GiB of 96.1 GiB VM-state, 335.0 MiB/s 2022-09-05 08:07:53 migration active, transferred 147.0 GiB of 96.1 GiB VM-state, 315.0 MiB/s 2022-09-05...
  10. E

    Invalid/wrong statistics during migration

    While migrating a VM from one node to another, the statistics are shown, which are wrong, please check attachment
  11. E

    (Unofficial) Proxmox VE VDI Client - Initial Release!

    Hi, I want to know if a user is allowed to access 3 VM's in cluster, I want to restrict access to specific VM if he access from specific machine but allow him to access all VM's if accessed from another system In short IP based/configuration based filtering based on system local config Feature...
  12. E

    Proxmox VE 7.2 released!

    Thanks checked the git, bump version is pending Tried erasure code pool, performance is better than RF=3 in benchmark, testing more on load and per VM
  13. E

    Proxmox VE 7.2 released!

    Hi there are typo errors in the documentation instead of "pveceph" it is written "pceveph" in many places. You may please correct that
  14. E

    Query Regarding API Permission

    user:manish@pve:1:0:::::: token:manish@pve!monitoring:0:1:: user:root@pam:1:0:::manish@istrac.gov.in::x: group:VMUSERS:manish@pve:: acl:1:/storage/local:manish@pve!monitoring:Administrator: acl:1:/vms/111:manish@pve,manish@pve!monitoring:PVEVMUser:
  15. E

    Query Regarding API Permission

    Is it because of this " API tokens come in two basic types: Separated privileges: The token needs to be given explicit access with ACLs. Its effective permissions are calculated by intersecting user and token permissions." " If that is the case, its my bad that I did not see that in the...
  16. E

    [SOLVED] Direct Kernel Boot

    This looks like metadata of the VM, what is the format of disk?? if disk format is qcow2, raw or can be converted to these formats, VM can be ported to Proxmox
  17. E

    Query Regarding API Permission

    It can be clearly seen that after add users to the VM permission then only VM.Audit:1 and many others are showing permissions
  18. E

    Query Regarding API Permission

    With both user and API permissions assigned to VM curl -f -s -S -k --header 'Authorization: PVEAPIToken=manish@pve!monitoring=b9b0c035-3fe2-46e9-9374-299854b44b12' "https://172.19.200.121:8006/api2/json/access/permissions"...
  19. E

    Query Regarding API Permission

    With API token permission only assigned to the VM curl -f -s -S -k --header 'Authorization: PVEAPIToken=manish@pve!monitoring=b9b0c035-3fe2-46e9-9374-299854b44b12' "https://172.19.200.121:8006/api2/json/access/permissions"...
  20. E

    [SOLVED] Spiceproxy via API

    @fabian, yes I am able to do it now, able to access my VM with API token without even going to WebUI Thanks for the help

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!