Search results

After restarting pve-ha-lrm ha service is working

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

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

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...

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

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

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...

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

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...

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

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

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:

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...

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

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

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"...

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"...

@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

I have created PVE user and its API Token for a user manish@pve in proxmox cluster running version 7. When i assign user permission to VM as attached in screenshot1, the permission are showing with propagate=Yes whereas if I assign token permission to the same VM with same role, it is showing...

I have create an API Token and wanted to access the spice-config through an API curl -f -s -S -k --header 'Authorization: PVEAPIToken=manish@pve!monitoring=b9b0c035-3fe2-46e9-9374-299854b44b12' "https://inc1pve53:8006/api2/spiceconfig/nodes/inc1pve53/qemu/111/spiceproxy" when I do this curl...