Recent content by chOzcA75vE0poCY0F6XC

Very cool, and thank you for sharing. Only after looking a bit more closely I noticed you used a lot of AI to create this. That's okay, but then also add a disclaimer somewhere that you got a lot of help from AI. That way people know what to expect from the project.

Amazing! Thank you.

Still a thing on PVE 7.2-1 on ZFS pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-6 pve-kernel-helper: 7.2-6 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.39-1-pve: 5.15.39-1 pve-kernel-5.15.35-2-pve: 5.15.35-5...

Moin, Hier dasselbe Problem. Lokale Nutzer können erfolgreich schreiben, und änderungen über andere clients verlaufen problemlos. Proxmox Backup Server meldet sich aber mit EACCES: Permission denied. Mir ist es nicht wichtig das der Speicher schnell ist. Mir ist wichtig das ich einen extra...

Dominic hasn't been online on this forum since Aug 11, 2021, maybe he took some very long vacation and forgot to mention this issue to other staff members?

I had hoped for a nice little surprice with the release of PVE 7.1, but sadly, no change. pve-manager/7.1-5/6fe299a0

it probably won't get fixed, no dev responses at all. Sadly, I am not a dev either, so I can't fix this myself.

Still not working for me. VM's are properly showing disk IO, LXC is not.

still an issue on proxmox 7, upgraded my recently reinstalled system. The other system with proxmox 6.4 still does not show disk io graphs.

You are right, my machine shows the same behavior. Load average seems accurate per container, but CPU shows one of the host CPU load instead of the LXC CPU load. It did work with the latest 6.4 version for me as well, but doesn't work anymore with 7.

Did you reboot? It works with a reboot over here. cat /lib/systemd/system/lxcfs.service [Unit] Description=FUSE filesystem for LXC ConditionVirtualization=!container Before=lxc.service Documentation=man:lxcfs(1) [Service] ExecStart=/usr/bin/lxcfs /var/lib/lxcfs -l KillMode=process...

Hello, this is still an issue for me as well, and someone else I know. ZFS on root install, was an issue before with GRUB-boot and with a fresh UEFI boot it's still not working.

Same issue here. Starts with 14336MB of RAM, but does not start with 16384 and higher with the QM command and Proxmox web UI. The raw command works fine in the command line. Is more information necessary for troubleshooting?

The reporting in the proxmox web UI isnt as accurate, no IP addresses as well, and to cite the Proxmox docs: "To properly shutdown the guest, instead of relying on ACPI commands or windows policies" and "To freeze the guest file system when making a backup (on windows, use the volume shadow...

@radensb Thank you, I passed two SAS HBA's in IT mode with firmware ROM, one for my proxmox machine, one for a VM itself. When I set those up a few weeks ago, everything went fine, they had their own device ID. After I changed the SSDs for bigger ones and had to do some fiddling to get them...