Cause: vzdump for unprivileged containers runs tar through lxc-usernsexec, which remaps uid/gid 0 → 100000 for the duration of the archive
When Proxmox runs the job itself (GUI/scheduler), the worker's cwd is /, which is world-traversable, so...
Could you share:
~# efibootmgr -v
Could it be related to:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#GRUB_Might_Fail_To_Boot_From_LVM_in_UEFI_Mode
?
From which version you upgraded?
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
Yes, I mean the same. The server aren't bootet and was not available on the network. Not with the interface for clustercommunication, nor with the openvswitch-bonds…
I was able to complete the full benchmark this morning on Node1, a Dell R760, and locally on the TrueNAS Enterprise system. I was not able to complete the full run on Node2, but I did run a smaller 100 GiB test last night, which is attached...
Hallo,
seit einigen Tagen funktioniert mein Web-Zungang nicht mehr, d.h. es wird kein Bild aufgebaut.
Der ssh-Zugang ist möglich. (Proxmox-Version 8.4.17)
kann mir jemand bei der Lösung helfen?
Gruß puba
Cause: vzdump for unprivileged containers runs tar through lxc-usernsexec, which remaps uid/gid 0 → 100000 for the duration of the archive
When Proxmox runs the job itself (GUI/scheduler), the worker's cwd is /, which is world-traversable, so...
Cause: vzdump for unprivileged containers runs tar through lxc-usernsexec, which remaps uid/gid 0 → 100000 for the duration of the archive
When Proxmox runs the job itself (GUI/scheduler), the worker's cwd is /, which is world-traversable, so...
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
Hello,
I am seeing a very strange error when running backups (via vzdump) from command line instead of via the GUI.
I have created a backup job on my datacenter:
vzdump: backup-a4770096-56f9
schedule weekly
compress zstd...